Skip to content

Conversation

@jostang
Copy link

@jostang jostang commented Dec 22, 2017

txt has to be converted into a buffer using the ISO-8859-1 encoding, otherwise there are problems with e. g. usernames or passwords containing non-ASCII characters

txt has to be converted into a buffer using the ISO-8859-1 encoding, otherwise there are problems with e. g. usernames or passwords containing non-ASCII characters
jostang and others added 11 commits January 11, 2018 17:06
If the actual value for "name_kontrahent" was "John Doe", the library returned "undefinedJohn Doe" because the value wasn't initialized with an empty string.
When there is a minus sign (-) at the beginning of a line inside the "Mehrfach" field in the raw data, this was mistaken for the end of the "Mehrfach" field which resulted in the properties of "verwendungszweck" ("verwendungszweck.text", "verwendungszweck.name_kontrahent", ...) being truncated or sometimes even missing.

To fix this, we now recognize only the sequence "\r\n-\r\n" as the end of the message.

Simplified example input data:

:86:166?00GUTSCHRIFT...Hans
-Peter Meier

...resulted in "-Peter Meier" not being parsed anymore for the reference line.
…able

Sticked to the existing naming conventions, even though German and English are mixed
This is necessary for PSD2 compatibility
This is necessary for PSD2 compatibility
include HIRMS (segment specific responses) in error messages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants