OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] Entity -> fo -> pdf with a Unicode font..


Well, even though you found your own solution, at least now I know
where to look when I want to change the fonts.

Also, you now have a limited form of copy protection for your documents ;-]

On 9/26/06, Fredrik Svensson <fred@ludd.ltu.se> wrote:
> Great, send a mail and then you find the solution.
>
> The font xml file generated with org.apache.fop.fonts.apps.TTFReader
> was run with -enc ansi. That "Limited to WinAnsi character set, which is
> roughly equivalent to iso-8889-1." Without this option eg. CID-keyed
> the font work and the arrows appears!
>
> The penalty seems to be "Search, index, and cut-and-paste operations in the
> output document will produce incorrect results." but I hope it will not be too
> bad.
>
> Oops copy-paste generates characters like \U00100028  etc...
>
> Are there any other way ?
> The comment was "(FOP currently doesn't emit the /ToUnicode table which is
> necessary for copy/paste to work.)"
>
> The bug being
> http://issues.apache.org/bugzilla/show_bug.cgi?id=40467
> according to
> http://issues.apache.org/bugzilla/show_bug.cgi?id=5335
> there might be a solution in trunk
>
> Back to bleeding edge software testing.
>
> /Fred
>
> Fredrik Svensson wrote:
> > Hi,
> >
> > I have a document using two types of arrows.
> > Unicode characters :
> > 0x2192 ->   0x21db => (three lines)
> > The respective entities are
> > &rarr;  and &rAarr;
> >
> > I am using the FreeSerif font that have these two characters.
> > I have checked with Fontforge.
> > I have picked FreeSerif as the font to be used in the xsl
> >
> >   <xsl:param name="body.font.family">FreeSerif</xsl:param>
> >   <xsl:param name="title.font.family">FreeSerif</xsl:param>
> >   <xsl:param name="symbol.font.family">FreeSerif</xsl:param>
> >
> > The fo gets the following output when using saxon 8.7.3J :
> > <E2><86><92> Text <E2><87><9B>
> > (output from vi)
> > The fo is noted with
> > <?xml version="1.0" encoding="UTF-8"?> and for example  works in the pdf when
> > it is in fo denoted <C3><BC> that works also in pdf.
> >
> > But the arrows are displayed as hashes (#) in pdf.
> >
> > I use fop 0.92beta and including the font with a new configuration file which
> > has FreeSerif included
> >         <font metrics-url="FreeSerif.xml" kerning="yes"
> > embed-url="/usr/share/fonts/truetype/freefont/FreeSerif.ttf">
> >           <font-triplet name="FreeSerif" style="normal" weight="normal"/>
> >         </font>
> > fop.xconf in the fop distribution was used as a starting point.
> > (yes I generated the xml file myself with fop)
> >
> > Have had a look at
> > http://www.sagehill.net/docbookxsl/SpecialChars.html
> > but no tricks seems to get it to work.
> >
> > Do anyone have any hints ?
> >
> > I do hate fighting with the docbook tool chain ...
> > well I am using the free one so I guess I have to blame myself :)
> >
> > /Fred
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
>
>


-- 
http://chris.chiasson.name/


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]