i18n support
Hi all I would like to know if FOP supports i18n. Can I embed Chinese characters in my XSL and export it to PDF? Thanks regards Kevin
Re: i18n support
Hi Jochen Thanks for your reply. I put some Chinese characters in an fo:block and I got this message: [ERROR]: An invalid XML character (Unicode: 0xa9) was found in the element content of the document. Any idea? Thanks regards Kevin On Fri, 28 Jun 2002 [EMAIL PROTECTED] wrote: Date: Fri, 28 Jun 2002 08:07:04 +0200 From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: i18n support I'm not 100% sure, but if you embed the chineese fonts i think you might get it done... Check the docs for how to embed the fonts... Jochen Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities. KBC Securities reserves the right to monitor all e-mail communications through its networks and any messages addressed to, received or sent by KBC Securities or its employees are deemed to be professional in nature. The sender or recipient of any messages to or of KBC Securities agrees that those may be read by other employees of KBC Securities than the stated recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof. KBC Securities does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of, or reliance on, the information. -- K
Re: i18n support
damned... i'll check around meanwhile did you check the message archive? ( http://marc.theaimsgroup.com) check as wel the fop-dev, and the fop-user mailing list... i'll check around to.. ok? i never use chineese characters but there must be a solution for it :D greetings Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities. KBC Securities reserves the right to monitor all e-mail communications through its networks and any messages addressed to, received or sent by KBC Securities or its employees are deemed to be professional in nature. The sender or recipient of any messages to or of KBC Securities agrees that those may be read by other employees of KBC Securities than the stated recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof. KBC Securities does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of, or reliance on, the information.
Re: i18n support
Hi, Kevin, I have used FOP to produce Chinese document with Chinese content in original XML, but have not tried embeded Chinese characters in the xsl. Make sure you have encoding correct in your xsl since the xsl itself should be valid XML document. In my case the XML document has encoding=Big5. ___ Jianbo Mao CheckFree i-Solutions Email: [EMAIL PROTECTED] Office: +44 (0) 1753 567896 Mobile: +44 (0) 7810 483974 Fax: +44 (0) 1753 567897 ___ |-+ | | Kevin Yeung | | | [EMAIL PROTECTED]| | | et.hk | | || | | 28/06/2002 07:28 | | | Please respond to| | | fop-user | | || |-+ -| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: i18n support | -| Hi Jochen Thanks for your reply. I put some Chinese characters in an fo:block and I got this message: [ERROR]: An invalid XML character (Unicode: 0xa9) was found in the element content of the document. Any idea? Thanks regards Kevin On Fri, 28 Jun 2002 [EMAIL PROTECTED] wrote: Date: Fri, 28 Jun 2002 08:07:04 +0200 From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: i18n support I'm not 100% sure, but if you embed the chineese fonts i think you might get it done... Check the docs for how to embed the fonts... Jochen Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities. KBC Securities reserves the right to monitor all e-mail communications through its networks and any messages addressed to, received or sent by KBC Securities or its employees are deemed to be professional in nature. The sender or recipient of any messages to or of KBC Securities agrees that those may be read by other employees of KBC Securities than the stated recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof. KBC Securities does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of, or reliance on, the information. -- K
Re: i18n support
Kevin, There are a number of things you need to do to get Chinese (or the characters of any language) to display in your PDF documents. 1. The encoding of your stylesheet, or FO document must match the encoding of the embedded characters. That means that if you are embedding chinese multi-byte characters in your document, you must put an encoding attribute on the stylesheet that matches the encoding used to create the multi-byte character (You seem to be using Big5, also available is UTF-8 etc.) I use ?xml version=1.0 encoding=UTF-8? 2. If you are using and XSL stylesheet to generate the FO, you need to make sure that the encoding is also passed through to the FO document (which may only exist in memory but you still need to pass the encoding) 3. You need to embed a font that will display that character. And the font must map the multi-byte character in the encoding to the character that you want. An alternative (which is how I do it because I got tired of wrestling with all the font character encoding issues) is to convert all of your multi-byte characters into unicode character entities. They can be found here: http://www.unicode.org/charts/ I use Microsoft word's save as web page feature to generate the entities. Chuck Paussa Kevin Yeung wrote: Hi all I would like to know if FOP supports i18n. Can I embed Chinese characters in my XSL and export it to PDF? Thanks regards Kevin
Re: i18n support
Kevin Yeung wrote: Thanks for your reply. I put some Chinese characters in an fo:block and I got this message: [ERROR]: An invalid XML character (Unicode: 0xa9) was found in the element content of the document. You have an encoding problem. This is a general XML issue, not specific to FOP. The encodsding in the XML declaration has to match the actual encoding in which the file is written to disk. If there is no encoding declared, the parser will almost always asssume UTF-8, and in this case U+00A9 maps to a control character which is not valid in any XML file. See XML declaration http://www.w3.org/TR/2000/REC-xml-20001006#sec-prolog-dtd Check the documentation for the editor you used to enter the chinese characters, declarae the encoding, and hope the parser understands it. If all else fails, look up th Unicode codepoints for the characters and enter them as character references using an ASCII editor. See character references http://www.w3.org/TR/2000/REC-xml-20001006#sec-references Unicode codepoints for chinese characters can be found somewhere on http://www.unicode.org/ J.Pietschmann
Hi all, the second Release Candidate for 0.20.3 (Maintenance release) is finally available at http://xml.apache.org/dist/fop for downloading and testing. There will be no new functionality added and if no new bugs show up FOP 0.20.3 will be released next week (target date is 27. Februar ;-) Changes from previous Release Candidate: - Proper use of font encodings for native fonts Submitted by: Peter S. Housel (housel@acm.org) and Rainer Garus (rainer.garus@arcor.de) - jimi.jar removed for license reasons - Added Printing from a servlet example Submitted by: Ralph LaChance Ralph_LaChance@compuserve.com - make sure label-end() value gets calculated (fix for bug #6094, endless loop while processing list-item-label)) - Improved i18n support for AWT viewer (Japanese dialogs) Submitted by: Satoshi Ishigami (ishigami@victokai.co.jp) - Generated text is written in UTF-8 encoding instead of ISO-8859-1 - MIF output strings escaping (see bug #1332) Submitted by: Vicente Salvador (vicentesalvador@netscape.net) - Fixed NoSuchElementException in MIF renderer (Christian Geisert) - Added Polish Hyphenation based on TeX hypenation Submitted by: Marcin Kuthan [M.Kuthan@elka.pw.edu.pl] - Added greek Hyphenation Submitted by: Dimitris Kamenopoulos el97146@mail.ntua.gr - Added hungarian Hyphenation Submitted by: Simon Geza simon@mail.drotposta.hu Just a reminder: This version has been updated to XSL 1.0 Recommendation syntax and requires JDK 1.2 or better. [ANNOUNCEMENT] Fop 0.20.3 released
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
