#7 Ascii character B2 (superscript 2) not received correctly

[MRothPidgin]

Hello,
I have successfully used SocketReaderService64 to listen for and accept incoming HL7 messages. We noticed that one of the messages converted an incoming ascii B2 and substituted ascii 3F. It is the "²" character. It is just data, it isn't a delimiter or anything special.

Is there some configuration option I can set up to tell SocketReaderService to accept the character as-is?

[Sebastian Weigmann]

Hi there,

thanks for the report.

Would you be so kind to provide a sample message (plz anonymize if needed)? What character encoding is used by default on the sender's and the receiver's side (maybe they are different operating systems)? What other software do you use in the transmission process (socketReader only or a combo of socketReader and anything else)?

Best,
Sebastian

[MRothPidgin]

Hello Sebastian,
I did some more testing, and have confirmed that it was the sending software (not SocketReader) that sent ascii "3F" instead of "B2". When I set up a test where I used SocketReader as the client and sent the same file to SocketReaderService, the correct character "B2" was sent and received unharmed. Please accept my apologies for not testing fully before issuing the bug report.

You may close this ticket.

[Sebastian Weigmann]

Hello,

thanks for your quick answer. Your report could have provided hints to a real bug. There's nothing wrong with the one or another false positive. Please feel free to come back if you have further questions.

Best regards,
Sebastian