RE: Why is FO(P) a superior model than what most proprietary tools propose
That's a big yes from me as well. Cheers Tim -Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED] Sent: Wednesday, 1 May 2002 15:50 To: [EMAIL PROTECTED] Subject: Re: Why is FO(P) a superior model than what most proprietary tools propose Patrick, If I read you right, I think the answer to that would be a resounding cry of Yes all round. You will certainly get one from me. What did you have in mind? Peter Patrick Lanphier wrote: I would agree with the last statement about a high performance commercial all Java FO-PDF. However, there is really no need. Would anybody be interested in working on FOP with payment leaving the licensing as is? This way everybody can benefit. Anybody with experience interested? The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
RE: [ANNOUNCEMENT] Fop 0.20.3 released
Thanks Christian - that's fixed it. I'm happy now. You can make your release. Seriously, sometimes I feel very stupid. Every other time I've had problems with versions I've looked in the examples and this time I didn't. Cheers Tim -Original Message- From: Christian Geisert [mailto:[EMAIL PROTECTED] Sent: Tuesday, 12 March 2002 21:06 To: [EMAIL PROTECTED] Subject: Re: [ANNOUNCEMENT] Fop 0.20.3 released Keen Tim wrote: Christian, I'm having problems with this (the third) and the second release candidate for 0.20.3, but not the first. Follow my thread Trouble with ZapfDingbats in fop-user for more info. Perhaps you can advise me also. There has been a change in in the font enconding from RC1 to RC2 (I think the patch *corrected* the enconding for the symbol fonts) Have a look at docs/examples/fo/fonts.fo Cheers Tim Christian The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
RE: Trouble with ZapfDingbats
Thanks for your help TJ. Can you, or anyone else, direct me to a resource where I can find the Unicode number for a unchecked box with a shadow in ZapfDingbats? I was using #113; prior to this problem with the second release candidate. FWIW I'm now trying to resolve it against the latest release candidate. Cheers Tim -Original Message- From: TJ Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, 6 March 2002 23:51 To: [EMAIL PROTECTED] Subject: Re: Trouble with ZapfDingbats Hi I recently had problems with ZapfDingbats in fop 20.3 The solution is to use the Unicode for the dingbat you wish to render - I was using: fo:inline font-family=ZapfDingbatsl/fo:inline which produced a filled-in circle character in 20.1, but rendered a pair of scissors in 20.3 The solution is to use: fo:inline font-family=ZapfDingbats#x25CF;/fo:inline which works fine in 20.3 Hope this helps TJ - Original Message - From: Keiron Liddle [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 06, 2002 4:48 AM Subject: Re: Trouble with ZapfDingbats I'm not sure what the problem is that you are having but ZapfDingbats works fine for me both on unix and windows NT. On 2002.03.06 00:35 Keen Tim wrote: I recently upgraded to the latest version of Fop (fop-0.20.3rc2) to take advantage of the changes to the attribute master-name and am now having problems with the ZapfDingbats font. Essentially my PDF doesn't recognise the font. Is anyone else experiencing the same problems? Is this a known problem? Am I missing something? Should I rollback to a previous version? Any help would be appreciated. Cheers The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
RE: [ANNOUNCEMENT] Fop 0.20.3 released
Christian, I'm having problems with this (the third) and the second release candidate for 0.20.3, but not the first. Follow my thread Trouble with ZapfDingbats in fop-user for more info. Perhaps you can advise me also. Cheers Tim -Original Message- From: Christian Geisert [mailto:[EMAIL PROTECTED] Sent: Tuesday, 12 March 2002 9:03 To: [EMAIL PROTECTED]; fop-dev@xml.apache.org Subject: [ANNOUNCEMENT] Fop 0.20.3 released Doh, sorry for the previous mail (don't know what happened..) Hi all, just in case someone hasn't noticed yet ;-) FOP 0.20.3 is finally available at http://xml.apache.org/dist/fop for downloading. The main reason for this release is the conformance to the XSL-FO Version 1.0 W3C Recommendation. Other changes include: - support for CMYK and embedded ICC profiles in jpeg images - support for EPS images - improved font encodings for native (Acrobat) fonts - i18n improvments for AWT viewer - support for letter-spacing - Polish, Greek, and Hungarian hyphenation - and of course a lot of bugfixes... Changes from previous Release Candidate (rc2): - added missing japanese resource for AWT viewer - fixed Markers - updated logkit from 1.0b4 to 1.0 Enjoy, Christian The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
RE: Trouble with ZapfDingbats
Thanks for all your help. I'm not sure what the problem is either. I followed the fop-user and fop-dev threads, and didn't notice anything that would cause a problem. Jay suggested I try loading the font's but I don't see that I should have to, as it is a base font mentioned on the fonts page in the documentation. I'm going to try the unicode example of TJ's when I get a chance (bloody deadlines). Maybe I can get rid of those scissors as well. My source XML uses a 'windows-1252' encoding so hopefully this doesn't affect the unicode value (I'm really dumb when talking about encodings). This encoding only works when I add xercesImpl.jar to the CLASSPATH. I tried changing the encodings and removing the latest erces archive , but had no joy. For now I've rolled back to the first release candidate of Fop 20.3 (Fop-0.20.3rc), which works as it did in the previous releases. Is there anything in this release that I should be aware of? I could have stayed with the previous release of Fop 20.2, but I had to change because the XSL spec had changed (master-name master-reference). FWIW I tried posting this to fop-dev as well but it doesn't seem to have made it there. Hopefully there are enough developers looking at this list (Keiron?). I've also set up a test with other fonts and saw that Symbol was also effected. If you want this test suite I'll happily send it. Cheers Tim -Original Message- From: TJ Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, 6 March 2002 23:51 To: [EMAIL PROTECTED] Subject: Re: Trouble with ZapfDingbats Hi I recently had problems with ZapfDingbats in fop 20.3 The solution is to use the Unicode for the dingbat you wish to render - I was using: fo:inline font-family=ZapfDingbatsl/fo:inline which produced a filled-in circle character in 20.1, but rendered a pair of scissors in 20.3 The solution is to use: fo:inline font-family=ZapfDingbats#x25CF;/fo:inline which works fine in 20.3 Hope this helps TJ - Original Message - From: Keiron Liddle [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 06, 2002 4:48 AM Subject: Re: Trouble with ZapfDingbats I'm not sure what the problem is that you are having but ZapfDingbats works fine for me both on unix and windows NT. On 2002.03.06 00:35 Keen Tim wrote: I recently upgraded to the latest version of Fop (fop-0.20.3rc2) to take advantage of the changes to the attribute master-name and am now having problems with the ZapfDingbats font. Essentially my PDF doesn't recognise the font. Is anyone else experiencing the same problems? Is this a known problem? Am I missing something? Should I rollback to a previous version? Any help would be appreciated. Cheers The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
Trouble with ZapfDingbats
I recently upgraded to the latest version of Fop (fop-0.20.3rc2) to take advantage of the changes to the attribute master-name and am now having problems with the ZapfDingbats font. Essentially my PDF doesn't recognise the font. Is anyone else experiencing the same problems? Is this a known problem? Am I missing something? Should I rollback to a previous version? Any help would be appreciated. Cheers Tim Keen Analyst Programmer WERD Project Dept of Natural Resources Mines 4th Floor, Mineral House 41 George St Brisbane QLD 4000 (07) 3224 2559 (ph) (07) 3224 7963 (fax) [EMAIL PROTECTED] The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
RE: Displaying characters in PDF
Thanks for your help Rainer. I'm fairly dumb when it comes to fonts. My problem is that I don't control the source of the character and I would expect that in most cases the characters that are a problem are in ANSI set from 127-255. From what you're saying I'll have to pre-parse the string and replace it with the matching character in Adobe. Is that right? Is there another way? Cheers Tim -Original Message- From: Rainer Garus [mailto:[EMAIL PROTECTED] Sent: Monday, 4 February 2002 4:30 To: [EMAIL PROTECTED] Subject: RE: Displaying characters in PDF If the standard fonts of FOP (Helvetica, Times, Courier, Symbol and ZapfDingbats) contains the character, then you do not use additional fonts. FOP use unicode. So you must insert the unicode value (code point) of the character in your fo file. If you mean with slanted apostrophe the character with the adobe font name quoteright the code point is 2019. This is a hexadezimal value. Using the iso-8859-1 encoding you have to insert the numeric character reference in your fo file, for example: fo:block font-family=Helvetica#x2018;text#x2019;/fo:block To find the code point of a character of the Helvetica font, you can search the adobe font name of the character in chapter C.1 of the pdf reference manual http://partners.adobe.com/asn/developer/acrosdk/DOCS/pdfspec.pdf and then use the adobe glyph list http://partners.adobe.com/asn/developer/type/glyphlist.txt Rainer Garus The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
Displaying characters in PDF
Hopefully someone can help me or at least point me in the right direction. My original problem was that I had a parse error because my xml had the character 0x92 (slanted apostraphe) in it. After using encoding=iso-8859-1 this problem went away. Now the character displays as a # in the PDF output. Ideally I'd like to have it displayed as it is meant to be. As the font I'm using sans-serif, which is probably Helvetica. That leaves me with a few questions: Does this base font support what I want? Should I use a different encoding? Do I have to do stuff with embedding fonts or font metrics to ensure PDF recognises this character? Cheers Tim Keen Analyst Programmer WERD Project Dept of Natural Resources Mines 4th Floor, Mineral House 41 George St Brisbane QLD 4000 (07) 3224 2559 (ph) (07) 3224 7963 (fax) [EMAIL PROTECTED] The information in this e-mail together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of review, disclosure, modification, distribution and/or publication of this e-mail message is prohibited. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.
