[CTS 36] Kanji dropped from KozMin-Bold version

[PhilterPaper]

Opened 2020 August 26 at 06:12:46 by stueber

Dear All,

Here I refer to the example program 025_unifonts.pl which produces when started a pdf file named 025_unifonts.pdf. I am working on a Windows 10 system with the Japanese font package installed.

When the pdf is viewed (for instance using Google Chrome some kanjis are not seen in the text version "KozMin-Bold" for instance in the sentence

uこのモジュールは日本語PDFを生成する。次のような特徴がある。

the character å¾´ is not seen.

In the KozGo-Italic and KozMin versions this character is found.

When the file is displayed in Adobe Acrobat Reader the character again displays fine, but only after the file FontPack1902120058_XtdAlf_Lang_DC.msi is installed.

greetings Kurt

[PhilterPaper]

Comment 2020 August 26 at 10:57:51 by PhilterPaper

Hi Kurt,

Are you talking about the line of CJK text after "=head2" and specifically the 5th character from the right? I looked at it on my Win10 system with Adobe Acrobat Reader DC, FireFox, Chrome, and Edge; and in all cases all four pages showed this character. In other words, it was all there.

So, I'm confused. The glyph is definitely there in the PDF. Are you saying that some font versions are missing this character? Are these problems fixed by upgrading the fonts (in which case this is not a PDF::Builder problem, but a local problem)? Or is there a CMAP problem somewhere (glyph-to-Unicode point mapping)? Remember that usually CJK fonts are not embedded in PDFs (I don't know why), and local font copies are used. Using ttfont() instead, some CJK fonts will embed, and some will even subset (just the glyphs used).

Phil

[PhilterPaper]

Comment 2020 August 26 at 16:50:14 by stueber

Dear Phil,

The Kanji is definitely in the pdf-file. This can be proven when the sentence is cut and pasted somewhere else.

For instance when I pasted it in this forum the character was seen again.

So I guess its a local problem in my computer. In Microsoft Edge the character is visible, in Firefox it is visible, only Google Chrome has a problem and replaces the character with a blank.

Sorry for bothering you... Kurt

[PhilterPaper]

Comment 2020 August 27 at 10:24:12 by PhilterPaper

So it appears to be an issue with a local font file, and not anything with PDF::Builder? If this is correct, do you need this ticket held open for anything, or can I close it?

Sorry for bothering you...

No problem. I appreciate that someone is trying to use PDF::Builder and is opening a ticket when they run into problems. This could save someone else time and trouble in the future by having things to check and a possible solution to their problem. I have no idea how many people are trying to use PDF::Builder, and of those, who assume there's no support and silently walk away from it if they encounter a problem.