https://issues.apache.org/ooo/show_bug.cgi?id=63015
edv@gruene.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |edv@gruene.de
--- Comment #35 from edv@gruene.de ---
After digging through PDF documentations, I found a pretty easy solution (for
PDF-1.4). My Type 1 font is defined in the pdf file like this:
9 0 obj
<</Type/Font/Subtype/Type1/BaseFont/Syntax /ToUnicode 8 0 R
/FirstChar 0 /LastChar 255
/Widths[ ....
When adding "/Encoding /WinAnsiEncoding" to it so that it becomes
9 0 obj
<</Type/Font/Subtype/Type1/BaseFont/Syntax
/Encoding /WinAnsiEncoding /ToUnicode 8 0 R
/FirstChar 0 /LastChar 255
/Widths[ ...
the umlauts show up. So please can we add this to Type1 Font created PDF files?
According to PDF Reference, Third Edition, version 1.4 linked here
http://www.adobe.com/devnet/pdf/pdf_reference_archive.html on Page 317-318
"Entries in a Type 1 font dictionary" it says for /Encoding:
(Optional) A specification of the font’s character encoding, if different from
dictionary its built-in encoding. The value of Encoding may be either the name
of a predefined encoding (MacRomanEncoding, MacExpertEncoding, or
WinAnsiEncoding, as described in Appendix D) or an encoding dictionary that
specifies differences from the font’s built-in encoding or from a specified
predefined encoding (see Section 5.5.5, “Character Encoding”).
So as long as no encoding is set through other constraints "/Encoding
/WinAnsiEncoding" could be set. My font itself has "StandardEncoding" as
parameter and this means pretty much nothing as described on page 329.
Regards
Martin
--
You are receiving this mail because:
You are on the CC list for the issue.
You are watching all issue changes.
|