W3C home > Mailing lists > Public > public-tt@w3.org > July 2016

Re: Precedence in tts:fontFamily

From: Pierre-Anthony Lemieux <pal@sandflow.com>
Date: Thu, 7 Jul 2016 10:11:19 -0700
Message-ID: <CAF_7JxD+9SZMKmM9TwXa=1rQ3z3O1YnDydMJkqQTDA9poWn8_g@mail.gmail.com>
To: Glenn Adams <glenn@skynav.com>
Cc: "public-tt@w3.org" <public-tt@w3.org>
Hi Glenn,

> order definitely matters

Ok. Makes sense to me. I could not find a clear statement to that
effect in TTML1. Do you see one? If not, perhaps add one in the next
errata and updated TTML2 accordingly?

Best,

-- Pierre

On Thu, Jul 7, 2016 at 10:08 AM, Glenn Adams <glenn@skynav.com> wrote:
>
>
> On Thu, Jul 7, 2016 at 10:53 AM, Pierre-Anthony Lemieux <pal@sandflow.com>
> wrote:
>>
>> Hi all,
>>
>> (Hopefully) quick questions: (i) is the ordering of values in
>> tts:fontFamily significant and (ii) does familyName take precedence
>> over genericFamilyName?
>
>
> order definitely matters
>
>>
>>
>> For instance, are the following two declarations equivalent?
>>
>> tts:fontFamily="proportionalSansSerif,Arial"
>> tts:fontFamily="Arial,proportionalSansSerif"
>
>
> it depends; if proportionalSansSerif maps to Arial (on some implementation)
> then they would be equivalent (on that implementation)
>
>>
>>
>> ... and what is the expected outcome of the following?
>>
>> tts:fontFamily="proportionalSansSerif,proportionalSerif"
>
>
> if proportionalSansSerif maps to F1 and proportionalSerif maps to F2, and if
> the character maps (cmap tables) of both F1 and F2 define mappings for the
> same set of characters, then the above would be equivalent to:
>
> tts:fontFamily="proportionalSansSerif" or
> tts:fontFamily="F1"
>
>>
>>
>> Thanks,
>>
>> -- Pierre
>>
>
Received on Thursday, 7 July 2016 17:12:12 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:29 UTC