Re: FOP 1.0 Japanese # marks
If I set this in my XSL stylesheet: xsl:param name=body.font.familySazanami/xsl:param Do I also need to set a mapping to Sazanami in the fop config file using metrics-url and embed-url as shown in http://xmlgraphics.apache.org/fop/1.0/fonts.html#register? Or can I just use auto-detect/ or directory to tell FOP where my fonts are? mike 675 wrote: Like this, maybe? xsl:param name=body.font.familySazanami/xsl:param mehdi houshmand wrote: Hi Mike, In the FO you are using Helvetica,Symbol,ZapfDingbats not Sazanami, you have to set the font name with the font-family attribute. Hope that helps Mehdi On 15 August 2011 10:37, mike 675 m_mcl...@yahoo.co.uk wrote: More details: The FontListMain utility shows that FOP can find the Japanese fonts on my computer (Red Hat 5.5): Sazanami Gothic: F137 [Sazanami Gothic, さざなみゴシック] Sazanami Gothic Regular,normal,400 Sazanami Gothic,normal,400 Sazanami-Gothic-Regular,normal,400 さざなみゴシック,normal,400 Sazanami Mincho: F138 [Sazanami Mincho, さざなみ明朝] Sazanami Mincho Regular,normal,400 Sazanami Mincho,normal,400 Sazanami-Mincho-Regular,normal,400 さざなみ明朝,normal,400 Here is my FOP config file: renderers renderer mime=application/pdf fonts auto-detect/ /fonts /renderer /renderers My FO file contains Japanese text, but has the standard font family settings: fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; text-align=left font-family=Helvetica,Symbol,ZapfDingbats font-size=10pt line-height=normal font-selection-strategy=character-by-character line-height-shift-adjustment=disregard-shifts writing-mode=lr-tb language=ja ... fo:block ホットキーに代わって、ホストキーが実装されました。 /fo:block The PDF export gives the following errors: Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ン (0x30f3, nkatakana) not available in font Helvetica-Bold. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph リ (0x30ea, rikatakana) not available in font Helvetica-Bold. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ス (0x30b9, sukatakana) not available in font Helvetica-Bold. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ノ (0x30ce, nokatakana) not available in font Helvetica-Bold. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph 発 (0x767a) not available in font Helvetica. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph 行 (0x884c) not available in font Helvetica. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph 日 (0x65e5) not available in font Helvetica. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph 年 (0x5e74) not available in font Helvetica. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph 月 (0x6708) not available in font Helvetica. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph パ (0x30d1, pakatakana) not available in font Helvetica. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ー (0x30fc, prolongedkana) not available in font Helvetica. Aug 15, 2011 10:36:13 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ト (0x30c8, tokatakana) not available in font Helvetica. Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph バ (0x30d0, bakatakana) not available in font Helvetica-Oblique. Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ー (0x30fc, prolongedkana) not available in font Helvetica-Oblique. Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ジ (0x30b8, zikatakana) not available in font Helvetica-Oblique. Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ョ (0x30e7, yosmallkatakana) not available in font Helvetica-Oblique. Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ン (0x30f3, nkatakana) not available in font Helvetica-Oblique. Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph リ (0x30ea, rikatakana) not available in font Helvetica-Oblique. Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ス (0x30b9, sukatakana) not available in font Helvetica-Oblique. Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Glyph ノ (0x30ce, nokatakana) not available in font Helvetica-Oblique. Aug 15, 2011 10:36:14 AM
Re: FOP 1.0 font cache: how long are fonts cached for?
On 15/08/2011 16:27, mike 675 wrote: Hi Mike, The FOP docs say that the fop font cache is on by default. How long are fonts cached for. Indefinitely. Searching for Fonts is a costly operation so it is only done if the cache file doesn't exist. What if I have a setting ofauto-detect/ to detect *all* fonts on my system. Then I change my fop config file to just use my own fonts: fonts directory/home/jdoe/temp/directory /fonts Are the system wide fonts from theauto-detect/ statement still held in cache? If you don't want to cache any fonts then why not disable it by setting use-cache setting to false as described here: http://xmlgraphics.apache.org/fop/1.0/configuration.html#general-elements Chris - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Multiple spaces
Hello, First of all, sorry for my poor english. I try to generate simple text. However, when I write multiple spaces or space before starting my text, everything is overwrited into a simple space (for multiple spaces) or erased (for my space before starting my text). For example, my text -a-b---c (with - as space ) is translated into a-b-c Do you know how can I keep my multiple spaces ? Thanks for you help, Morgan -- View this message in context: http://old.nabble.com/Multiple-spaces-tp32280005p32280005.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: FOP and large documents (again)
On Tue, Aug 16, 2011 at 04:23:47AM +0200, Stephan Thesing wrote: I would rather change the layout managers to produce KnuthElements in the way TeX does and leave page alignment to the page collection stage. I don't see another manageable way to do this but to add to the layout managers a new interface for this demand driven approach. Essentially, this would result in a parallel implementation of generating content to the getNextKnuthElements() and addAreas() interface. By demand driven do you mean that the page collection process requests Knuth elements from the layout managers? That seems the way to go indeed. You may come a long way, but it will be difficult to reproduce all details and pass all unit tests. OTOH, efforts that aimed at full compatibility have failed so far, so an effort which focuses on the target functionality first, and full compatibility later, may be the best strategy. PS: Is there any more in-depth documentation about the way the layout managers work apart from the Wiki Pages? Years ago I had documentation which was called DnI (Design and Implementation). I deleted it because it had become obsolete. It has quite a few details on the layout engine, and maybe some of it is still useful. You can find it in old revisions, e.g. http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/DnI/?pathrev=947983. It is based on docbook 4.2. You may have some trouble building it, because the Makefile still uses fop 0.20.5. Other documentation than that we do not have. Simon - 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 Japanese # marks
OK, I've solved this. It turns out that the new FOP 1.0 config parameters auto-detect/ and directory have no effect! I used an embed-url statement instead and FOP was able to use the Japanese font. mike 675 wrote: I used to use FOP 0.20.5 to build Japanese PDFs and they looked fine. Now after upgrading to FOP 1.0 the PDF build completes with no errors. But the PDF file is full of # marks. I am running on Red Hat 5.5. -- View this message in context: http://old.nabble.com/FOP-1.0-Japanese---marks-tp32244995p32282756.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
Open Source alternatives to Arial Unicode
I'm using Red Hat Linux 5.5. What are the best open source font alternatives to MS Arial Unicode for Japanese and Chinese (ZH-CN) PDF output? I have Japanese and Chinese font packs installed. The following fonts are Japanese, I think: Sazanami Mincho Sazanami Gothic These fonts are Chinese, I think: AR PL ShanHeiSun Uni AR PL ZenKai Uni Which of these should I use? -- View this message in context: http://old.nabble.com/Open-Source-alternatives-to-Arial-Unicode-tp32282826p32282826.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
