I seem to have lost some markup somewhere. But the default fop.xconf has font metrics-url entries
mike 675 wrote: > > The default config file has an example that includes metrics... > > > <font-triplet name="Arial" style="normal" weight="normal"/> > <font-triplet name="ArialMT" style="normal" weight="normal"/> > > > <font-triplet name="Arial" style="normal" weight="bold"/> > <font-triplet name="ArialMT" style="normal" weight="bold"/> > > > > 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-tp32244995p32253068.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]
