I found a possible bug of the PDF annotation feature. I added some Chinese annotation into a PDF file with Okular 0.20.2 in Linux, and open the file with Adobe Reader 11.0.0.379 in Windows. Most of the characters in the annotation are correct. However, some characters become wrong characters. I checked these wrong characters, and had the following observation: In Okular, annotations are saved in UTF-16. If the 2-byte code of a character includes "0D", it will be converted to "0A" if shown in Adobe Reader, so the character goes wrong. For example, the Chinese character "不" (U+4E0D) will be shown as "上" (U+4E0A) in the annotation in Adobe Reader. BTW, I tested some other PDF tool to add Chinese annotations. The annotations added by Adobe Reader and Foxit Reader can both be shown correctly in Adobe Reader. I am not sure whether it is a bug of Okular. Although the stored UTF-16 strings are correct, I am not sure whether some meta-info for the annotation is correct. Well, it might also be a bug in Adobe Reader. I have made an example PDF file: <http://1drv.ms/1GQzYTD>, you can download and test it. Will you please take a look? Thank you very much! Reproducible: Always
Created attachment 91722 [details] The file for posterity
Can you please attach (here not in onedrive) the bug that is correctly created by foxit and shows correctly in adobe reader (is it shown correctly in okular too?)
Created attachment 91723 [details] pdf annotation examples The PDF annotation examples created by Adobe, Okular, and Foxit are attached. All the 3 PDF files are shown correctly in Okular and Foxit. However, the PDF file annotated by Okular cannot be shown correctly in Adobe, as shown in the "different.png". Thanks!
I also asked this issue in the Adobe Reader community. One of the reply <https://forums.adobe.com/message/7341360#7341360> said the behavior of Adobe Reader (change 0x0D to 0x0A) is correct according to ISO 32000-1. He thought Okular did something wrong (write "0x0D" directly in literal strings). Will you please take a look? Thanks!
Needs investigation, it's most probably a poppler bug anyway
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.