- From: Jordan Soet <jordan.soet@u21global.edu.sg>
- Date: Tue, 18 Apr 2006 08:49:24 +0800
- To: "Ken Beesley" <ken.beesley@xrce.xerox.com>, "xsl-fo" <www-xsl-fo@w3.org>
Hey, in FOP 0.91 Beta (and I guess for 0.90 alpha too) the way that the userconfig.xml file is used has been changed (note, I think you should be changing the userconfig.xml, not the config.xml). You can find documentation here: http://xmlgraphics.apache.org/fop/0.91/configuration.html. As it says, just open up your fop.xconf file and change it as you see fit. (also note that for some reason relative addresses don't work) Hope that helps, Jordan -----Original Message----- From: www-xsl-fo-request@w3.org [mailto:www-xsl-fo-request@w3.org] On Behalf Of Ken Beesley Sent: Friday, April 14, 2006 10:31 PM To: xsl-fo Subject: FOP and font problem (newbie) I recently installed fop 0.20.5 (on Linux) and used it successfully with the built-in fonts. My next step was to try to add and use the Charis SIL font family, a Unicode font which is particularly good for rendering any Roman or Cyrillic letter character with one or more "combining diacritic marks". So I converted CharisSILR.ttf, CharisSILB.ttf, CharisSILI.ttf, and CharisSILBI.ttf to make .xml versions, and modified my personal config.xml file to include <fonts> <font metrics-file="/home/beesley/.fop/fonts/CharisSILR.xml" kerning="yes" embed-file="/home/beesley/.fonts/CharisSILR.ttf"> <font-triplet name="Charis SIL" style="normal" weight="normal"/> </font> <font metrics-file="/home/beesley/.fop/fonts/CharisSILB.xml" kerning="yes" embed-file="/home/beesley/.fonts/CharisSILB.ttf"> <font-triplet name="Charis SIL" style="normal" weight="bold"/> </font> <font metrics-file="/home/beesley/.fop/fonts/CharisSILI.xml" kerning="yes" embed-file="/home/beesley/.fonts/CharisSILI.ttf"> <font-triplet name="Charis SIL" style="italic" weight="normal"/> </font> <font metrics-file="/home/beesley/.fop/fonts/CharisSILBI.xml" kerning="yes" embed-file="/home/beesley/.fonts/CharisSILBI.ttf"> <font-triplet name="Charis SIL" style="italic" weight="bold"/> </font> In 0.20.5, the Charis SIL font is found and used. In my FO source file, I can specify them as, e.g. <fo:block font-family="Charis SIL" font-size="18pt" line-height="24pt" space-after.optimum="15pt" text-align="center" padding-top="3pt">Precomposed accented glyphs: Hopìikwa Lavàytutuveni ì í à á ö ö </fo:block> <fo:block font-family="Charis SIL" font-size="18pt" line-height="24pt" space-after.optimum="15pt" text-align="center" padding-top="3pt">Accented glyphs based on plain 'o' followed by a combining accent (grave, acute, circum, diaeresis): ò ó ô ö</fo:block> <fo:block font-family="Charis SIL" font-size="18pt" line-height="24pt" space-after.optimum="15pt" text-align="center" padding-top="3pt">Accented glyphs based on precomposed ö (0x00F6) followed by a combining accent (grave, acute, circum): ö̀ ö́ ö̂ </fo:block> <fo:block font-family="Charis SIL" font-size="18pt" line-height="24pt" space-after.optimum="15pt" text-align="center" padding-top="3pt">Accented glyphs based on plain 'o' followed by a combining diaeresis (0x0308) and another combining accent (grave, acute, circum): ö̀ ö́ ö̂</fo:block> These new fonts are found and used. ************** Problems: 1. The last three fo:block examples use Unicode Combining Diacritical Marks, in particular ̀ (combining grave accent), ́ (combining acute accent), ̂ (combining circumflex accent) and ̈ (combining diaeresis). From the second block, the PDF output shows good placement of single combining diacritics over 'o'. But in the final two blocks, the PDF output is bad. E.g. a sequence like ö́ should be rendered as an 'o', with a diaeresis on top of it, with an acute accent on top of the diaeresis. In fact, with FOP the acute accent is overlaid incorrectly on the diaeresis in the PDF output. The acute accent should be rendered higher up so that it doesn't clash with the diaeresis. The Charis SIL font has Graphite and AAT information necessary to place multiple accents correctly, but it looks like FOP doesn't use that information. XeTeX and some other applications can use Charis SIL and display such combining-diacritic sequences correctly. 2. I tried again using FOP 0.90alpha With 0.90 (and using the same config.xml, .xml fonts, and source file) I got the following error message: fop-0.90 -c /home/beesley/.fop/config.xml -fo tryaccents.xml -pdf out2.pdf Initializing User Agent Configuration Font 'Charis SIL,normal,400' not found. Substituting with default font. i.e. it complains that it can't find 'Charis SIL,normal,400' 3. I then tried FOP 0.91beta (using the same config.xml, .xml fonts, and source file) and got the following slightly different error message: fop-beta -c /home/beesley/.fop/config.xml -fo tryaccents.xml -pdf out3.pdf Font 'SIL,normal,400' not found. Substituting with default font. i.e. it complains that it can't find 'SIL,normal,400' With both alpha and beta, the default font is indeed used, and the output of combining diacritics is completely inacceptable. ******************* Questions: What's going on here? What am I doing wrong? If it's not my fault, when might I expect a bug fix? Thanks, Ken
Received on Tuesday, 18 April 2006 00:48:53 UTC