Re: Error when using XSL with French Characters
Hi, Andreas Delmelle wrote: On Sep 3, 2008, at 18:35, Steffanina, Jeff wrote: Hi Jeff There is always one MORE option to consider!! What would you suggest as the best way to handle this? I think I'd opt for using (N)umeric (C)haracter (R)eferences. Reasoning would be that if one changes the BASIC code to emit the sequence '#xE8;', this will never, ever have to be changed (unless Unicode would somehow decide on altering the codepoints). You can change the encoding in the XML header all you want, NCRs will always work. On the other hand, if you have a LOT of those characters, using NCRs could make your XML a bit bulky (instead of 1 byte/character, you Not mentioning the fact that this would make the document really tedious to type, and not very readable... actually generate 6-8 bytes to represent one character in the final result; the XML parser, instead of needing only one byte, has to parse all bytes from '' up to and including ';'). The character code you mentioned earlier (130) is the decimal value for 'é' in ASCII, so if you're concerned with the size of the XML and do not want to generate 6 bytes for one character, try specifying US-ASCII as encoding for the source XML. No, US-ASCII is a 7-bit character set, which means it can contain only 128 characters, none of them being an accented letter [1]. From your other message it looks like the default character set on your system is ISO-8859-15, which is ok for all of the western languages plus a few more [2]. Your BASIC program probably uses that character set, in which case you just have to change the header of your xml file: ?xml version=1.0 encoding=ISO-8859-15? As long as you put the right header in the XML file you can live with that setup. However, it is safer to switch to UTF-8 now, in order to avoid troubles in the future. Indeed, it’s probable that when you change your computer or upgrade your system the default character set will become UTF-8. Then if you re-edit that file on the new system, accented letters will be entered as UTF-8 sequences that are incompatible with ISO-8859-15, and you’ll basically see garbage in the result. Unless your editor is elaborate enough to recognize that the file is xml, and parses the header to get its encoding. But I doubt many editors do that... You can choose to convert your files to UTF-8 later on, but that might represent a lot of work, plus you will have to edit every file to change the xml header to UTF-8. Since the use of UTF-8 as the default charset will happen sooner or later, you better do that now, when you don’t have too many files. Changing the default character set is very system-dependent. Basically you have to play with the LOCALE variable. You can (may) get a list of available locales by typing the following command in a terminal: $ locale -a C en_US.iso885915 en_US.utf8 ... If no UTF-8 locale is available it must be generated. Try to find documentation for your system or ask the system administrator if applicable... You find that complicated? It is, it has always been, and I’m afraid it may forever be. This is historical... [1] http://en.wikipedia.org/wiki/Ascii [2] http://en.wikipedia.org/wiki/ISO/IEC_8859-15 HTH, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FOP 0.94 : How to increase heap size
Hi there! Could you please assist me how can I increase JVM heap size? Please let me know what I have to modify in FOP.BAT file so that it can take automatically whenever I run FOP from command prompt. When I am trying to convert XML to PDF using FOP, it's showing java.lang:OutofMemory Java heap space error. Would appreciate your prompt response! With Thanks! Newkid -- View this message in context: http://www.nabble.com/FOP-0.94-%3A-How-to-increase-heap-size-tp19309290p19309290.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FOP 0.94 : How to increase heap size
http://xmlgraphics.apache.org/fop/0.94/running.html#memory Eric Amick Legislative Computer Systems Office of the Clerk -Original Message- From: Newkid [mailto:[EMAIL PROTECTED] Sent: Thursday, September 4, 2008 10:25 To: fop-users@xmlgraphics.apache.org Subject: FOP 0.94 : How to increase heap size Hi there! Could you please assist me how can I increase JVM heap size? Please let me know what I have to modify in FOP.BAT file so that it can take automatically whenever I run FOP from command prompt. When I am trying to convert XML to PDF using FOP, it's showing java.lang:OutofMemory Java heap space error. Would appreciate your prompt response! With Thanks! Newkid -- View this message in context: http://www.nabble.com/FOP-0.94-%3A-How-to-increase-heap-size-tp19309290p 19309290.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
error creating ttf metrics
ciao, ttf reader give an error with a barmeno font... with all other fonts it works fine... the same ttf file works with TTFReader for fop 0.20.5 any idea? here the debug info... TTF Reader for Apache FOP 0.95 Parsing font... Reading Barmeno-Bold.ttf... sfnt version: OpenType 1.0 Reading 14 dir tables dir tables: [loca, post, glyf, fpgm, kern, hmtx, hhea, prep, cvt , OS/2, cmap, name, head, maxp] unit per em: 1000 Number of glyphs in font: 399 hhea.Ascender: 865 865 hhea.Descender: -250 -250 Number of horizontal metrics: 399 PostScript format: 0x2 PostScript format 2 Reading 396 glyphnames, that are not in the standard Macintosh set. Total number of glyphs=399 sTypoAscender: 776 776 sTypoDescender: -243 -243 sTypoLineGap: 150 usWinAscent: 953 953 usWinDescent: 250 250 Error while building XML font metrics file. java.io.EOFException: Reached EOF, file size=88952 offset=88958 at org.apache.fop.fonts.truetype.FontFileReader.seekSet(FontFileReader.java:86) at org.apache.fop.fonts.truetype.FontFileReader.seekAdd(FontFileReader.java:99) at org.apache.fop.fonts.truetype.FontFileReader.skip(FontFileReader.java:109) at org.apache.fop.fonts.truetype.TTFFile.readOS2(TTFFile.java:1016) at org.apache.fop.fonts.truetype.TTFFile.readFont(TTFFile.java:495) at org.apache.fop.fonts.apps.TTFReader.loadTTF(TTFReader.java:209) at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:164) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error when using XSL with French Characters
On Sep 4, 2008, at 12:06, Vincent Hennebert wrote: snip / No, US-ASCII is a 7-bit character set, which means it can contain only 128 characters, none of them being an accented letter [1]. Ouch! Indeed. I'm so used to the basic 7-bit set being extended... To think that I even tried it over here in an editor. If I had only also tried to actually save the file, I would have noticed... Sorry for the confusion, Jeff. The conclusion is definitely the right one: if you can somehow manage to have the BASIC code write the file as UTF-8, all the encoding hassles disappear. Cheers Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
