Greek Characters in Postscript Output
Hello User Group, we are currently in the process of porting our 0.20.5 FOP embed up to a more actual version 1.0/1.1 and wanted to aim for Postscript Output (currently we use the Java Renderer to print). So before we used TrueTpe Fonts enabling us to use i.e. alpha and omega characters in one standard font, i.e. Arial. Now with postscript, as far as i understand it, we can only use single-byte character encoded fonts, so we have a massively limited array of characters in comparison to True Type fonts. Do you have any solution to such a problem? We need to use Arial (could substitute with Base-14 Helvetica) and Verdana (or a lookalike). How would we achieve a font enabling these special characters? Thank you a lot in advance for any clues ou could give me. Best Regards Normen -- View this message in context: http://apache-fop.1065347.n5.nabble.com/Greek-Characters-in-Postscript-Output-tp40610.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: Drastic Performance Improvement by dropping xerces and xalan
Actually, we are using -xsl and -xml as input. Glenn Adams-2 wrote Personally, I support removing all XSLT functions from FOP, but I'm afraid that would cause many users to find it less useful. I think it was a serious architectural error to combine those functions in the first place, but that horse left the gate long ago. On Tue, May 13, 2014 at 4:18 AM, Peter lt; p.kullmann@ gt; wrote: We had some performance problems with fop and began to investigate. For a specific example document of about 400 pages fop took about 55 seconds on a server at a client. The same process was much faster in our own setting (taking about 11 seconds). What we found out is the following: - fop from the distribution (either 1.1 release or 1.2 snapshot) takes 55 seconds - fop from the suse package takes only 11 seconds The two configurations differ in the jars: The suse config does not include xercesImpl, xalan and serializer We are running java version 1.7.0_40 OpenJDK Runtime Environment (IcedTea 2.4.1) (suse-8.18.1-x86_64) OpenJDK 64-Bit Server VM (build 24.0-b50, mixed mode) So, removing these three libraries drastically improved performance for us. Can someone explain why this is so? Can I safely drop these jars? Best regards Peter -- View this message in context: http://apache-fop.1065347.n5.nabble.com/Drastic-Performance-Improvement-by-dropping-xerces-and-xalan-tp40586.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscribe@.apache For additional commands, e-mail: fop-users-help@.apache -- View this message in context: http://apache-fop.1065347.n5.nabble.com/Drastic-Performance-Improvement-by-dropping-xerces-and-xalan-tp40586p40597.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: PDF rendering (and SVG-in-PDF rendering) of Arabic fonts not working correctly with ligatures for many fonts
Arabic is not presently supported in SVG when using FOP. For direct FOP use (not SVG), then if you are using any version of FOP prior to FOP 1.1, Arabic is not supported. If you are using 1.1 or current dev build, then you are doing something wrong. You need to provide more details. On Wed, May 14, 2014 at 11:08 AM, Robert Gurol robert.gu...@signavio.comwrote: Hi all, for rendering PDF containing both Arabic text and SVG containing arabic text, I recently experimented with different fonts. Except for the Tahoma font (which I'd rather not use for its license restrictions), Arabic text is rendered without ligatures, i.e. the letters of words are displayed as if they were written alone, while Arabic demands they be rendered differently inside of words and at the beginning and end of words, so they apper connected like hand-written text. That even though most fonts I tried seem to work perfectly well with PNG transcoding (when registered with the GraphicsEnvironment beforehand), generating Arabic text as expected. The fonts I tried so far are Lateef, Scheherazade and (Wikipedia-used) Amiri. Amiri (Regular) contains almost all characters of the unicode character sets Arabic, Arabic Supplement, Arabic Presentation Forms A and Arabic Presentation Forms B. As far as I know, ArabicTextHandler tries to replace adjacent letters with the respective connected forms and annotates the characters (not: code points, alas) with the respective in-word-position information for the letter, and it is called in both PNG transcoding and SVG-in-PDF transcoding. However, PNG looks much better in all cases, the ligatures seem to work only there. Is this a known issue? If not, I will gladly provide more information and test resources. Regards, Robert
Re: Greek Characters in Postscript Output
You can use TrueType fonts with PostScript. Things changed a lot since 0.20.5 On 5/16/14, 12:17 PM, Normen wrote: Hello User Group, we are currently in the process of porting our 0.20.5 FOP embed up to a more actual version 1.0/1.1 and wanted to aim for Postscript Output (currently we use the Java Renderer to print). So before we used TrueTpe Fonts enabling us to use i.e. alpha and omega characters in one standard font, i.e. Arial. Now with postscript, as far as i understand it, we can only use single-byte character encoded fonts, so we have a massively limited array of characters in comparison to True Type fonts. Do you have any solution to such a problem? We need to use Arial (could substitute with Base-14 Helvetica) and Verdana (or a lookalike). How would we achieve a font enabling these special characters? Thank you a lot in advance for any clues ou could give me. Best Regards Normen -- View this message in context: http://apache-fop.1065347.n5.nabble.com/Greek-Characters-in-Postscript-Output-tp40610.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 - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
