-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Date formats ("Geburtsdatum") differ from each other #5
Comments
What does "are not readable" mean in detail? |
Thank you for your answer. After inserting some cards, nothing happens.
|
There should be some output written to the Debug output. What does it say? |
I will check that tomorrow. I have no card to check that yet. |
I found the problem after checking the debug output. The property 'Geschlecht' is missing in PkvResult.cs. I added this line |
Interesting... I had a deeper look into the specs we have (basically those shown in #4 (comment)) where the KVK spec mentions "Das Geburtsdatum ist in der Ausprägung Edit (supplementary info):
Is there any offical specification for that? Neither KVP spec nor PVK spec has a field for |
Also same problem here. It seems that there are at least 3 date format strings provided on different cards. Very confusing :( |
Although this is confusing, this specific problem is not an issue of this library. The library itself does not convert any data nor does it throw any exceptions because of different date formats stored on an eGK/KVP/PVK-Card. The only issue I see is that the documentation of the "Geburtsdatum" field is not specific enough. |
There is a (new) property eGK-KVK/KaupischIT.CardReader/CardResult.cs Lines 81 to 87 in 572d71e
|
Thank you! |
I'm using the Cherry SmartTerminal ST-1144 with the required library. But some card's are not readable. The most G2 cards working but G2.1 is not working. Do you have any ideas what could be the reason?
Best regards.
David
The text was updated successfully, but these errors were encountered: