I've never encountered a Type 1 font with russian characters before. When I implemented the PFM parser I therefore couldn't provide for any other character sets, especially since no others (except Korean, Chinese and Japanese) are mentioned in the PFM documentation. However, I imagine it is possible for a Type 1 font to contain more glyphs than are accessible through the standard encoding. The problem: These glyphs are defined in the AFM file of the Type 1 font which FOP can't parse, yet. It is possible that these AFM files will be readable for FOP when the new font subsystem is integrated. Efforts in this direction are underway.
In the meantime, you might want to use the TrueType variant of your font. On 05.12.2005 21:35:49 Andreas L Delmelle wrote: > On Dec 5, 2005, at 18:09, Pavel wrote: > > Hi, > > > I need embed Postscript - Type 1 fonts with russian characters. > > FOP 0.20.5 embedding fonts only with Encoding:Ansi > > and in pdf are # instead of russian characters > > (in generated xml font metric file is <encoding>WinAnsiEncoding</ > > encoding>). > > If I use these fonts in MSWord, russian characters are displayed OK. > > How can be set up correct encoding for Type 1 fonts? > > I hope someone else with more background knowledge about Type1 fonts > can offer any more feedback here, but AFAICT both FOP 0.20.5 and 0.90 > seem to extract this information directly from the PFM file itself... > They read a byte, and translate that to "WinAnsi" when it has value 0. > (see org.apache.fop.fonts.type1.PFMFile.getCharSetName()) > > Are you absolutely sure you're using the *exact* same font-file in > MSWord that you feed to the PFMReader? (and not a separate WinAnsi > encoded version?) Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
