You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Alex V. Alishevskikh" <al...@vismech.ru> on 2001/04/26 07:28:22 UTC
FOP 0.19-CVS tested with russian
Hi, there!
I have tested the CVS snapshot of FOP 0.19 (20010424105603 - last at
that time) with russian.
It is succesfully works with UTF-8 and Unicode truetype fonts without
any additional localization adjustments (the hyphenation patterns only).
My pleasure :-))
The hyphenation patterns now are accepted in UTF-8 as well, so there
isn't neccessary to reencode the files (to single-byte encoding) now.
The hyphenations are works as well too.
But there is still problems with cyrillic PS Type1 (pfb). This trouble
is a same as I've described at 16apr ("Problems with i18n and fonts at
FOP 0.18.1") and Tore Engvig's answer (17apr):
> 1) For embedding cyrillic Type1 I see whitespaces instead of cyrillic
> characters in output PDF. (without my mapping adjustment (i.e. just to
> use the native charlist.xml), I see the hashes "#").
(Tore)> I think it's possible to this but it would require some (a lot
of) manual work. I'm a little unsure about how to do it, but will look
at it.
Tore, what you think about where is this problems cause may be? I would
to have an attempt to resolve this things, 'cause I guess what Type1 is
better choice for professional typographics than TTF.
So, IMHO - this release is more i18n compliant and enough easy for
localization (as against the previous versions, required for the some
hackers actions ;-) This is just my initial opinion and I hope, I will
not change it at future :)
Thanks a lot!
P.S.
Russian hyphenation patterns file is attached to a separate message.
--
Best regards,
Alex "Achtung" Alishevskikh
[mailto:alex@vismech.ru]
Visual Mechanics Lab
http://www.vismech.ru
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: FOP 0.19-CVS tested with russian
Posted by Tore Engvig <te...@manamind.com>.
Sorry for taking so long to answer, but I've not had the opportunity until
now.
-----Original Message-----
From: Alex V. Alishevskikh [mailto:alex@vismech.ru]
Sent: Thursday, April 26, 2001 07:28
To: fop-dev@xml.apache.org
Subject: FOP 0.19-CVS tested with russian
*snip*
But there is still problems with cyrillic PS Type1 (pfb). This trouble
is a same as I've described at 16apr ("Problems with i18n and fonts at
FOP 0.18.1") and Tore Engvig's answer (17apr):
> 1) For embedding cyrillic Type1 I see whitespaces instead of cyrillic
> characters in output PDF. (without my mapping adjustment (i.e. just to
> use the native charlist.xml), I see the hashes "#").
(Tore)> I think it's possible to this but it would require some (a lot
of) manual work. I'm a little unsure about how to do it, but will look
at it.
Seems like I was a little to quick there... It's not possible today, but
it's relatively easy to change fop so it's possible.
The font class implementing the type 1 font (ie a subclass of
SingleByteFont) would have to override the mapChar method to return the
correct mapping for the font. It would also have to return a correct
encoding in the encoding method (encoding using /Differences I think).
To enable encoding using /Differences I suppose you would have to change the
toPDF method in the PDFFont class.
All this could of course be handled by adding the correct encoding in the
fonts metric.xml file (ie by adding bfentries the same way as with truetype
cid fonts) and implementing this in the SingleByteFont class.
Then the problem is to read the encoding from the fontfile. pfm files
doesn't contain the encoding. There is a byte (or int?) in the pfm file to
indicate encoding, but I've no idea what the different numbers mean. I guess
that the encoding attribute in the pfm files wouldn't suffice anyway because
many fonts probably don't use a preregistered encoding. The only way to get
correct encoding is to read the .pfb file. If you want to create a PFBReader
you're more than welcome :)
While we're at it: this would only work for singlebyte type 1 fonts. The big
Type0 CJK fonts are still unsupported. So if you're really ambitious, a
converter from type1 (and type 0) to opentype fonts would be a nice thing :)
Tore
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org