Hello Team,
Do we have any updates here?
@pthube We have completed analyzing the issue, but it is not yet scheduled for development. We will keep you updated and let you know once it is resolved or we have more information for you.
Thank you for the update and for analyzing the issue. Could you please let us know if there’s an estimated timeline for when this fix might be scheduled for development? We’d appreciate any insights you can share.
@pthube Unfortunately, there are no news regarding the issue yet. Please accept our apologies for your inconvenience.
We understand that resolving such issues can take time; however, this matter is impacting our operations and we kindly request an update on the current status. We would appreciate it if you could prioritize this fix on an urgent basis and let us know the expected timeline for resolution.
@pthube Unfortunately, there are no news regarding the issue yet. Please accept our apologies for your inconvenience. I have asked the responsible developers to take a look at the issue shortly. We will keep you updated.
@pthube WE have investigated the document shared earlier. We did not find any symbols with the above-mentioned codes (0x0080 – 0x0099) in the attached pdf document. We can assume that you meant UTF-8 prefix when encoding 0x2022(Bullet mark) symbol. If so, then such text can be inserted either through the code or directly in the string in DocumentBuilder.
DocumentBuilder builder = new DocumentBuilder();
// this way
builder.Writeln("Zeitschrift F\x2022 R Anorganische Und Allgemeine Chemie");
// or this way
builder.Writeln("Zeitschrift F• R Anorganische Und Allgemeine Chemie");
But this has nothing to do with 0x0080 symbol.
While debugging the visual studio, we can see the text shown above.
It is being received from an XML request.
Could this issue occur if a character in the XML data received in the request is corrupted?
Encoding is UTF-8
@pthube This is probably a problem with different encodings on different systems, and \u0081 is a control character that should not appear in UTF-8 text. You can replace it with \x2022 to get the expected data. Unfortunately, it’s hard to say more about it.