Mike,
No, the characters seem to be pasted as images rather than characters.
The docs outline this problem (http://xml.apache.org/fop/fonts.html, see last paragraph), but when I use the -enc ansi option the PDF is way larger (because the whole font is embedded), but the russian characters don't show up (they're marked with # once again).
Here's how I tried to generate the font metrics file:
java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar;lib\xercesImpl.jar;lib\xalan.jar org.apache.fop.fonts.apps.TTFReader -enc ansi c:\winnt\fonts\L_10646.ttf lucida-sans-unicode-ansi.xml
The option for using winansi encoding is -enc ansi, but it doesn't seem to work on my PC. Please try at yours.
Johannes
| Mike Ferrando <[EMAIL PROTECTED]>
14.06.2003 14:39
|
|
Johannes,
Good to hear your workflow is back on track. I struggled with this
for a while but finally figured it out by reading the stuff in the
pdf guide and the web site (and fixing the errors in the code and
commandlines found therein).
I would like to know if the file you generated can be printed and
cut/paste and searched using Adobe Acrobat Reader?
Mike F.
--- Johannes Fiala <[EMAIL PROTECTED]> wrote:
> Mike,
>
> I'm astonished how fast and helpful your answer was.
>
> I found the font "Lucida Sans Unicode" which is part of the Win2K
> fonts
> and contains the necessary cyrillic font subset.
> Then I generated the necessary xml file for it and embedded the
> font in
> the userconfig.xml and - voila! the russian characters show up
> correctly!
>
> I wouldn't have thought that this is so easy!
>
> The only typo I found in the userguide is:
>
> http://xml.apache.org/fop/fonts.html#type1-metrics
>
> <font metrics-file="cyberbit.xml" kerning="yes"
> embed-file="C:\WINNT\Fonts\Cyberbit.ttf">
> <font-triplet name="Cyberbit" style="normal" weight="normal">
> </font>
>
> They forgot the trailing / at the end of the font-triplet tag, so
> this
> would throw a parsing exception.
>
> Thanks a lot for your support Mike,
> Johannes
>
>
>
>
> Mike Ferrando <[EMAIL PROTECTED]>
> 14.06.2003 06:16
> Please respond to
> [EMAIL PROTECTED]
>
>
> To
> [EMAIL PROTECTED]
> cc
>
> Subject
> Re: Using russian characters in FO-Files
>
>
>
>
>
>
> Johannes,
> The # indicates that the font you are using has no glyph for that
> character. You have to use a font that works with your characters.
> You can test this out by using MS Word and the character map. If
> you
> need to use a ttf font you will have to follow the directions for
> making an xml metrics file in your fonts.xml file at the apache fop
> site.
>
> I had the same problem.
> Mike F.
> Washington, DC
>
>
> --- Johannes Fiala <[EMAIL PROTECTED]> wrote:
> > Hi there,
> >
> > I tried to use russian characters (UTF-8 encoded) inside an FO
> > file.
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > ...
> > <fo:block language="ru" hyphenate="true">
> > russian characters:
> > ��� ���������� ������������ �����
> > �����, � �������� � ����� �������, � ������� ������� ����
> �������.
> > end russian characters
> > </fo:block>
> >
> > What I get after running the FOP test suite (I'm using
> > fop-0.20.5rc.) is
> > only "#" signs where the russian characters should be.
> > Other languages as Finnish or French are working.
> > Beneath %FOP_HOME%/hyph/ is a file ru.xml which should define the
> > russian
> > hyphenation characters I believe.
> >
> > I tried leaving the hyphenate parameter away and tried using
> > different
> > hyphenation settings, all without success.
> > Has anybody a hint want I am missing?
> >
> > thx alot
> > Johannes
> >
>
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
