blocks|key|2509315|text|必须执行三个步骤才能在使用FOP创建的PDF文件中正确显示中文字符(对于默认字体中不可用的所有字符也是如此，更常见的情况是使用非默认字体)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2509316|让我们使用这个简单的fo示例来展示当出现问题时FOP产生的警告：|2509317|<?xml+version="1.0"+encoding="UTF-8"?>
<fo:root+xmlns:fo="http://www.w3.org/1999/XSL/Format">
++++<fo:layout-master-set>
++++++++<fo:simple-page-master+master-name="one">
++++++++++++<fo:region-body+/>
++++++++</fo:simple-page-master>
++++</fo:layout-master-set>
++++<fo:page-sequence+master-reference="one">
++++++++<fo:flow+flow-name="xsl-region-body">
++++++++++++
++++++++++++<fo:block>博洛尼亚大学中国学生的毕业论文</fo:block>
++++++++</fo:flow>
++++</fo:page-sequence>
</fo:root>|code-block|syntax|javascript|2509318|在处理此输入时，FOP会给出几个类似下面的警告：|2509319|org.apache.fop.events.LoggingEventListener+processEvent
WARNING:+Glyph+"?"+(0x535a)+not+available+in+font+"Helvetica".
...|2509320|在FO文件中没有任何明确的字体系列指示，FOP默认为使用Helvetica，这是Base-14+fonts之一(到处都可以使用的字体，所以不需要嵌入它们)。|offset|length|2509321|每种字体都支持一组字符，并为它们分配一个可见的字形；当字体不支持某个字符时，会产生上述警告，并且会显示"#“而不是缺少的字形。|style|BOLD|2509322|步骤1:在FO文件中设置font-family|2509323|如果默认字体不支持文本的字符(或者我们只是想使用不同的字体)，我们必须使用font-family属性来声明所需的字体。|CODE|2509324|font-family的值是继承的，所以如果我们想对整个文档使用相同的字体，我们可以在fo:page-sequence上设置该属性；如果我们只需要对某些段落或单词使用特殊字体，我们可以在相关的fo:block或fo:inline上设置font-family。|2509325|因此，我们的输入变成(以我有的一个字体为例)：|2509326|<?xml+version="1.0"+encoding="UTF-8"?>
<fo:root+xmlns:fo="http://www.w3.org/1999/XSL/Format">
++++<fo:layout-master-set>
++++++++<fo:simple-page-master+master-name="one">
++++++++++++<fo:region-body+/>
++++++++</fo:simple-page-master>
++++</fo:layout-master-set>
++++<fo:page-sequence+master-reference="one">
++++++++<fo:flow+flow-name="xsl-region-body">
++++++++++++
++++++++++++<fo:block+font-family="SimSun">博洛尼亚大学中国学生的毕业论文</fo:block>
++++++++</fo:flow>
++++</fo:page-sequence>
</fo:root>|2509327|但是现在我们得到了一个新的警告，除了旧的警告之外！|2509328|org.apache.fop.events.LoggingEventListener+processEvent
WARNING:+Font+"SimSun,normal,400"+not+found.+Substituting+with+"any,normal,400".
org.apache.fop.events.LoggingEventListener+processEvent
WARNING:+Glyph+"?"+(0x535a)+not+available+in+font+"Times-Roman".
...|2509329|FOP不知道如何将"SimSun“映射到字体文件，因此它默认为不支持我们的中文字符的通用Base-14字体(Times+Roman)，并且仍然显示"#"。|2509330|步骤2:在FOP的配置文件中配置字体映射|2509331|在FOP的文件夹中，文件conf/fop.xconf是一个示例配置；我们可以直接编辑它，也可以从它开始复制。|2509332|配置文件是一个XML文件，我们必须在/fop/renderers/renderer[@mime+=+'application/pdf']/fonts/中添加font+mappings+(对于每个可能的输出mime类型，都有一个renderer部分，因此请检查您是否正确地插入了映射)：|2509333|<?xml+version="1.0"?>
<fop+version="1.0">
++...
++<renderers>
++++<renderer+mime="application/pdf">
++++++...
++++++<fonts>

