Re: unable to use afp:resource-level=external
Thansk a lot Peter and Julien. I changed the line from the AFPStreamer.java as you suggested and checked that it is working as expected. Thank you so much for your help. Best regards, Mrutyunjay - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: FOP 1.0 in the maven repository [was: Re: The Apache Software Foundation Announces Apache FOP Version 1.0]
You can find maven bundles at http://people.apache.org/~spepping/commons-1_4/xmlgraphics-commons-1.4-bundle.jar and http://people.apache.org/~spepping/fop-1_0/fop-1.0-bundle.jar. If you open the jar files as zip files, you will find pom.xml. For your convenience I extracted them as http://people.apache.org/~spepping/commons-1_4/pom.xml and http://people.apache.org/~spepping/fop-1_0/pom.xml. Simon On Mon, Aug 16, 2010 at 11:08:23PM -0700, user7474 wrote: Ognjen Blagojevic-5 wrote: On 23.7.2010 12:19, Simon Pepping wrote: We could install 1.0 manually to local repo, but it would be much easier to have it in Maven Central. I have added fop 1.0 to our local maven repository. Because of the fact that there is no pom.xml I have written one, is the following correct, especially the dependencies? project modelVersion4.0.0/modelVersion groupIdorg.apache.xmlgraphics/groupId artifactIdfop/artifactId version1.0/version urlhttp://xmlgraphics.apache.org/fop//url description Apache FOP (Formatting Objects Processor) is the world's first print formatter driven by XSL formatting objects (XSL-FO) and the world's first output independent formatter. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. Output formats currently supported include PDF, PCL, PS, AFP, TIFF, PNG, SVG, XML (area tree representation), Print, AWT and TXT. The primary output target is PDF. /description inceptionYear2010/inceptionYear mailingLists mailingList nameFOP Users List/name subscribefop-users-subscr...@xmlgraphics.apache.org/subscribe unsubscribefop-users-unsubscr...@xmlgraphics.apache.org/unsubscribe archivehttp://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users//archive /mailingList mailingList nameFOP Developer List/name subscribefop-dev-subscr...@xmlgraphics.apache.org/subscribe unsubscribefop-dev-unsubscr...@xmlgraphics.apache.org/unsubscribe archivehttp://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev//archive /mailingList mailingList nameFOP Commit List/name subscribefop-commits-subscr...@xmlgraphics.apache.org/subscribe unsubscribefop-commits-unsubscr...@xmlgraphics.apache.org/unsubscribe archivehttp://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-commits//archive /mailingList /mailingLists licenses license nameThe Apache Software License, Version 2.0/name urlhttp://www.apache.org/licenses/LICENSE-2.0.txt/url distributionrepo/distribution /license /licenses scm connectionscm:svn:http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/connection developerConnectionscm:svn:https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/developerConnection urlhttp://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/?root=Apache-SVN/url /scm organization nameApache Software Foundation/name urlhttp://www.apache.org//url /organization dependencies !-- XML Graphics -- dependency groupIdorg.apache.xmlgraphics/groupId artifactIdxmlgraphics-commons/artifactId version1.4/version /dependency dependency groupIdorg.apache.xmlgraphics/groupId artifactIdbatik-svg-dom/artifactId version1.7/version /dependency dependency groupIdorg.apache.xmlgraphics/groupId artifactIdbatik-bridge/artifactId version1.7/version /dependency dependency groupIdorg.apache.xmlgraphics/groupId artifactIdbatik-awt-util/artifactId version1.7/version /dependency dependency groupIdorg.apache.xmlgraphics/groupId artifactIdbatik-gvt/artifactId version1.7/version /dependency dependency groupIdorg.apache.xmlgraphics/groupId artifactIdbatik-transcoder/artifactId version1.7/version exclusions exclusion groupIdorg.apache.xmlgraphics/groupId artifactIdfop/artifactId /exclusion /exclusions /dependency dependency groupIdorg.apache.xmlgraphics/groupId artifactIdbatik-extension/artifactId version1.7/version /dependency dependency groupIdorg.apache.xmlgraphics/groupId artifactIdbatik-ext/artifactId version1.7/version /dependency !-- other dependencies -- dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version /dependency dependency groupIdcommons-io/groupId artifactIdcommons-io/artifactId
Re: font variance across platforms?
Hi Trevor, ZapfDingbats is one of the base 14 PDF fonts and the character you are using (U+260E) belongs to its default encoding. Therefore it should be supported by any compliant PDF viewer. I’ve just checked on my own system and it works. What do you mean exactly by “not seeing the correct symbol”? If it’s a telephone symbol that looks different to the one you see in Adobe Reader, then that’s normal. Viewers are free to use any glyph they want, as long as it looks like “a black telephone”. If what they get is not a black telephone, then something is likely to be wrong with their setup. If you want the very same glyph to be displayed on every system, then you have to embed a particular font of your choice that supports the characters you need. It doesn’t have to be a Dingbats font, it can be any font that contains the appropriate glyphs (DejaVu Sans, for example). See here to configure custom fonts: http://xmlgraphics.apache.org/fop/1.0/fonts.html HTH, Vincent Trevor Nicholls wrote: Hi I am using fop 0.95. In a couple of locations my current document uses this: fo:character character=#x260E; font-family=ZapfDingbats / to insert a special character in the text. When I view the PDF in Adobe Reader on Windows I see the expected glyph (a telephone symbol), but I have been alerted to the fact that some users displaying this document under X-Windows on Linux are not seeing the correct symbol. How do I tell fop to embed the font (or at least the particular characters used in the document) so that the generated PDF is truly platform independent? Cheers Trevor - 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: font variance across platforms?
Hi Vincent The telephone glyph appears as a diamond superimposed on a diagonal cross. Another glyph I use (U+2709) as an email symbol appears as a large U. But I have discovered that these characters are being displayed correctly by Adobe Reader on Linux. The viewer with the problem is using Evince's document viewer. I see the same erroneous characters when I use that same viewer. It seems that this has ceased to be a fop issue - but thank you for the link you gave below. If we can't find out what is wrong with the Evince application I will give it a try. Cheers Trevor -Original Message- From: Vincent Hennebert [mailto:vhenneb...@gmail.com] Sent: Wednesday, 18 August 2010 10:43 p.m. To: fop-users@xmlgraphics.apache.org Subject: Re: font variance across platforms? Hi Trevor, ZapfDingbats is one of the base 14 PDF fonts and the character you are using (U+260E) belongs to its default encoding. Therefore it should be supported by any compliant PDF viewer. I’ve just checked on my own system and it works. What do you mean exactly by “not seeing the correct symbol”? If it’s a telephone symbol that looks different to the one you see in Adobe Reader, then that’s normal. Viewers are free to use any glyph they want, as long as it looks like “a black telephone”. If what they get is not a black telephone, then something is likely to be wrong with their setup. If you want the very same glyph to be displayed on every system, then you have to embed a particular font of your choice that supports the characters you need. It doesn’t have to be a Dingbats font, it can be any font that contains the appropriate glyphs (DejaVu Sans, for example). See here to configure custom fonts: http://xmlgraphics.apache.org/fop/1.0/fonts.html HTH, Vincent Trevor Nicholls wrote: Hi I am using fop 0.95. In a couple of locations my current document uses this: fo:character character=#x260E; font-family=ZapfDingbats / to insert a special character in the text. When I view the PDF in Adobe Reader on Windows I see the expected glyph (a telephone symbol), but I have been alerted to the fact that some users displaying this document under X-Windows on Linux are not seeing the correct symbol. How do I tell fop to embed the font (or at least the particular characters used in the document) so that the generated PDF is truly platform independent? Cheers Trevor - 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
Bug in 1.0?
In the attached FO and PDF files, I was expecting all the boldface numbers to be aligned, but they're not. Am I misunderstanding, or is this a bug? Eric Amick Systems Engineer II U.S. House of Representatives | Office of the Clerk | Legislative Computer Systems Office: 202-225-1182 http://clerk.house.gov http://clerk.house.gov/ Please consider the environment before printing this email. test.fo Description: test.fo test.pdf Description: test.pdf - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Default font?
It looks like my print preview and PDF are both using the custom font I selected. If I send a custom character as #x2611; which is not in my custom font, the print preview (AWTRenderer) looks like a checkbox while the PDF (PDFRenderer) shows a #. I want it to print a checkbox. Surely I'll have to add another custom font if my custom text font doesn't have this character. I'm just wondering why the 2 different outputs produce different results.
Another example
Here's a simpler example illustrating the problem in 1.0 I reported earlier. Eric Amick Systems Engineer II U.S. House of Representatives | Office of the Clerk | Legislative Computer Systems Office: 202-225-1182 http://clerk.house.gov http://clerk.house.gov/ Please consider the environment before printing this email. test.fo Description: test.fo test.pdf Description: test.pdf - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Special font chars
I'm trying to print a character to a PDF as #x25A1; which is supposed to be a square and it's printing a # character instead. The 25A1 character should be in my font. The PDF should be embedding LTYPE.TTF which comes with Windows XP.. Am I missing something or is FOP 1.0 missing something?
direction=rtl not available in fop-1.0?
I've been considering fop-1.0 to produce Hebrew text from XML files. Hebrew is a right-to-left language. I've embedded a Hebrew font and was already to see great results when .. direction=rtl fails to work. The suggested fix of using a fo:block-container with writing-mode=rl-tb fails to work also, although in a weird, pixel based mode. Or am I abusing fop-1.0 in some way? It seems incredible to limit the output to left-to-right languages. Thanks, Chris -- View this message in context: http://old.nabble.com/direction%3D%22rtl%22-not-available-in-fop-1.0--tp29475611p29475611.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: direction=rtl not available in fop-1.0?
Work is underway to add full support for complex scripts, including bidirectional writing, to FOP. A preliminary patch was posted at the following, however, please note that it is preliminary, incomplete, and has known issues. I expect this work will be fully completed within a few months and you shall then have full support for Arabic, Hebrew, Syriac, and other bidirectional scripts. https://issues.apache.org/bugzilla/show_bug.cgi?id=49687 I will post further information on this users list when the work is complete and integrated into the FOP 1.1dev trunk. Regards, Glenn Adams On Thu, Aug 19, 2010 at 4:19 AM, Chris Kimball m...@cvkimball.com wrote: I've been considering fop-1.0 to produce Hebrew text from XML files. Hebrew is a right-to-left language. I've embedded a Hebrew font and was already to see great results when .. direction=rtl fails to work. The suggested fix of using a fo:block-container with writing-mode=rl-tb fails to work also, although in a weird, pixel based mode. Or am I abusing fop-1.0 in some way? It seems incredible to limit the output to left-to-right languages. Thanks, Chris -- View this message in context: http://old.nabble.com/direction%3D%22rtl%22-not-available-in-fop-1.0--tp29475611p29475611.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
