Like this, maybe? <xsl:param name="body.font.family">Sazanami</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 <[email protected]> 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 org.apache.fop.events.LoggingEventListener >> processEvent >> WARNING: Glyph "モ" (0x30e2, mokatakana) not available in font "Courier". >> Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener >> processEvent >> WARNING: Glyph "ノ" (0x30ce, nokatakana) not available in font "Courier". >> Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener >> processEvent >> WARNING: Glyph "ス" (0x30b9, sukatakana) not available in font "Courier". >> Aug 15, 2011 10:36:14 AM org.apache.fop.events.LoggingEventListener >> processEvent >> WARNING: Glyph "ペ" (0x30da, pekatakana) not available in font "Courier". >> >> My PDF contains # throughout where Japanese glyphs should be. >> >> >> Eric Douglas wrote: >>> >>> You don't supply metrics in 1.0. >>> >>> >>> -----Original Message----- >>> From: mike 675 [mailto:[email protected]] >>> Sent: Friday, August 12, 2011 11:35 AM >>> To: [email protected] >>> Subject: RE: FOP 1.0 Japanese # marks >>> >>> >>> I see the config file format has changed from 0.20.5. >>> >>> 0.20.5 config file used these params: >>> embed-file >>> metrics-file >>> >>> 1.0 config file uses these params: >>> embed-url >>> metrics-url >>> >>> Am I on to something? >>> >>> >>> mike 675 wrote: >>>> >>>> It's the default fop.xconf file. I haven't made any changes or >>>> specified any fonts in there. >>>> >>>> Eric Douglas wrote: >>>>> >>>>> Yes and yes >>>>> Your FOP should have configuration telling it what fonts are >>> available. >>>>> Your XSLFO should have tags in it telling what font to use. >>>>> If you can provide more details about what you're doing someone may >>>>> provide more details about what you're missing. >>>>> Are you using fop.xconf file? What's that look like? >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: michael mclaughlin [mailto:[email protected]] >>>>> Sent: Friday, August 12, 2011 5:23 AM >>>>> To: [email protected] >>>>> Subject: Re: FOP 1.0 Japanese # marks >>>>> >>>>> Do you mean configure FOP 1.0 to use a Japanese font? >>>>> Or is there an XSL stylesheet option to do this? >>>>> Or do I manually edit the .fo file. >>>>> Thanks, >>>>> Mike >>>>> >>>>> >>>>> --- On Fri, 12/8/11, Sergiu Dumitriu <[email protected]> wrote: >>>>> >>>>>> From: Sergiu Dumitriu <[email protected]> >>>>>> Subject: Re: FOP 1.0 Japanese # marks >>>>>> To: [email protected] >>>>>> Date: Friday, 12 August, 2011, 2:03 >>>>>> On 08/11/2011 03:48 PM, 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. >>>>>> > >>>>>> > >>>>>> >>>>>> # usually means that the font is missing those characters. >>>>>> Make sure >>>>>> you've configured your FO to use a font that does cover the Japanese >>> >>>>>> Unicode range. >>>>>> >>>>>> -- >>>>>> Sergiu Dumitriu >>>>>> http://purl.org/net/sergiu/ >>>>>> >>>>>> -------------------------------------------------------------------- >>>>>> - 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] >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: >>>>> [email protected] >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/FOP-1.0-Japanese---marks-tp32244995p32251273.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] >>> >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/FOP-1.0-Japanese---marks-tp32244995p32263205.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] > > > -- View this message in context: http://old.nabble.com/FOP-1.0-Japanese---marks-tp32244995p32264294.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]
