Skip to content

Fixed a small bug in case the server responds with UT8 responses.#31

Merged
dib0 merged 2 commits intodib0:masterfrom
styxke:utf8_fix
Mar 4, 2026
Merged

Fixed a small bug in case the server responds with UT8 responses.#31
dib0 merged 2 commits intodib0:masterfrom
styxke:utf8_fix

Conversation

@styxke
Copy link
Copy Markdown

@styxke styxke commented Mar 4, 2026

I did not change the ValidateMLLPMessage based on the stringbuilder but this can also be done on the byte array thus removing the need for the stringbuilder altogether.
This code also assumes if you instantiate the client with an encoding that the server will answer in the same encoding, if none provided UTF-8 is assumed.

@styxke
Copy link
Copy Markdown
Author

styxke commented Mar 4, 2026

For example an A19 where the response contains a patient name with UTF-8 characters (eg. "TÉST PÁTIENT") will now decode correctly.

@dib0 dib0 merged commit c9a8ec4 into dib0:master Mar 4, 2026
@dib0
Copy link
Copy Markdown
Owner

dib0 commented Mar 4, 2026

Thanks! The creation of anew release will have to wait until this weekend

@styxke styxke deleted the utf8_fix branch March 8, 2026 18:26
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