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

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

From: Glenn Adams <glenn@skynav.com>
Date: Wed, 11 Jan 2017 09:08:38 -0700
Message-ID: <CACQ=j+f7bwrKaPkYtKtjchSFU8WW_xcqkmX1Kx3fYnc48P_3SA@mail.gmail.com>
To: Tony Graham <tgraham@antenna.co.jp>
Cc: "www-xsl-fo@w3.org" <www-xsl-fo@w3.org>
thanks; that is a useful point of comparison

On Wed, Jan 11, 2017 at 7:55 AM, Tony Graham <tgraham@antenna.co.jp> wrote:

> On 11/01/2017 13:55, Glenn Adams wrote:
> ...
>
>>     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.
>>
>> this feature isn't implemented in FOP
>>
>
> It is in AH Formatter, which is what I was using:
>
> https://www.antennahouse.com/product/ahf64/ahf-fo11.html#fon
> t-selection-strategy
>
> But, as above, it made no difference in this case. It looks like SimSun
> covers the ASCII/halfwidth range of characters so, with or without
> 'font-selection-strategy="character-by-character"', 'Arial, SimSun'
> produces the desired result and 'SimSun, Arial' produces all SimSun
> glyphs.  See attached.
>
>
> Regards,
>
>
> Tony Graham.
> --
> Senior Architect
> XML Division
> Antenna House, Inc.
> ----
> Skerries, Ireland
> tgraham@antenna.co.jp
>
Received on Wednesday, 11 January 2017 16:09:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 January 2017 16:09:32 UTC