Hi, >From a quick look at your files, the problem seems to come from the encoding of your font which isn't recognized by the PFMReader. I'm not sure there is any workaround at the moment. The good news is that there is ongoing work to improve the font system, so your problem might be fixed quite soon. Other developers might have suggestions of what to do for now. For example, you may try to find a substitute TrueType font (you might be interested by the latex xft fonts).
Note for fop-devs: the mapping field of SingleByteFont is null because in the updateMapping() method, the call to getEncoding() returns "UnknownEncoding". I guess the LMRoman font uses some custom encoding (from the TeX world) the PFMReader can't deal with. HTH, Vincent kralik a écrit : > If I do this, problem seems to be the same :-( > My new config file: "http://o4c.wz.cz/FOP/myfop.xconf"; > PFB file: "http://o4c.wz.cz/FOP/lmr17.pfb"; is in conf folder > > > > Jeremias Maerki-2 wrote: >> Replace embed-url="&fop.home;/conf/lmr17.pfm" with >> embed-url="&fop.home;/conf/lmr17.pfb". The PFM only contains the font >> metrics. For embedding, you need the PFB. >> >> On 23.10.2006 16:07:58 kralik wrote: >>> Hello! >>> >>> >>> I have a problem with registering PFM (Type 1) fonts with latest FOP >>> Trunk. >>> >From file http://o4c.wz.cz/FOP/lmr17.pfm lmr17.pfm was succesfully >>> created >>> font metrics file http://o4c.wz.cz/FOP/lmr17.pfm lmr17.xml >>> >>> >>> This is the snapshot: >> <snip/> >>> <font metrics-url="&fop.home;/conf/lmr17.xml" kerning="yes" >>> embed-url="&fop.home;/conf/lmr17.pfm"> >>> >>> <font-triplet name="LMRoman17-Regular" style="normal" >>> weight="normal"/> >>> >>> </font> >>> >> <snip/> >> >> >> Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