++++++++
++++++++<font+kerning="yes"+embed-url="/Users/furini/Library/Fonts/SimSun.ttf"+embedding-mode="subset">
++++++++++<font-triplet+name="SimSun"+style="normal"+weight="normal"/>
++++++++

++++++++
++++++++<directory>/Users/furini/Library/Fonts</directory>

++++++</fonts>
++++++...
++++</renderer>
++++...
++</renderers>
</fop>|2509334|2509335|每个font元素指向一个字体文件|unordered-list-item|2509336|每个font-triplet条目标识font-family+%2B+font-style+(正常，斜体，...)+%2B+font-weight+(正常，粗体，...)的组合映射到父element|2509337|using+font+folder+elements中的字体文件也可以自动配置指定文件夹中的所有字体文件(但如果文件夹包含大量字体，则需要一些时间)|2509338|2509339|如果我们有一个完整的文件集，其中包含所需字体的特定版本(正常、斜体、粗体、浅色、粗体、斜体...)我们可以将每个文件映射到精确的字体三元组，从而生成一个非常复杂的PDF。|2509340|在光谱的另一端，我们可以将所有三元组映射到相同的字体文件，如果它是我们所有可用的:在输出中，所有文本看起来都是一样的，即使在FO文件中它的某些部分被标记为斜体或粗体。|2509341|请注意，我们不需要注册所有可能的字体三元组；如果缺少一个，FOP将使用为“相似”字体注册的字体(例如，如果我们不映射三元组"SimSun，italic,400“，FOP将使用映射到"SimSun，normal,400”的字体，警告我们字体替换)。|2509342|我们还没有完成，因为没有下一步和最后一步，当我们处理输入文件时什么也不会改变。|2509343|步骤3:告诉FOP使用配置文件|2509344|如果我们从命令行调用FOP，我们使用-c选项指向我们的配置文件，例如：|2509345|$+fop+-c+/path/to/our/fop.xconf+input.fo+input.pdf|2509346|从我们可以使用的java代码(另请参阅FOP's+site)：|2509347|fopFactory.setUserConfig(new+File("/path/to/our/fop.xconf"));|2509348|现在，PDF最终应该正确使用所需的字体并按预期显示。|2509349|相反，如果FOP突然终止，并出现如下错误：|2509350|org.apache.fop.cli.Main+startFOP
SEVERE:+Exception+org.apache.fop.apps.FOPException:+Failed+to+resolve+font+with+embed-url+'/Users/furini/Library/Fonts/doesNotExist.ttf'|2509351|这意味着FOP找不到字体文件，需要再次检查字体配置；典型的原因有|2509352|url|2509353|insufficient+|2509354|在字体文件中输入错误的权限访问字体文件|2509355|2509356|2509357|entityMap|0|LINK|mutability|MUTABLE|http://en.wikipedia.org/wiki/Portable_Document_Format#Standard_Type_1_Fonts_.28Standard_14_Fonts.29|1|http://xmlgraphics.apache.org/fop/trunk/fonts.html|2|http://www.w3.org/TR/xsl/#font-family|3|http://www.w3.org/TR/xsl/#font-style|4|http://www.w3.org/TR/xsl/#font-weight|5|http://xmlgraphics.apache.org/fop/1.1/embedding.html#config-external^0|0|0|0|0|0|14|D|0|0|1C|E|0|0|11|B|0|0|B|17|G|2O|8|2X|9|39|B|0|0|0|0|0|0|O|0|0|C|E|0|I|1L|35|8|26|D|1|0|0|0|2|4|0|2|C|I|B|W|A|1L|B|I|B|2|W|A|3|1L|B|4|0|6|4|B|6|0|0|0|0|0|0|0|I|2|0|0|J|A|5|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|37|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|38|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|39|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|3A|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|3B|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|3C|8|@]|9|@$O|3D|P|3E|1|3F]]|A|$]]|$1|Q|3|R|5|6|7|3G|8|@$O|3H|P|3I|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|3J|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|3K|8|@$O|3L|P|3M|S|Y]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|3N|8|@$O|3O|P|3P|S|Y]|$O|3Q|P|3R|S|Y]|$O|3S|P|3T|S|Y]|$O|3U|P|3V|S|Y]|$O|3W|P|3X|S|Y]]|9|@]|A|$]]|$1|11|3|12|5|6|7|3Y|8|@]|9|@]|A|$]]|$1|13|3|14|5|F|7|3Z|8|@]|9|@]|A|$G|H]]|$1|15|3|16|5|6|7|40|8|@]|9|@]|A|$]]|$1|17|3|18|5|F|7|41|8|@]|9|@]|A|$G|H]]|$1|19|3|1A|5|6|7|42|8|@$O|43|P|44|S|T]]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|45|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|46|8|@$O|47|P|48|S|Y]]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|49|8|@$O|4A|P|4B|S|Y]|$O|4C|P|4D|S|Y]]|9|@$O|4E|P|4F|1|4G]]|A|$]]|$1|1H|3|1I|5|F|7|4H|8|@]|9|@]|A|$G|H]]|$1|1J|3|-4|5|6|7|4I|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|1M|7|4J|8|@$O|4K|P|4L|S|Y]]|9|@]|A|$]]|$1|1N|3|1O|5|1M|7|4M|8|@$O|4N|P|4O|S|Y]|$O|4P|P|4Q|S|Y]|$O|4R|P|4S|S|Y]|$O|4T|P|4U|S|Y]]|9|@$O|4V|P|4W|1|4X]|$O|4Y|P|4Z|1|50]|$O|51|P|52|1|53]]|A|$]]|$1|1P|3|1Q|5|1M|7|54|8|@$O|55|P|56|S|Y]|$O|57|P|58|S|Y]]|9|@]|A|$]]|$1|1R|3|-4|5|6|7|59|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|5A|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|6|7|5B|8|@]|9|@]|A|$]]|$1|1W|3|1X|5|6|7|5C|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|6|7|5D|8|@]|9|@]|A|$]]|$1|20|3|21|5|6|7|5E|8|@]|9|@]|A|$]]|$1|22|3|23|5|6|7|5F|8|@$O|5G|P|5H|S|Y]]|9|@]|A|$]]|$1|24|3|25|5|F|7|5I|8|@]|9|@]|A|$G|H]]|$1|26|3|27|5|6|7|5J|8|@]|9|@$O|5K|P|5L|1|5M]]|A|$]]|$1|28|3|29|5|F|7|5N|8|@]|9|@]|A|$G|H]]|$1|2A|3|2B|5|6|7|5O|8|@]|9|@]|A|$]]|$1|2C|3|2D|5|6|7|5P|8|@]|9|@]|A|$]]|$1|2E|3|2F|5|F|7|5Q|8|@]|9|@]|A|$G|H]]|$1|2G|3|2H|5|6|7|5R|8|@]|9|@]|A|$]]|$1|2I|3|2J|5|6|7|5S|8|@]|9|@]|A|$]]|$1|2K|3|2L|5|1M|7|5T|8|@]|9|@]|A|$]]|$1|2M|3|2N|5|1M|7|5U|8|@]|9|@]|A|$]]|$1|2O|3|-4|5|6|7|5V|8|@]|9|@]|A|$]]|$1|2P|3|-4|5|6|7|5W|8|@]|9|@]|A|$]]|$1|2Q|3|-4|5|6|7|5X|8|@]|9|@]|A|$]]]|2R|$2S|$5|2T|2U|2V|A|$2J|2W]]|2X|$5|2T|2U|2V|A|$2J|2Y]]|2Z|$5|2T|2U|2V|A|$2J|30]]|31|$5|2T|2U|2V|A|$2J|32]]|33|$5|2T|2U|2V|A|$2J|34]]|35|$5|2T|2U|2V|A|$2J|36]]]]

Three steps must be taken for chinese characters to correctly show in a PDF file created with FOP (this is also true for all characters not available in the default font, and more generally to use a non-default font).

Let us use this simple fo example to show the warnings produced by FOP when something is wrong:

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"&gt;
 &lt;fo:layout-master-set&gt;
 &lt;fo:simple-page-master master-name="one"&gt;
 &lt;fo:region-body /&gt;
 &lt;/fo:simple-page-master&gt;
 &lt;/fo:layout-master-set&gt;
 &lt;fo:page-sequence master-reference="one"&gt;
 &lt;fo:flow flow-name="xsl-region-body"&gt;
 &lt;!-- a block of chinese text --&gt;
 &lt;fo:block&gt;博洛尼亚大学中国学生的毕业论文&lt;/fo:block&gt;
 &lt;/fo:flow&gt;
 &lt;/fo:page-sequence&gt;
&lt;/fo:root&gt;
</code></pre>

Processing this input, FOP gives several warnings similar to this one:

<pre><code>org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "?" (0x535a) not available in font "Helvetica".
...
</code></pre>

Without any explicit font-family indication in the FO file, FOP defaults to using Helvetica, which is one of the <a href="http://en.wikipedia.org/wiki/Portable_Document_Format#Standard_Type_1_Fonts_.28Standard_14_Fonts.29" rel="noreferrer">Base-14 fonts</a> (fonts that are available everywhere, so there is no need to embed them).

Each font supports a set of characters, assigning a visible glyphs to them; when a font does not support a character, the above warning is produced, and the PDF shows "#" instead of the missing glyph.

<h2>Step 1: set font-family in the FO file</h2>

If the default font doesn't support the characters of our text (or we simply want to use a different font), we must use the <code>font-family</code> property to state the desired one.

The value of <code>font-family</code> is inherited, so if we want to use the same font for the whole document we can set the property on the <code>fo:page-sequence</code>; if we need a special font just for some paragraphs or words, we can set <code>font-family</code> on the relevant <code>fo:block</code> or <code>fo:inline</code>.

So, our input becomes (using a font I have as example):

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"&gt;
 &lt;fo:layout-master-set&gt;
 &lt;fo:simple-page-master master-name="one"&gt;
 &lt;fo:region-body /&gt;
 &lt;/fo:simple-page-master&gt;
 &lt;/fo:layout-master-set&gt;
 &lt;fo:page-sequence master-reference="one"&gt;
 &lt;fo:flow flow-name="xsl-region-body"&gt;
 &lt;!-- a block of chinese text --&gt;
 &lt;fo:block font-family="SimSun"&gt;博洛尼亚大学中国学生的毕业论文&lt;/fo:block&gt;
 &lt;/fo:flow&gt;
 &lt;/fo:page-sequence&gt;
&lt;/fo:root&gt;
</code></pre>

But now we get a new warning, in addition to the old ones!

<pre><code>org.apache.fop.events.LoggingEventListener processEvent
WARNING: Font "SimSun,normal,400" not found. Substituting with "any,normal,400".
org.apache.fop.events.LoggingEventListener processEvent
WARNING: Glyph "?" (0x535a) not available in font "Times-Roman".
...
</code></pre>

FOP doesn't know how to map "SimSun" to a font file, so it defaults to a generic Base-14 font (Times-Roman) which does not support our chinese characters, and the PDF still shows "#".

<h2>Step 2: configure font mapping in FOP's configuration file</h2>

Inside FOP's folder, the file <code>conf/fop.xconf</code> is an example configuration; we can directly edit it or make a copy to start from.

The configuration file is an XML file, and we have to add the <a href="http://xmlgraphics.apache.org/fop/trunk/fonts.html" rel="noreferrer">font mappings</a> inside <code>/fop/renderers/renderer[@mime = 'application/pdf']/fonts/</code> (there is a <code>renderer</code> section for each possible output mime type, so check you are inserting your mapping in the right one):

<pre><code>&lt;?xml version="1.0"?&gt;
&lt;fop version="1.0"&gt;
 ...
 &lt;renderers&gt;
 &lt;renderer mime="application/pdf"&gt;
 ...
 &lt;fonts&gt;

 &lt;!-- specific font mapping --&gt;
 &lt;font kerning="yes" embed-url="/Users/furini/Library/Fonts/SimSun.ttf" embedding-mode="subset"&gt;
 &lt;font-triplet name="SimSun" style="normal" weight="normal"/&gt;
 &lt;/font&gt;

 &lt;!-- "bulk" font mapping --&gt;
 &lt;directory&gt;/Users/furini/Library/Fonts&lt;/directory&gt;

 &lt;/fonts&gt;
 ...
 &lt;/renderer&gt;
 ...
 &lt;/renderers&gt;
&lt;/fop&gt;
</code></pre>

<ul>
<li>each <code>font</code> element points to a font file</li>
<li>each <code>font-triplet</code> entry identifies a combination of <a href="http://www.w3.org/TR/xsl/#font-family" rel="noreferrer"><code>font-family</code></a> + <a href="http://www.w3.org/TR/xsl/#font-style" rel="noreferrer"><code>font-style</code></a> (normal, italic, ...) + <a href="http://www.w3.org/TR/xsl/#font-weight" rel="noreferrer"><code>font-weight</code></a> (normal, bold, ...) mapped to the font file in the parent <code>font</code> element</li>
<li>using <code>folder</code> elements it is also possible to configure automatically all the font files inside the indicated folders (but this takes some time if the folders contain a lot of fonts)</li>
</ul>

If we have a complete file set with specific versions of the desired font (normal, italic, bold, light, bold italic, ...) we can map each file to the precise font triplet, thus producing a very sophisticated PDF.

On the opposite end of the spectrum we can map all the triplet to the same font file, if it's all we have available: in the output all text will appear the same, even if in the FO file parts of it were marked as italic or bold. 

Note that we don't need to register all possible font triplets; if one is missing, FOP will use the font registered for a "similar" one (for example, if we don't map the triplet "SimSun,italic,400" FOP will use the font mapped to "SimSun,normal,400", warning us about the font substitution).

