Spyros, we cannot verify the font your are using (due to licence protection). Can you check your job with a well known and widely available font that contains greek glyphes (one cited by Jeremias, or one of DejaVu collection). If OK, dthe DINRg is probably faulty. If not OK, can you provide a short XSLFO snippet (not XSLT) that will allow the community to reproduce the described issue?
Pascal Le 26/07/2010 13:26, Spyros Papantoniou a écrit : > Jeremy, > Thank you for the prompt reply! > Alas, I still do not get a usable output although I tried with fonts that > work with MS-Word, and other text processing applications. > My userconfig below includes my attempts. > The font DINRg [DIN Regular] that includes Greek glyphs, still refuses to > print and displays ###. > Removed the metric file, but still no progress. > > Have tried FreeSans, although it has some minor errors with the accented > Greek characters. It also displays ###. > I suspect FOP refuses to look after the first code page. German umlaute, > accent grave etc. are in the 128-255 part of the first page, > Greek chars are located in the second half [128-255] of one of the next pages. > > > How do I confirm that the font has the right CMap table? > With Mac OSX I can write in any font in Greek on all text processing > applications, > I tried to embed the OS font Arial , but still with no success. > > Spyros Papantoniou, > > > > On 26 Ιουλ 2010, at 12:21 μ.μ., Jeremias Maerki wrote: > > >> Normally, http://xmlgraphics.apache.org/fop/faq.html#pdf-characters >> applies. >> >> Removing the metrics-url is one step in the right direction. Then you >> need a font that contains the required glyphs, hoping it is not a >> symbolic font which can cause problems. Fonts like Arial or FreeSans are >> known to have Greek characters. If the font has the right Unicode >> characters and a Unicode CMap table, FOP can display the characters. >> >> On 23.07.2010 12:30:10 Spyros Papantoniou wrote: >> >>> Hello, >>> >>> I try to print Greek characters with FOP 0.95, but apparently only the >>> first page (ANSI) seems to be accessible. The Greek characters are located >>> in the second page (after 255) of the character set. >>> They are displayed as ####. >>> >>> Use userconfig.xml, and was advised to remove the metrics files. >>> Still the fonts are not printed. >>> >>> <fop version="1.0"> >>> <renderers> >>> <renderer mime="application/pdf"> >>> <fonts> >>> <font >>> metrics-url="file:///Users/sp/Triboni8080/ginkgo/fopFonts/Greek.xml" >>> kerning="yes" >>> >>> embed-url="file:///Users/sp/Triboni8080/ginkgo/fopFonts/Greek.ttf"> >>> <font-triplet name="FreeSans" style="normal" weight="normal"/> >>> </font> >>> <font >>> metrics-url="file:///Users/spyrospapantoniou/Triboni8080/ginkgo/fopFonts/GREEKPAR.xml" >>> >>> kerning="yes" >>> >>> embed-url="file:///Users/spyrospapantoniou/Triboni8080/ginkgo/fopFonts/GREEKPAR.ttf"> >>> <font-triplet name="FreeSans" style="normal" weight="bold"/> >>> </font> >>> >>> <font <!-- >>> metrics-url="file:///Users/sp/Triboni8080/ginkgo/fopFonts/DINRg.xml" >>> kerning="yes" --> >>> >>> embed-url="file:///Users/sp/Triboni8080/ginkgo/fopFonts/DINRg.ttf"> >>> <font-triplet name="DINRg" style="normal" weight="normal"/> >>> </font> >>> >>> >>> </fonts> >>> <renderer> >>> </renderers> >>> </fop> >>> >>> Sample output with DINRg: >>> >>> ####: Anafora ########### DINRg, ##μ### 24.05.2010 ### 23.07.2010 >>> >>> latin chars ok, Greek = ### >>> >>> >>> Any ideas how to configure fop to print Greek? >>> many thanks >>> Spyros >>> >>> >>> >>> >> >> >> >> Jeremias Maerki >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > . > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
