W3C home > Mailing lists > Public > www-xsl-fo@w3.org > January 2017

Re: specifying fonts when latin and complex scripts are mixed together.

From: Tony Graham <tgraham@antenna.co.jp>
Date: Wed, 11 Jan 2017 13:19:46 +0000
To: www-xsl-fo@w3.org
Message-ID: <39c99974-6916-2dd6-7296-dd5a4dfe0b16@antenna.co.jp>
On 11/01/2017 12:45, Amick, Eric wrote:
> You could try
> <fo:block font-family=”SimSun, Arial”>
> Text
> </fo:block>

Almost, but not quite.

<fo:block font-family="Arial, SimSun">2015年12月</fo:block>

should work, since the FO Processor should look at each of the specified
font names in 'font-family' in turn to try to find a glyph [2]. Arial
(other than 'Arial Unicode MS') wouldn't be expected to contain the
ideographs, so it's unlikely that your version of Arial has them. The
formatter would then have to look in SimSun to find them.

To be doubly certain, you could add
'font-selection-strategy="character-by-character"' [2] so each character
is considered individually, but I couldn't get it to make any difference
in this example.

If you are using AH Formatter, you could configure the font settings [3]
in your Option Setting File to set the default font for, e.g., 'serif'
and 'sans-serif' fonts for the 'Latn' and 'Hans' scripts so that you
always get Arial, Times Roman, and SimSun just by using the generic font


Tony Graham.
Senior Architect
XML Division
Antenna House, Inc.
Skerries, Ireland

[1] https://www.w3.org/TR/xsl11/#font-selection-strategy
[2] https://www.w3.org/TR/xsl11/#font-family
[3] https://www.antennahouse.com/product/ahf64/ahf-optset.html#font-settings
Received on Wednesday, 11 January 2017 13:20:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:10:21 UTC