Re: FOP conversion font problems

Thanks for the links. I have read them. I will just have to transform
my XML into FO catching every character not in the base font set. I
will then put the character in <fo:inline> and indicate the font
family found in my userconfig.xml file. The bottom line is that the
characters not in the base font set are a wash. At least I can
display them correctly even if they cannot be searched.

I can only hope that the future will make it possible to go forward
rather than attempting at this point to "translate" my unicode back
into an ASCII equivalent. Until then, this is the best possible
transformation.

Mike F.


--- "J.Pietschmann" <j3322ptm@xxxxxxxx> wrote:
> Mike Ferrando wrote:
> > Ok, great. Now if only I knew what that meant.
> > 
> See
>   http://xml.apache.org/fop/faq.html#pdf-characters
> To elaborate: a glyph is what is shown on the monitor or the
> paper. A font basically provides a mapping from character codes
> to glyphs. If the font does not provide such a mapping for a
> certain character code, you are out of luck.
> You can use some other utility, for example the Windows font
> viewer, to confirm whether your font provides a glyph for a
> particular character or not.
> 
> BTW FOP specific question should be asked on the FOP user list.
> 
> > Am I supposed to add something to my command line or change my fo
> > coding? (Sorry, I just started using the FOP engine.)
> 
> Did you read
>   http://xml.apache.org/fop/fonts.html
> 
> J.Pietschmann
> 
> 
>  XSL-List info and archive: 
> http://www.mulberrytech.com/xsl/xsl-list
> 


__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list