You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by "Jesiolowski, Dominik" <Do...@domdata.com> on 2005/02/08 09:06:05 UTC
Re: Embedding Type 1 Polish font - Bayesian Filter detected spam
Hello!
Thanks for your answer.
> -----Original Message-----
> From: J.Pietschmann [mailto:j3322ptm@yahoo.de]
> Sent: Monday, February 07, 2005 11:03 PM
> To: fop-user@xml.apache.org
> Subject: Re: Embedding Type 1 Polish font - Bayesian
>
>
> [...]
> Are you sure you are using the correct codes?
I think I am. Have a look here:
http://www.eki.ee/letter/chardata.cgi?lang=pl+Polish&script=latin
> Other possible causes of problems should have resulted in error
> messages:
> - If the font file doen't have a unicode table, you should have
> gotten a notification. You have to generate the metrics for such
> fonts with the winansiencoding flag.
I do not get anny errors or warnings while running FOP, but I don't think
the font has a unicode table. The file generated by PFMReader contains:
[...]<encoding>UnknownEncoding</encoding>[...]. I tried to change this to
WinAnsiEncoding but the result is the same :(
If you want you can look at the files I am processing
(.fo, .pfb, .pfm, .pdf) here:
http://cygnus.et.put.poznan.pl/~djes/fop/
Regards
Dominik
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: Embedding Type 1 Polish font - Bayesian Filter detected spam
Posted by Victor Mote <vi...@outfitr.com>.
J.Pietschmann wrote:
> > I do not get anny errors or warnings while running FOP, but I don't
> > think the font has a unicode table. The file generated by
> PFMReader contains:
> > [...]<encoding>UnknownEncoding</encoding>[...]. I tried to
> change this
> > to WinAnsiEncoding but the result is the same :(
>
> Dealing with PFM fonts is more tricky than with TTF. I defer
> to the experts.
I also will defer to the experts, but my recollection is that FOP 0.20.5
doesn't support any encodings but Adobe Standard and ISO Latin 1, neither of
which AFAICT handles the required Polish characters mentioned. Best way to
tell for sure is to open the output from PFMReader and see what it was able
to do.
The standard Type 1 files don't have anything resembling the Unicode tables
in TrueType fonts. I haven't delved into the multibyte Type 1 formats enough
to know how they are handled there, but FOP doesn't handle those formats
anyway. Best bet for FOP 0.20.5 is probably to use a TrueType font, but then
you have to live with the encoding limitations there (either WinAnsi or
underlying text is scrambled).
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Embedding Type 1 Polish font - Bayesian Filter detected spam
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Jesiolowski, Dominik wrote:
> I do not get anny errors or warnings while running FOP, but I don't think
> the font has a unicode table. The file generated by PFMReader contains:
> [...]<encoding>UnknownEncoding</encoding>[...]. I tried to change this to
> WinAnsiEncoding but the result is the same :(
Dealing with PFM fonts is more tricky than with TTF. I defer to the
experts.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
RE: Embedding Type 1 Polish font - Bayesian Filter detected spam
Posted by Victor Mote <vi...@outfitr.com>.
Jeremias Maerki wrote:
> in WinAnsiEncoding. The real problem is that FOP currently
> doesn't contain a parser for PFB or PFA files that could
> parse the character map. I don't know if Victor Mote could
> use the font with his PFB parser in FOray.
If it is a standard Type 1 font file, FOray should be able to parse it, but
doesn't yet know how to reencode it for the PDF. If it is a CFF file, FOray
would probably say that it doesn't recognize the format.
Victor Mote
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Embedding Type 1 Polish font - Bayesian Filter detected spam
Posted by Jeremias Maerki <de...@greenmail.ch>.
The problem is that the PFB file defines an encoding that differs from
WinAnsiEncoding in several characters. FOP only supports Type1 fonts
which have an unchanged WinAnsiEncoding or Symbol encoding (if I
remember correctly).
In your PDF you see the "oacute" character which is in the
WinAnsiEncoding, but you don't see "nacute", for example, which the PFB
file maps to code point 241 which is "ntilde" in WinAnsiEncoding. The
real problem is that FOP currently doesn't contain a parser for PFB or
PFA files that could parse the character map. I don't know if Victor
Mote could use the font with his PFB parser in FOray.
Anyway, you're out of luck with this font in FOP and you will have to
find a TrueType equivalent of your font so you get proper Unicode
support.
On 08.02.2005 09:06:05 Jesiolowski, Dominik wrote:
>
> Hello!
> Thanks for your answer.
>
> > -----Original Message-----
> > From: J.Pietschmann [mailto:j3322ptm@yahoo.de]
> > Sent: Monday, February 07, 2005 11:03 PM
> > To: fop-user@xml.apache.org
> > Subject: Re: Embedding Type 1 Polish font - Bayesian
> >
> >
> > [...]
> > Are you sure you are using the correct codes?
>
> I think I am. Have a look here:
> http://www.eki.ee/letter/chardata.cgi?lang=pl+Polish&script=latin
>
> > Other possible causes of problems should have resulted in error
> > messages:
> > - If the font file doen't have a unicode table, you should have
> > gotten a notification. You have to generate the metrics for such
> > fonts with the winansiencoding flag.
>
> I do not get anny errors or warnings while running FOP, but I don't think
> the font has a unicode table. The file generated by PFMReader contains:
> [...]<encoding>UnknownEncoding</encoding>[...]. I tried to change this to
> WinAnsiEncoding but the result is the same :(
>
> If you want you can look at the files I am processing
> (.fo, .pfb, .pfm, .pdf) here:
> http://cygnus.et.put.poznan.pl/~djes/fop/
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org