Re: Generating metrics
Thank you, it works but i get an another error message: Unsupported TrueType font: Unicode cmap table not present. Aborting and metrics file do not generated ** Parsing font... Reading C:\windows\fonts\Barcode128C.TTf... sfnt version: OpenType 1.0 Reading 14 dir tables dir tables: [PCLT, loca, post, glyf, fpgm, hmtx, hhea, prep, cvt , OS/2, cmap, n ame, head, maxp] unit per em: 1000 Number of glyphs in font: 132 hhea.Ascender: 1498 1498 hhea.Descender: -364 -364 Number of horizontal metrics: 132 PostScript format: 0x2 PostScript format 2 Reading 2 glyphnames, that are not in the standard Macintosh set. Total number o f glyphs=132 sTypoAscender: 1498 1498 sTypoDescender: -364 -364 sTypoLineGap: 97 usWinAscent: 1498 1498 usWinDescent: 364 364 sxHeight: 0 sCapHeight: 500 Font box height: 1862 Ascender and descender together are larger than the em box. This could lead to a wrong baseline placement in Apache FOP. 1 0 0 1 Barcode 128C 1 0 0 2 Regular 1 0 0 3 Barcode 128C 1 0 0 4 Barcode 128C 1 0 0 6 Barcode 128C 3 0 1033 1 Barcode 128C 3 0 1033 2 Regular 3 0 1033 3 Barcode 128C 3 0 1033 4 Barcode 128C 3 0 1033 6 Barcode 128C xHeight from PCLT: 1498 1498 capHeight from PCLT: 1498 1498 3 cmap tables Platform ID: 0 Encoding: 0 Platform ID: 1 Encoding: 0 Platform ID: 3 Encoding: 0 Unsupported TrueType font: Unicode cmap table not present. Aborting XML font metrics file successfully created. *** Tomas Rimšelis wrote: > > Hello, > please make sure, that xmlgraphics-commons-1.3.1.jar is included, too. In > Your case a command should be like this: > > java -cp > "build/fop.jar;lib/serializer-2.7.0.jar;lib/commons-logging-1.0.4.jar;lib/commons-io-1.3.1.jar;lib/xmlgraphics-commons-1.3.1.jar" > org.apache.fop.fonts.apps.TTFReader > C:\windows\fonts\Barcode128C.TTf Barcode128C.xml > > On Mon, Jan 4, 2010 at 11:53 PM, Magdikova wrote: > >> >> I have the same problem, >> >> If I run the following command: >> java -cp >> >> "build/fop.jar;lib/serializer-2.7.0.jar;lib/commons-logging-1.0.4.jar;lib/commons-io-1.3.1.jar" >> org.apache.fop.fonts.apps.TTFReader C:\windows\fonts\Barcode128C.TTf >> Barcode128C.xml >> >> I get the following error message: >> ** >> TTF Reader for Apache FOP 0.95 >> >> Parsing font... >> Reading C:\windows\fonts\Barcode128C.TTf... >> Exception in thread "main" java.lang.NoClassDefFoundError: >> org/apache/xmlgraphic >> s/fonts/Glyphs >>at >> org.apache.fop.fonts.truetype.TTFFile.initAnsiWidths(TTFFile.java:444 >> ) >>at >> org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:493) >>at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209) >>at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164) >> Caused by: java.lang.ClassNotFoundException: >> org.apache.xmlgraphics.fonts.Glyphs >> >>at java.net.URLClassLoader$1.run(Unknown Source) >>at java.security.AccessController.doPrivileged(Native Method) >>at java.net.URLClassLoader.findClass(Unknown Source) >>at java.lang.ClassLoader.loadClass(Unknown Source) >>at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) >>at java.lang.ClassLoader.loadClass(Unknown Source) >>at java.lang.ClassLoader.loadClassInternal(Unknown Source) >>... 4 more >> >> ** >> >> Please help me, thanks in advance. >> >> >> Erwan de FERRIERES wrote: >> > >> > Hi all, >> > >> > I'm trying to generate font metrics in order to import them in a >> > project. Generating start well, but then I've got some errors. I'm >> > running debian and javai version is 1.6.0_07 >> > >> > Here is the line I type to launch the metric generation : >> > java -cp >> fop.jar:avalon-framework.jar:commons-logging.jar:commons-io.jar >> > org.apache.fop.fonts.apps.TTFReader FreeMono.ttf -d DEBUG >> > >> > Then the debug tells me : >> > >> > TTF Reader for Apache FOP 0.95 >> > >> > Parsing font... >> > Reading FreeMono.ttf... >> > sfnt version: OpenType 1.0 >> > Reading 18 dir tables >> > dir tables: [loca, post, FFTM, glyf, fpgm, hmtx, GPOS, hhea, prep, >> GSUB, >> > GDEF, cvt , gasp, name, OS/2, cmap, head, maxp] >> > unit per em: 1000 >> > Number of glyphs in font: 2709 >> > hhea.Ascender: 900 900 >> > hhea.Descender: -300 -300 >> > Number of horizontal metrics: 4 >> > Exception in thread "main" java.lang.NoClassDefFoundError: >> > org/apache/xmlgraphics/fonts/Glyphs >> > at >> org.apache.fop.fonts.truetype.TTFFile.initAnsiWidths(TTFFile.java:444) >> > at >> org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:493) >> > at >> org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209) >> > at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164) >> > Caused by: java.lang.ClassNotFoundException: >> > org.apache.xmlgraphics.fonts.Glyphs >> > at java.net.URLClassLoader$1.run(
Generating metrics error: Unicode cmap table not present. Aborting
I would like to generate metrics filebut I get the following error:Unsupported TrueType font: Unicode cmap table not present. Aborting what is the problem? "XML font metrics file successfully created." but I can not found the xml file TTF Reader for Apache FOP 0.95 Parsing font... Reading C:\windows\fonts\Barcode128C.TTf... sfnt version: OpenType 1.0 Reading 14 dir tables dir tables: [PCLT, loca, post, glyf, fpgm, hmtx, hhea, prep, cvt , OS/2, cmap, n ame, head, maxp] unit per em: 1000 Number of glyphs in font: 132 hhea.Ascender: 1498 1498 hhea.Descender: -364 -364 Number of horizontal metrics: 132 PostScript format: 0x2 PostScript format 2 Reading 2 glyphnames, that are not in the standard Macintosh set. Total number o f glyphs=132 sTypoAscender: 1498 1498 sTypoDescender: -364 -364 sTypoLineGap: 97 usWinAscent: 1498 1498 usWinDescent: 364 364 sxHeight: 0 sCapHeight: 500 Font box height: 1862 Ascender and descender together are larger than the em box. This could lead to a wrong baseline placement in Apache FOP. 1 0 0 1 Barcode 128C 1 0 0 2 Regular 1 0 0 3 Barcode 128C 1 0 0 4 Barcode 128C 1 0 0 6 Barcode 128C 3 0 1033 1 Barcode 128C 3 0 1033 2 Regular 3 0 1033 3 Barcode 128C 3 0 1033 4 Barcode 128C 3 0 1033 6 Barcode 128C xHeight from PCLT: 1498 1498 capHeight from PCLT: 1498 1498 3 cmap tables Platform ID: 0 Encoding: 0 Platform ID: 1 Encoding: 0 Platform ID: 3 Encoding: 0 Unsupported TrueType font: Unicode cmap table not present. Aborting XML font metrics file successfully created. C:\xampp\fop>^A -- View this message in context: http://old.nabble.com/Generating-metrics-error%3A-Unicode-cmap-table-not-present.-Aborting-tp27024689p27024689.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Generating metrics
Hello, please make sure, that xmlgraphics-commons-1.3.1.jar is included, too. In Your case a command should be like this: java -cp "build/fop.jar;lib/serializer-2.7.0.jar;lib/commons-logging-1.0.4.jar;lib/commons-io-1.3.1.jar;lib/xmlgraphics-commons-1.3.1.jar" org.apache.fop.fonts.apps.TTFReader C:\windows\fonts\Barcode128C.TTf Barcode128C.xml On Mon, Jan 4, 2010 at 11:53 PM, Magdikova wrote: > > I have the same problem, > > If I run the following command: > java -cp > > "build/fop.jar;lib/serializer-2.7.0.jar;lib/commons-logging-1.0.4.jar;lib/commons-io-1.3.1.jar" > org.apache.fop.fonts.apps.TTFReader C:\windows\fonts\Barcode128C.TTf > Barcode128C.xml > > I get the following error message: > ** > TTF Reader for Apache FOP 0.95 > > Parsing font... > Reading C:\windows\fonts\Barcode128C.TTf... > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/xmlgraphic > s/fonts/Glyphs >at > org.apache.fop.fonts.truetype.TTFFile.initAnsiWidths(TTFFile.java:444 > ) >at org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:493) >at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209) >at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164) > Caused by: java.lang.ClassNotFoundException: > org.apache.xmlgraphics.fonts.Glyphs > >at java.net.URLClassLoader$1.run(Unknown Source) >at java.security.AccessController.doPrivileged(Native Method) >at java.net.URLClassLoader.findClass(Unknown Source) >at java.lang.ClassLoader.loadClass(Unknown Source) >at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) >at java.lang.ClassLoader.loadClass(Unknown Source) >at java.lang.ClassLoader.loadClassInternal(Unknown Source) >... 4 more > > ** > > Please help me, thanks in advance. > > > Erwan de FERRIERES wrote: > > > > Hi all, > > > > I'm trying to generate font metrics in order to import them in a > > project. Generating start well, but then I've got some errors. I'm > > running debian and javai version is 1.6.0_07 > > > > Here is the line I type to launch the metric generation : > > java -cp fop.jar:avalon-framework.jar:commons-logging.jar:commons-io.jar > > org.apache.fop.fonts.apps.TTFReader FreeMono.ttf -d DEBUG > > > > Then the debug tells me : > > > > TTF Reader for Apache FOP 0.95 > > > > Parsing font... > > Reading FreeMono.ttf... > > sfnt version: OpenType 1.0 > > Reading 18 dir tables > > dir tables: [loca, post, FFTM, glyf, fpgm, hmtx, GPOS, hhea, prep, GSUB, > > GDEF, cvt , gasp, name, OS/2, cmap, head, maxp] > > unit per em: 1000 > > Number of glyphs in font: 2709 > > hhea.Ascender: 900 900 > > hhea.Descender: -300 -300 > > Number of horizontal metrics: 4 > > Exception in thread "main" java.lang.NoClassDefFoundError: > > org/apache/xmlgraphics/fonts/Glyphs > > at > org.apache.fop.fonts.truetype.TTFFile.initAnsiWidths(TTFFile.java:444) > > at org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:493) > > at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209) > > at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164) > > Caused by: java.lang.ClassNotFoundException: > > org.apache.xmlgraphics.fonts.Glyphs > > at java.net.URLClassLoader$1.run(URLClassLoader.java:200) > > at java.security.AccessController.doPrivileged(Native Method) > > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > > ... 4 more > > > > I've been trying with other fonts, but got the same error. > > Thank you for your time and help ! > > > > > > -- > > - Erwan - > > > > - > > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > > > > > > > > -- > View this message in context: > http://old.nabble.com/Generating-metrics-tp20668871p27019948.html > Sent from the FOP - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > >
Re: Generating metrics
I have the same problem, If I run the following command: java -cp "build/fop.jar;lib/serializer-2.7.0.jar;lib/commons-logging-1.0.4.jar;lib/commons-io-1.3.1.jar" org.apache.fop.fonts.apps.TTFReader C:\windows\fonts\Barcode128C.TTf Barcode128C.xml I get the following error message: ** TTF Reader for Apache FOP 0.95 Parsing font... Reading C:\windows\fonts\Barcode128C.TTf... Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/xmlgraphic s/fonts/Glyphs at org.apache.fop.fonts.truetype.TTFFile.initAnsiWidths(TTFFile.java:444 ) at org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:493) at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209) at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164) Caused by: java.lang.ClassNotFoundException: org.apache.xmlgraphics.fonts.Glyphs at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) ... 4 more ** Please help me, thanks in advance. Erwan de FERRIERES wrote: > > Hi all, > > I'm trying to generate font metrics in order to import them in a > project. Generating start well, but then I've got some errors. I'm > running debian and javai version is 1.6.0_07 > > Here is the line I type to launch the metric generation : > java -cp fop.jar:avalon-framework.jar:commons-logging.jar:commons-io.jar > org.apache.fop.fonts.apps.TTFReader FreeMono.ttf -d DEBUG > > Then the debug tells me : > > TTF Reader for Apache FOP 0.95 > > Parsing font... > Reading FreeMono.ttf... > sfnt version: OpenType 1.0 > Reading 18 dir tables > dir tables: [loca, post, FFTM, glyf, fpgm, hmtx, GPOS, hhea, prep, GSUB, > GDEF, cvt , gasp, name, OS/2, cmap, head, maxp] > unit per em: 1000 > Number of glyphs in font: 2709 > hhea.Ascender: 900 900 > hhea.Descender: -300 -300 > Number of horizontal metrics: 4 > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/xmlgraphics/fonts/Glyphs > at > org.apache.fop.fonts.truetype.TTFFile.initAnsiWidths(TTFFile.java:444) > at org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:493) > at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209) > at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164) > Caused by: java.lang.ClassNotFoundException: > org.apache.xmlgraphics.fonts.Glyphs > at java.net.URLClassLoader$1.run(URLClassLoader.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > ... 4 more > > I've been trying with other fonts, but got the same error. > Thank you for your time and help ! > > > -- > - Erwan - > > - > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > > > -- View this message in context: http://old.nabble.com/Generating-metrics-tp20668871p27019948.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
HELP me: java.lang.NoClassDefFoundError: org/apache/xmlgraphics/fonts/Glyphs
I am using apache fop 0.95 and I would like to generate a letter with barcode 128. I need Barcode128C.TTF and Barcode128C.xml files I have to generate font metrics file (Barcode128C.xml). I am using the folowing command: java -cp "build/fop.jar;lib/serializer-2.7.0.jar;lib/commons-logging-1.0.4.jar;lib/commons-io-1.3.1.jar" org.apache.fop.fonts.apps.TTFReader C:\windows\fonts\Barcode128C.TTf Barcode128C.xml I get this error : " TTF Reader for Apache FOP 0.95 Parsing font... Reading C:\windows\fonts\Barcode128C.TTf... Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/xmlgraphic s/fonts/Glyphs at org.apache.fop.fonts.truetype.TTFFile.initAnsiWidths(TTFFile.java:444 ) at org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:493) at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209) at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164) Caused by: java.lang.ClassNotFoundException: org.apache.xmlgraphics.fonts.Glyphs at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) ... 4 more please help me what is the problem? -- View this message in context: http://old.nabble.com/HELP-me%3A-java.lang.NoClassDefFoundError%3A-org-apache-xmlgraphics-fonts-Glyphs-tp27019770p27019770.html Sent from the FOP - Users mailing list archive at Nabble.com.
Re: Looking for help, including consulting, with font selection
Simon, The claim is that it's fixed on trunk. I did a trunk build, and my colleague who started all this will test it. If his test fails, I'll reopen it. --benson On Mon, Jan 4, 2010 at 3:12 PM, Simon Pepping wrote: > Pascal and Abel, > > Why was this bug closed? I believe it is Benson's intention to report > a known issue. He is looking to get it resolved and is willing to pay > for the effort. Unless Benson is raising a non-existent problem, I am > happy with his initiative. And I do not have the impression that it is > a non-existent problem. > > Benson, > > Can you submit the resulting XSL-FO file, and possibly the resulting > HTML file for comparison of the intended result? I have a problem > running your transformations, and I do not wish to debug my XSLT2 > system now. > > Regards, Simon > > On Mon, Jan 04, 2010 at 06:41:00PM +0100, Abel Braaksma wrote: >> It concludes what was said. And Pascal's remark is about the issue >> that was solved. But you try it with FOP Trunk and decide whether it >> is sufficiently solved. If not, provide a reproducible example >> (reproducible with the latest build) . >> >> My talk about character-by-character is a known issue and is >> unrelated to your bug report and is sufficiently covered on other >> places. >> >> Benson Margulies wrote: >> >Does this add up to a reason to reopen the bz? >> > > > -- > Simon Pepping > home page: http://www.leverkruid.eu > > - > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > > - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
Pascal and Abel, Why was this bug closed? I believe it is Benson's intention to report a known issue. He is looking to get it resolved and is willing to pay for the effort. Unless Benson is raising a non-existent problem, I am happy with his initiative. And I do not have the impression that it is a non-existent problem. Benson, Can you submit the resulting XSL-FO file, and possibly the resulting HTML file for comparison of the intended result? I have a problem running your transformations, and I do not wish to debug my XSLT2 system now. Regards, Simon On Mon, Jan 04, 2010 at 06:41:00PM +0100, Abel Braaksma wrote: > It concludes what was said. And Pascal's remark is about the issue > that was solved. But you try it with FOP Trunk and decide whether it > is sufficiently solved. If not, provide a reproducible example > (reproducible with the latest build) . > > My talk about character-by-character is a known issue and is > unrelated to your bug report and is sufficiently covered on other > places. > > Benson Margulies wrote: > >Does this add up to a reason to reopen the bz? > > -- Simon Pepping home page: http://www.leverkruid.eu - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
It concludes what was said. And Pascal's remark is about the issue that was solved. But you try it with FOP Trunk and decide whether it is sufficiently solved. If not, provide a reproducible example (reproducible with the latest build) . My talk about character-by-character is a known issue and is unrelated to your bug report and is sufficiently covered on other places. Benson Margulies wrote: Does this add up to a reason to reopen the bz? On Mon, Jan 4, 2010 at 11:19 AM, Pascal Sancho wrote: Abel Braaksma a écrit : To recap: apparently the problem was that for individual letters not available in a font, the wrong selection was made, resulting in the question mark (for missing letter) appearing. No, FOP replaces missing characters "#" character. I suspect a wrong character selection While this was apparently fixed, note that character-by-character is still not supported. Meaning, in "AXB", where X is a Japanese (or other) character not available in font Candara (or other), but available in MS PMincho, it will still display as a question mark. Change it to "A X B" and it should work. If your only issue is with Japanese text, this can easily be solved in the XSLT step (using codepoints ranges), in case you have this type of exceptional cases in your text. Good to know that the issue is solved, Pascal. -- Abel -- Pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
Does this add up to a reason to reopen the bz? On Mon, Jan 4, 2010 at 11:19 AM, Pascal Sancho wrote: > Abel Braaksma a écrit : >> >> To recap: apparently the problem was that for individual letters not >> available in a font, the wrong selection was made, resulting in the >> question mark (for missing letter) appearing. >> > > No, FOP replaces missing characters "#" character. I suspect a wrong > character selection >> >> While this was apparently fixed, note that character-by-character is >> still not supported. Meaning, in "AXB", where X is a Japanese (or other) >> character not available in font Candara (or other), but available in MS >> PMincho, it will still display as a question mark. Change it to "A X B" >> and it should work. >> >> If your only issue is with Japanese text, this can easily be solved in >> the XSLT step (using codepoints ranges), in case you have this type of >> exceptional cases in your text. >> >> Good to know that the issue is solved, Pascal. >> >> -- Abel -- > > Pascal > > - > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > > - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
Abel Braaksma a écrit : To recap: apparently the problem was that for individual letters not available in a font, the wrong selection was made, resulting in the question mark (for missing letter) appearing. No, FOP replaces missing characters "#" character. I suspect a wrong character selection While this was apparently fixed, note that character-by-character is still not supported. Meaning, in "AXB", where X is a Japanese (or other) character not available in font Candara (or other), but available in MS PMincho, it will still display as a question mark. Change it to "A X B" and it should work. If your only issue is with Japanese text, this can easily be solved in the XSLT step (using codepoints ranges), in case you have this type of exceptional cases in your text. Good to know that the issue is solved, Pascal. -- Abel -- Pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
Am I correct in understanding that list that character-by-character is indeed not supported? I'm not sure what change was responsible for fixing this particular issue though, doesn't seem to be mentioned... Pascal Sancho wrote: The URL given in my previous mail was a bit out of topic: this was about TTC fonts usage. Here is the good one: list of changes in font subsystem. http://xmlgraphics.apache.org/fop/changes.html#Changes+to+the+Font+Subsystem Pascal Pascal Sancho a écrit : Hi Benson, What you need is implemented in FOP TRUNK. See [1] for further details. I'll close the bug since I cannot reproduce it in FOP TRUNK, but you feel free to reopen. [1] http://xmlgraphics.apache.org/fop/trunk/fonts.html#truetype-collections-metrics Pascal Benson Margulies a écrit : Please see bz https://issues.apache.org/bugzilla/show_bug.cgi?id=48481. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
To recap: apparently the problem was that for individual letters not available in a font, the wrong selection was made, resulting in the question mark (for missing letter) appearing. While this was apparently fixed, note that character-by-character is still not supported. Meaning, in "AXB", where X is a Japanese (or other) character not available in font Candara (or other), but available in MS PMincho, it will still display as a question mark. Change it to "A X B" and it should work. If your only issue is with Japanese text, this can easily be solved in the XSLT step (using codepoints ranges), in case you have this type of exceptional cases in your text. Good to know that the issue is solved, Pascal. -- Abel -- Pascal Sancho wrote: Hi Benson, What you need is implemented in FOP TRUNK. See [1] for further details. I'll close the bug since I cannot reproduce it in FOP TRUNK, but you feel free to reopen. [1] http://xmlgraphics.apache.org/fop/trunk/fonts.html#truetype-collections-metrics Pascal Benson Margulies a écrit : Please see bz https://issues.apache.org/bugzilla/show_bug.cgi?id=48481. On Mon, Jan 4, 2010 at 7:46 AM, Abel Braaksma wrote: Can you clarify? Because that's precisely what I wrote. Perhaps we have some misunderstanding on what the font-selection-strategy means and/or what "picked" means (who picks what by what criteria?). Can you provide a simple input (XML) output (XSL-FO) example that currently renders incorrectly, but which is a little bit more elaborate then the "A=E3=81=82" string example? I.e., how would you deal with the selection of the font and what do you expect FOP to do for you? Benson Margulies wrote: - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
The URL given in my previous mail was a bit out of topic: this was about TTC fonts usage. Here is the good one: list of changes in font subsystem. http://xmlgraphics.apache.org/fop/changes.html#Changes+to+the+Font+Subsystem Pascal Pascal Sancho a écrit : Hi Benson, What you need is implemented in FOP TRUNK. See [1] for further details. I'll close the bug since I cannot reproduce it in FOP TRUNK, but you feel free to reopen. [1] http://xmlgraphics.apache.org/fop/trunk/fonts.html#truetype-collections-metrics Pascal Benson Margulies a écrit : Please see bz https://issues.apache.org/bugzilla/show_bug.cgi?id=48481. On Mon, Jan 4, 2010 at 7:46 AM, Abel Braaksma wrote: Can you clarify? Because that's precisely what I wrote. Perhaps we have some misunderstanding on what the font-selection-strategy means and/or what "picked" means (who picks what by what criteria?). Can you provide a simple input (XML) output (XSL-FO) example that currently renders incorrectly, but which is a little bit more elaborate then the "A=E3=81=82" string example? I.e., how would you deal with the selection of the font and what do you expect FOP to do for you? Benson Margulies wrote: We don't want to specify fonts char-by-char, we want them picked. On Mon, Jan 4, 2010 at 7:35 AM, Abel Braaksma wrote: I'm under the impression that Benson means selection strategy based on availability. Suppose the "A" is available in Candara, but the other letters/symbols are not, and the needed font selection strategy is "character by character" then the result must be similar to what you wrote, but automatically so. According to http://xmlgraphics.apache.org/fop/trunk/fonts.html#selection this is not implemented yet. Note that "auto" (which is implemented) means "the selection criterion is implementation defined". For FOP that means (afaik) that word boundaries and element boundaries work and that the "largest portion of a text or word that's available in a particular font" will be chosen. In the example above, the Gothic font will be used, because that has the largest part of the word/text. Changing to "character-by-character" means that each character is considered individually. Naturally, if Candara would contain all capital letters only, choosing character-by-character in the following: A=E3=81=82 then the rendering with character-by-character would be equivalent with the following: A = E 3=81=82 Obviously, either this or the original example from Benson cannot be achieved with current means (unless you add some rather prolific XSLT 2.0 preprocessing, i.e., give it a list of fonts and do the selection strategy in the earlier processing step, using some home-brewed extension functions, which could be a possible alternative while waiting for the implementation). Cheers, Abel Jason Harrop wrote: I don't have a font called "MS Gothic" on my XP / Word 2007 PC, so i've used "Century Gothic" instead, but subject to that, and assuming the relevant fonts are available, isn't this just: A =E3=81=82 with a config such as: true cheers .. Jason - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
Hi Benson, What you need is implemented in FOP TRUNK. See [1] for further details. I'll close the bug since I cannot reproduce it in FOP TRUNK, but you feel free to reopen. [1] http://xmlgraphics.apache.org/fop/trunk/fonts.html#truetype-collections-metrics Pascal Benson Margulies a écrit : Please see bz https://issues.apache.org/bugzilla/show_bug.cgi?id=48481. On Mon, Jan 4, 2010 at 7:46 AM, Abel Braaksma wrote: Can you clarify? Because that's precisely what I wrote. Perhaps we have some misunderstanding on what the font-selection-strategy means and/or what "picked" means (who picks what by what criteria?). Can you provide a simple input (XML) output (XSL-FO) example that currently renders incorrectly, but which is a little bit more elaborate then the "A=E3=81=82" string example? I.e., how would you deal with the selection of the font and what do you expect FOP to do for you? Benson Margulies wrote: We don't want to specify fonts char-by-char, we want them picked. On Mon, Jan 4, 2010 at 7:35 AM, Abel Braaksma wrote: I'm under the impression that Benson means selection strategy based on availability. Suppose the "A" is available in Candara, but the other letters/symbols are not, and the needed font selection strategy is "character by character" then the result must be similar to what you wrote, but automatically so. According to http://xmlgraphics.apache.org/fop/trunk/fonts.html#selection this is not implemented yet. Note that "auto" (which is implemented) means "the selection criterion is implementation defined". For FOP that means (afaik) that word boundaries and element boundaries work and that the "largest portion of a text or word that's available in a particular font" will be chosen. In the example above, the Gothic font will be used, because that has the largest part of the word/text. Changing to "character-by-character" means that each character is considered individually. Naturally, if Candara would contain all capital letters only, choosing character-by-character in the following: A=E3=81=82 then the rendering with character-by-character would be equivalent with the following: A = E 3=81=82 Obviously, either this or the original example from Benson cannot be achieved with current means (unless you add some rather prolific XSLT 2.0 preprocessing, i.e., give it a list of fonts and do the selection strategy in the earlier processing step, using some home-brewed extension functions, which could be a possible alternative while waiting for the implementation). Cheers, Abel Jason Harrop wrote: I don't have a font called "MS Gothic" on my XP / Word 2007 PC, so i've used "Century Gothic" instead, but subject to that, and assuming the relevant fonts are available, isn't this just: A =E3=81=82 with a config such as: true cheers .. Jason - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: problem with fo:inline and fo:external-graphic, overflows
Hi, I cannot reproduce different behavior when using fo:block instead of fo:inline with provided material. You should be more explicit: actual XSL-FO code for both cases, and if possible actual image file used. However, I suspect you are using an old FOP version, can you check that? Note that FOP 0.95 conforms to the spec (see REC §6.6.5 - fo:external-graphic, at [1]), while FOP 0.2x doesn't: - actual size of the image is calculated regarding intrinsic image size and content-* size properties for the fo:e-g - if not directly available, the intrinsic size is calculated using the source resolution (see [2]) Usual script should be, assuming a lr-tb writing-mode: see also, for further details: REC §7.15.3 block-progression-dimension at [3] REC §7.15.4 content-height at [4] REC §7.15.5 content-width at [5] REC §7.15.7 inline-progression-dimension at [6] [1] http://www.w3.org/TR/xsl/#fo_external-graphic [2] http://xmlgraphics.apache.org/fop/0.95/graphics.html#resolution [3] http://www.w3.org/TR/xsl/#block-progression-dimension [4] http://www.w3.org/TR/xsl/#content-height [5] http://www.w3.org/TR/xsl/#content-width [6] http://www.w3.org/TR/xsl/#inline-progression-dimension HTH, Pascal lexa2009 a écrit : hello. i want to generate pdf with text and some images inside it. for example this part of fo sometext some text some text but when there must be a new page or new string fop does not make it and my image does not display correct in pdf (overflows visible area). if i use fo:block instead of fo:inline all is good, but i have to use fo:inline becouse if it is possible image must be displayed on the same string. thx:) - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Text of given font width
Hello, I need to programatically get a width of some text (word, specifically) in a given font, size and style, which will be generated in Apache FOP (version 0.95) PDF document. The problem is that I need to know, if given word will fit to a column with a known width, and if it won't - resize to a fitable size. So far I have used java.awt.FontMetrics.stringWidth() method for this, but it seems that Java AWT's and FOP's PDF renderer generate text of different sizes.
Re: Looking for help, including consulting, with font selection
Please see bz https://issues.apache.org/bugzilla/show_bug.cgi?id=48481. On Mon, Jan 4, 2010 at 7:46 AM, Abel Braaksma wrote: > Can you clarify? Because that's precisely what I wrote. Perhaps we have some > misunderstanding on what the font-selection-strategy means and/or what > "picked" means (who picks what by what criteria?). > > Can you provide a simple input (XML) output (XSL-FO) example that currently > renders incorrectly, but which is a little bit more elaborate then the > "A=E3=81=82" string example? I.e., how would you deal with the selection of > the font and what do you expect FOP to do for you? > > Benson Margulies wrote: >> >> We don't want to specify fonts char-by-char, we want them picked. >> >> On Mon, Jan 4, 2010 at 7:35 AM, Abel Braaksma >> wrote: >> >>> >>> I'm under the impression that Benson means selection strategy based on >>> availability. Suppose the "A" is available in Candara, but the other >>> letters/symbols are not, and the needed font selection strategy is >>> "character by character" then the result must be similar to what you >>> wrote, >>> but automatically so. According to >>> http://xmlgraphics.apache.org/fop/trunk/fonts.html#selection this is not >>> implemented yet. >>> >>> Note that "auto" (which is implemented) means "the selection criterion is >>> implementation defined". For FOP that means (afaik) that word boundaries >>> and >>> element boundaries work and that the "largest portion of a text or word >>> that's available in a particular font" will be chosen. In the example >>> above, >>> the Gothic font will be used, because that has the largest part of the >>> word/text. >>> >>> Changing to "character-by-character" means that each character is >>> considered >>> individually. >>> >>> Naturally, if Candara would contain all capital letters only, choosing >>> character-by-character in the following: >>> >>> A=E3=81=82 >>> >>> then the rendering with character-by-character would be equivalent with >>> the >>> following: >>> >>> A >>> = >>> E >>> 3=81=82 >>> >>> Obviously, either this or the original example from Benson cannot be >>> achieved with current means (unless you add some rather prolific XSLT 2.0 >>> preprocessing, i.e., give it a list of fonts and do the selection >>> strategy >>> in the earlier processing step, using some home-brewed extension >>> functions, >>> which could be a possible alternative while waiting for the >>> implementation). >>> >>> Cheers, >>> Abel >>> >>> >>> Jason Harrop wrote: >>> I don't have a font called "MS Gothic" on my XP / Word 2007 PC, so i've used "Century Gothic" instead, but subject to that, and assuming the relevant fonts are available, isn't this just: A =E3=81=82 with a config such as: true >>> weight="normal"/> >>> weight="normal"/> cheers .. Jason >>> >>> - >>> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org >>> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org >>> >>> >>> >> >> - >> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org >> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org >> >> >> >> > > - > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > > - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
I see how I misunderstood your email. I will get you a test case. On Mon, Jan 4, 2010 at 7:46 AM, Abel Braaksma wrote: > Can you clarify? Because that's precisely what I wrote. Perhaps we have some > misunderstanding on what the font-selection-strategy means and/or what > "picked" means (who picks what by what criteria?). > > Can you provide a simple input (XML) output (XSL-FO) example that currently > renders incorrectly, but which is a little bit more elaborate then the > "A=E3=81=82" string example? I.e., how would you deal with the selection of > the font and what do you expect FOP to do for you? > > Benson Margulies wrote: >> >> We don't want to specify fonts char-by-char, we want them picked. >> >> On Mon, Jan 4, 2010 at 7:35 AM, Abel Braaksma >> wrote: >> >>> >>> I'm under the impression that Benson means selection strategy based on >>> availability. Suppose the "A" is available in Candara, but the other >>> letters/symbols are not, and the needed font selection strategy is >>> "character by character" then the result must be similar to what you >>> wrote, >>> but automatically so. According to >>> http://xmlgraphics.apache.org/fop/trunk/fonts.html#selection this is not >>> implemented yet. >>> >>> Note that "auto" (which is implemented) means "the selection criterion is >>> implementation defined". For FOP that means (afaik) that word boundaries >>> and >>> element boundaries work and that the "largest portion of a text or word >>> that's available in a particular font" will be chosen. In the example >>> above, >>> the Gothic font will be used, because that has the largest part of the >>> word/text. >>> >>> Changing to "character-by-character" means that each character is >>> considered >>> individually. >>> >>> Naturally, if Candara would contain all capital letters only, choosing >>> character-by-character in the following: >>> >>> A=E3=81=82 >>> >>> then the rendering with character-by-character would be equivalent with >>> the >>> following: >>> >>> A >>> = >>> E >>> 3=81=82 >>> >>> Obviously, either this or the original example from Benson cannot be >>> achieved with current means (unless you add some rather prolific XSLT 2.0 >>> preprocessing, i.e., give it a list of fonts and do the selection >>> strategy >>> in the earlier processing step, using some home-brewed extension >>> functions, >>> which could be a possible alternative while waiting for the >>> implementation). >>> >>> Cheers, >>> Abel >>> >>> >>> Jason Harrop wrote: >>> I don't have a font called "MS Gothic" on my XP / Word 2007 PC, so i've used "Century Gothic" instead, but subject to that, and assuming the relevant fonts are available, isn't this just: A =E3=81=82 with a config such as: true >>> weight="normal"/> >>> weight="normal"/> cheers .. Jason >>> >>> - >>> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org >>> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org >>> >>> >>> >> >> - >> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org >> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org >> >> >> >> > > - > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > > - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
Can you clarify? Because that's precisely what I wrote. Perhaps we have some misunderstanding on what the font-selection-strategy means and/or what "picked" means (who picks what by what criteria?). Can you provide a simple input (XML) output (XSL-FO) example that currently renders incorrectly, but which is a little bit more elaborate then the "A=E3=81=82" string example? I.e., how would you deal with the selection of the font and what do you expect FOP to do for you? Benson Margulies wrote: We don't want to specify fonts char-by-char, we want them picked. On Mon, Jan 4, 2010 at 7:35 AM, Abel Braaksma wrote: I'm under the impression that Benson means selection strategy based on availability. Suppose the "A" is available in Candara, but the other letters/symbols are not, and the needed font selection strategy is "character by character" then the result must be similar to what you wrote, but automatically so. According to http://xmlgraphics.apache.org/fop/trunk/fonts.html#selection this is not implemented yet. Note that "auto" (which is implemented) means "the selection criterion is implementation defined". For FOP that means (afaik) that word boundaries and element boundaries work and that the "largest portion of a text or word that's available in a particular font" will be chosen. In the example above, the Gothic font will be used, because that has the largest part of the word/text. Changing to "character-by-character" means that each character is considered individually. Naturally, if Candara would contain all capital letters only, choosing character-by-character in the following: A=E3=81=82 then the rendering with character-by-character would be equivalent with the following: A = E 3=81=82 Obviously, either this or the original example from Benson cannot be achieved with current means (unless you add some rather prolific XSLT 2.0 preprocessing, i.e., give it a list of fonts and do the selection strategy in the earlier processing step, using some home-brewed extension functions, which could be a possible alternative while waiting for the implementation). Cheers, Abel Jason Harrop wrote: I don't have a font called "MS Gothic" on my XP / Word 2007 PC, so i've used "Century Gothic" instead, but subject to that, and assuming the relevant fonts are available, isn't this just: A =E3=81=82 with a config such as: true cheers .. Jason - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
We don't want to specify fonts char-by-char, we want them picked. On Mon, Jan 4, 2010 at 7:35 AM, Abel Braaksma wrote: > I'm under the impression that Benson means selection strategy based on > availability. Suppose the "A" is available in Candara, but the other > letters/symbols are not, and the needed font selection strategy is > "character by character" then the result must be similar to what you wrote, > but automatically so. According to > http://xmlgraphics.apache.org/fop/trunk/fonts.html#selection this is not > implemented yet. > > Note that "auto" (which is implemented) means "the selection criterion is > implementation defined". For FOP that means (afaik) that word boundaries and > element boundaries work and that the "largest portion of a text or word > that's available in a particular font" will be chosen. In the example above, > the Gothic font will be used, because that has the largest part of the > word/text. > > Changing to "character-by-character" means that each character is considered > individually. > > Naturally, if Candara would contain all capital letters only, choosing > character-by-character in the following: > > A=E3=81=82 > > then the rendering with character-by-character would be equivalent with the > following: > > A > = > E > 3=81=82 > > Obviously, either this or the original example from Benson cannot be > achieved with current means (unless you add some rather prolific XSLT 2.0 > preprocessing, i.e., give it a list of fonts and do the selection strategy > in the earlier processing step, using some home-brewed extension functions, > which could be a possible alternative while waiting for the implementation). > > Cheers, > Abel > > > Jason Harrop wrote: >> >> I don't have a font called "MS Gothic" on my XP / Word 2007 PC, so >> i've used "Century Gothic" instead, but subject to that, and assuming >> the relevant fonts are available, isn't this just: >> >> >> A >> =E3=81=82 >> >> >> with a config such as: >> >> >> true >> >> >> >> >> > weight="normal"/> >> >> >> > weight="normal"/> >> >> >> >> >> >> >> cheers .. Jason >> >> >> > > - > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > > - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Looking for help, including consulting, with font selection
I'm under the impression that Benson means selection strategy based on availability. Suppose the "A" is available in Candara, but the other letters/symbols are not, and the needed font selection strategy is "character by character" then the result must be similar to what you wrote, but automatically so. According to http://xmlgraphics.apache.org/fop/trunk/fonts.html#selection this is not implemented yet. Note that "auto" (which is implemented) means "the selection criterion is implementation defined". For FOP that means (afaik) that word boundaries and element boundaries work and that the "largest portion of a text or word that's available in a particular font" will be chosen. In the example above, the Gothic font will be used, because that has the largest part of the word/text. Changing to "character-by-character" means that each character is considered individually. Naturally, if Candara would contain all capital letters only, choosing character-by-character in the following: A=E3=81=82 then the rendering with character-by-character would be equivalent with the following: A = E 3=81=82 Obviously, either this or the original example from Benson cannot be achieved with current means (unless you add some rather prolific XSLT 2.0 preprocessing, i.e., give it a list of fonts and do the selection strategy in the earlier processing step, using some home-brewed extension functions, which could be a possible alternative while waiting for the implementation). Cheers, Abel Jason Harrop wrote: I don't have a font called "MS Gothic" on my XP / Word 2007 PC, so i've used "Century Gothic" instead, but subject to that, and assuming the relevant fonts are available, isn't this just: A =E3=81=82 with a config such as: true cheers .. Jason - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
