sumatrapdf
sumatrapdf copied to clipboard
annotation contents doesn't support Chinese
As shown in the above Figure,some Chinese text are ignored and disappeared.
I have the same problem.
Reproduce:
- Create a new free text annotation in a
.pdf
file(I use C17 Final Draft.pdf) - Input the character 生(\u751f), 产(\u4ea7), 的(\u7684)
- The character 生(\u751f) and 的(\u7684) display, but the character 产(\u4ea7) not
- The character 產(\u7522), which is the traditional character of 产(\u4ea7) can display
- The character 亦(\u4ea6) and 亨(\u4ea8) whose Unicode are next to 产(\u4ea7) can display
In addition, all character in CJK Unified Ideographs Extension A(\u3400—\u4db5) seem unsupported.
SumatraPDF Version: 3.3.3 Windows Version: Windows 家庭中文版(Home, Chinese) 19043.1348 Annotation in: C17 Final Draft.pdf
related to https://github.com/sumatrapdfreader/sumatrapdf/issues/2154
whilst 2 wrongs dont make a write the behaviour in edge is worse
SumatraPDF can try to correct the fully seen characters in the comment even if MuPDF cannot render all of them !
@kjk I had hoped the latest CJK font update may have helped with annotation rendering but it seems there may be ? a MuPDF issue with that character range \u3400—\u4fff ?
potential duplicate of https://github.com/sumatrapdfreader/sumatrapdf/issues/1671 MuPDF only supports PDF Standard 14 fonts in comments.
I encountered the same problem, do you have any solutions?
Thank you for your answer
At 2023-10-23 11:49:23, "GitHubRulesOK" @.***> wrote:
potential duplicate of #1671 MuPDF only supports PDF Standard 14 fonts in comments.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
@wms6017 It should be possible to support UTF-16bit in comments as "Rich Text" and unsure how far MuPDF/SumatraPDF has gone towards supporting that more complex annotation. but not all Chinese characters stick to the 2 byte
(paired) when import/export by say clipboard As I have seen on occasion some 3 byte or more coding's.
The Issue is clearly not well covered so this issue is "held open" for now.