On 20/04/2012 18:54, Glenn Adams wrote:

Hi Glenn,

it is best you create a bug at [1] to track this; you can upload attachments on the new bug; file it under the "Fop" product;

I'm not happy to encourage users on this list to open bugs before confirming there is a defect.

Everything I've read on this thread so far suggests this is a configuration issue. Metrics files are deprecated in FOP v1.0+

How to reference instead of embed is to add the embed-url attribute on the fonts elements and use the <referenced-fonts> element as described in [1]

Thanks,

Chris

[1] http://xmlgraphics.apache.org/fop/trunk/fonts.html#embedding


[1] https://issues.apache.org/bugzilla/

On Fri, Apr 20, 2012 at 5:55 AM, Jean-Philippe Courson <[email protected] <mailto:[email protected]>> wrote:

    Hi,

    I am trying to produce chinese PDFs not embedding fonts. I am
    using the SimSun font.

    When embedding the font, everything is fine. However, when trying
    to reference the font, FOP produced an invalid PDF, despite the
    Simsun font being installed on the machines were the PDF is
    produced and opened.

    I tried both auto-configuring the fonts and the old style, metric
    based manual font configuration:

    1) Auto-configured fonts:

    <fonts>
    <referenced-fonts>
    <match font-family=".*"/>
    </referenced-fonts>
    </fonts>
    <renderers>
    <renderer mime="application/pdf">
        ...
    <auto-detect/>

    The produced PDF shows # characters for every chinese symbol.

    2) Manually configured fonts:

    <renderers>
    <renderer mime="application/pdf">
        ...
    <fonts>
    <font
    metrics-url="file:///Users/jumal/Downloads/fop-1.0/SimSun.xml"
    kerning="yes">
    <font-triplet name="SimSun" style="normal" weight="normal"/>
    <font-triplet name="SimSun" style="normal" weight="bold"/>
    <font-triplet name="SimSun" style="italic" weight="normal"/>
    <font-triplet name="SimSun" style="italic" weight="bold"/>
    </font>

       a) Metric file generated with the default options:

            java -cp ... org.apache.fop.fonts.apps.TTFReader
    SimSun.ttf SimSun.xml

            The produced PDF can not be opened by Acrobat Reader which
    gives the following error message: "Cannot find or create the font
    'SimSun'. Some characters may not display or print correctly".

       b) Metric file generated with the -enc ansi options:

            java -cp ... org.apache.fop.fonts.apps.TTFReader -enc ansi
    SimSun.ttf SimSun.xml

            The produced PDF shows # characters for every chinese symbol.

    Having a look at
    http://xmlgraphics.apache.org/fop/trunk/fonts.html#truetype-metrics,
    and in particular:

    TTFReader [options]:
           ...
           • -enc ansi Creates a WinAnsi-encoded font metrics file.
    Without this option, a CID-keyed font metrics file is created. The
    table below summarises the differences between these two encoding
    options as currently used within FOP. Please note that this
    information only applies to TrueType fonts and TrueType collections:
Issue WinAnsi CID-keyed
    Usable Character Set      Limited to WinAnsi character set, which
    is roughly equivalent to iso-8889-1.  Limited only by the
    characters in the font itself.
Embedding the Font Optional. Mandatory. Not embedding the font
    produces invalid PDF documents.

    it looks like you need to use the -enc ansi to be able to
    reference a font. Does this mean that have to use WinAnsi
    (windows-1252) encoding for the input XML files?

    If it is the case, that would mean to produce for example chinese
    PDFs, you would have to embed the font, as windows-1252 cannot be
    used to encode chinese symbols.

    Am I missing something or the only way to produce chinese PDF is
    to embed the font with the font licensing costs it implies?

    Cheers,
    JP

    ---------------------------------------------------------------------
    To unsubscribe, e-mail:
    [email protected]
    <mailto:[email protected]>
    For additional commands, e-mail:
    [email protected]
    <mailto:[email protected]>




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to