We are not done yet, as without the next and last step nothing changes when we process our input file.

<h2>Step 3: tell FOP to use the configuration file</h2>

If we are calling FOP from the command line, we use the <code>-c</code> option to point to our configuration file, for example:

<pre><code>$ fop -c /path/to/our/fop.xconf input.fo input.pdf
</code></pre>

From java code we can use (see also <a href="http://xmlgraphics.apache.org/fop/1.1/embedding.html#config-external" rel="noreferrer">FOP's site</a>): 

<pre><code>fopFactory.setUserConfig(new File("/path/to/our/fop.xconf"));
</code></pre>

Now, at last, the PDF should correctly use the desired fonts and appear as expected.

If instead FOP terminates abruptly with an error like this:

<pre><code>org.apache.fop.cli.Main startFOP
SEVERE: Exception org.apache.fop.apps.FOPException: Failed to resolve font with embed-url '/Users/furini/Library/Fonts/doesNotExist.ttf'
</code></pre>

it means that FOP could not find the font file, and the font configuration needs to be checked again; typical causes are

<ul>
<li>a typo in the font url</li>
<li>insufficient privileges to access the font file</li>
</ul>

I am maintaining a program which uses the Apache FOP for printing PDF documents. There have been a couple complaints about the Chinese characters coming up as &quot;####&quot;. I have found an existing thread out there about this problem and done some research on my side.
<a href="http://apache-fop.1065347.n5.nabble.com/Chinese-Fonts-td10789.html" rel="nofollow noreferrer">http://apache-fop.1065347.n5.nabble.com/Chinese-Fonts-td10789.html</a>
I do have the uming.tff language files installed on my system. Unlike the person in this thread, I am still getting the &quot;####&quot;.
From this point forward, has anyone seen a work around that would allow you to print complex characters in a PDF document using Apache FOP?

Apache FOP Displaying ### with SimSun

我正在维护一个使用Apache FOP打印PDF文档的程序。有几个人抱怨说，这个汉字变成了"####“。我找到了一个关于这个问题的现有帖子，并在我这边做了一些研究。我的系统上确实安装了uming.tff语言文件。与这个帖子中的人不同，我仍然得到了"####“。从现在开始，有没有人看到过允许您使用Apache FOP打印...

问Apache FOP使用SimSun显示###
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Apache FOP使用SimSun显示###EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Apache FOP使用SimSun显示###
EN