W3C home > Mailing lists > Public > www-style@w3.org > June 2016

RE: [css-fonts] font-language-override

From: Levantovsky, Vladimir <Vladimir.Levantovsky@monotype.com>
Date: Wed, 1 Jun 2016 08:35:39 +0000
To: Chris Lilley <chris@w3.org>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <f89b5f8dfa0c4c48ae3b07e959ebadbb@wob-maildb-04.agfamonotype.org>
On Tuesday, May 31, 2016 11:30 AM Chris Lilley wrote:

Let me amplify and restate these points:

On 2016-05-31 06:57, Andrew Cunningham wrote:
It would be fairly quick and easy for google to add support for font-language-override

Supporting font-language override would not only increase spec compliance, it would be the path of least effort

I am not sure why font-language-override is really needed, can’t a developer simply define a span with another language tag [the one which behavior one wants to mimic]? Won’t the end result be the same ?

Depending on complex mappings from @lang to OpenType lang is a lot of work, currently being done for you by font designers. This is a duplication of effort and a maintenance burden; just support font-language-override. It is there for a reason.

OpenType maintains its own language tag system where the mappings in most cases are 1:1 and in some cases are n:1, but I wouldn’t consider it a complex mapping – as far as user is concerned, there is always a straightforward mapping from a content language tag to the OT language tag. Changing the content language tag, e.g. by defining a span with a different tag, should do the trick.

Regards,
Vlad


--

Chris Lilley

@svgeesus

Technical Director, W3C Interaction Domain
Received on Wednesday, 1 June 2016 08:36:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:47 UTC