|
|
@@ -208,16 +208,14 @@ will produce incorrect results.</td> |
|
|
|
<tr> |
|
|
|
<td>Character Display</td> |
|
|
|
<td>Correct.</td> |
|
|
|
<td>Correct if and only if the font is embedded in the output. (This is possible |
|
|
|
because, although the underlying characters are encoded incorrectly, the embedded font is |
|
|
|
also encoded incorrectly).</td> |
|
|
|
<td>Correct, but copy/paste won't work in Acrobat Reader. (FOP currently doesn't emit the /ToUnicode table which is necessary for copy/paste to work.)</td> |
|
|
|
</tr> |
|
|
|
<tr> |
|
|
|
<td>Embedding the Font</td> |
|
|
|
<td>Optional.</td> |
|
|
|
<td>Mandatory. Not embedding the font produces invalid PDF documents.</td> |
|
|
|
</tr> |
|
|
|
</table> |
|
|
|
<warning id="cid-keyed-encoding-ttf">As shown in the above table, regardless of |
|
|
|
whether the font is embedded or not, text generated from a CID-keyed font metrics file |
|
|
|
will <em>never </em>be encoded properly. |
|
|
|
Further, if the related font is not embedded, it cannot even be displayed properly. |
|
|
|
Obviously, this behavior is not desirable, and we hope to correct it in upcoming releases.</warning> |
|
|
|
</section> |
|
|
|
<section id="truetype-collections-metrics"> |
|
|
|
<title>TrueType Collections Font Metrics</title> |
|
|
@@ -255,6 +253,11 @@ It will display all of the font names and exit with an Exception.</p> |
|
|
|
<note>The font is simply embedded into the PDF file, it is not converted.</note> |
|
|
|
<p>Font embedding is enabled in the userconfig.xml file and controlled by the embed-url attribute. |
|
|
|
If you don't specify the embed-url attribute the font will not be embedded, but will only be referenced.</p> |
|
|
|
<warning> |
|
|
|
Omitting the embed-url attribute for CID-encoded TrueType fonts will currently produce invalid |
|
|
|
PDF files! If you create the XML font metric file using the "-enc ansi" option, you can omit |
|
|
|
the embed-url attribute for TrueType fonts but you're restricted to the WinAnsi character set. |
|
|
|
</warning> |
|
|
|
<p>When FOP embeds a font, it adds a prefix to the fontname to ensure that the name will not match the fontname of an installed font. |
|
|
|
This is helpful with older versions of Acrobat Reader that preferred installed fonts over embedded fonts.</p> |
|
|
|
<p>When embedding PostScript fonts, the entire font is always embedded.</p> |
|
|
@@ -291,7 +294,7 @@ See <a href="#ttf-encoding">Table of TTF Encoding Options</a> for more details.< |
|
|
|
<x-height>766</x-height> |
|
|
|
[..]]]></source> |
|
|
|
<note> |
|
|
|
FOP does not currently comply with or support the PDF/A standard. |
|
|
|
FOP does not currently fully comply with or support the PDF/A standard. There's partial support for PDF/A-1b. This is "work-in-progress". |
|
|
|
</note> |
|
|
|
</section> |
|
|
|
</section> |