From fa489a755120427899d918eac470fd42fd13b211 Mon Sep 17 00:00:00 2001 From: Roger Sheen Date: Sat, 28 Jan 2017 17:22:25 +0100 Subject: [PATCH] Remove obsolete info, update PDF2 I18N for #46 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add related links: * DITA 1.3 spec on metadata cascade * @jelovirt’s “Font configuration in PDF2” post Signed-off-by: Roger Sheen --- parameters/lib-configuration-properties.dita | 80 +++++--------------- resources/external-links.ditamap | 9 +++ 2 files changed, 28 insertions(+), 61 deletions(-) diff --git a/parameters/lib-configuration-properties.dita b/parameters/lib-configuration-properties.dita index 3c58a997d..aaffffa53 100644 --- a/parameters/lib-configuration-properties.dita +++ b/parameters/lib-configuration-properties.dita @@ -39,16 +39,6 @@ requested on the commmand line via dita . - default.cascade @@ -100,62 +90,30 @@ org.dita.pdf2.i18n.enabled - (PDF transformation only) Enables I18N font processing. The following - values are allowed: + +

(PDF transformation only) Enables internationalization (I18N) font processing to provide per-character + font selection for FO renderers that do not support the font-selection-strategy property + (such as Apache FOP).

+

When this feature is enabled, DITA-OT uses a font mapping process that takes the content language into + consideration. The mapping process uses configuration files for each language to define characters that + should be rendered with certain logical fonts, and font mappings that associate each logical font to + physical font files.

+

The following values are allowed:

    -
  • (default) — Enables I18N processing
    • -
  • — Disables I18N processing
    • +
  • (default) — Enables font mapping
    • +
  • — Disables font mapping
- This needs beefing up. Here is info - provided by Jarno Elovirta: -

(IIRC, pre 1.0 versions of FOP didn't correctly implement font selection in XSL FO files, that's the - reason for this feature existing). The PDF2 I18N allows you to say define which characters are output - with which pseudo-font, and the font mapping files define the actual font. E.g. the configuration for - English at src/main/plugins/org.dita.pdf2/cfg/fo/i18n/en.xml - is: - <alphabet char-set="SymbolsSuperscript"> - <character-set> - <!-- Copyright --> - <character>&#169;</character> - <!-- Registered Trademark --> - <character>&#174;</character> - <!-- Trademark --> - <character>&#8482;</character> - <!-- Service mark --> - <character>&#2120;</character> - </character-set> - </alphabet> - <alphabet char-set="SubmenuSymbol"> - <character-set> - <character>&#x27A4;</character> - </character-set> - </alphabet> -

-

That is, those specific characters are marked as "SymbolsSuperscript" or "SubmenuSymbol" charset. The - font mappings at src/main/plugins/org.dita.pdf2/cfg/fo/font-mappings.xml then define which font to use - for them, - e.g.:<physical-font char-set="SymbolsSuperscript"> - <font-face>Helvetica, Arial Unicode MS</font-face> - <baseline-shift>20%</baseline-shift> - <override-size>smaller</override-size> - </physical-font>

-

The I18N processing is on by default (because it's been on before), but for most users it's just an - additional level of complexity which should be turned off and support for multiple languages be handled - in XSLT code.

- + If you don’t use custom character mappings, turning off font mapping makes it easier to + define custom fonts simply by changing font names in the XSL attributes files of your custom PDF plug-in. + For details, see . - + + + + + diff --git a/resources/external-links.ditamap b/resources/external-links.ditamap index 99b8d5ee8..a2daa12d0 100644 --- a/resources/external-links.ditamap +++ b/resources/external-links.ditamap @@ -321,5 +321,14 @@ Sass + + + Font configuration in PDF2 + +