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

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

From: Myles C. Maxfield <mmaxfield@apple.com>
Date: Tue, 31 May 2016 23:16:06 -0700
Cc: www-style <www-style@w3.org>
Message-id: <DDF43CBE-6767-4844-80D6-BCFA6021F42E@apple.com>
To: Andrew Cunningham <lang.support@gmail.com>
The criterion for determining “at risk” is interoperable implementations. If you are hoping for vendors to implement this feature, I suggest filing (or commenting in existing) bugs in their respective bug trackers.

—Myles

> On May 30, 2016, at 10:22 PM, Andrew Cunningham <lang.support@gmail.com> wrote:
> 
> Hi all,
> 
> The current editors draft indicates that font-language-override feature is at risk.
> 
> This feature can be used with firefox, but not with other browsers.
> 
> Current support means we can use the Padauk or Noto Sans Myanmar for a range of languages in Firefox that can not be supported by the same font in other browsers. For instance if I need to support some of the other Karen languages using Sgaw Karen preferences, i can not currently rely on font-language-override suppot to handle this.
> 
> This forces us to hack the fonts in question making alternative language versions of the fonts where the default rendering is changed.
> 
> Reengineering fonts in this way is beyond the ability of the average web developer and browser developers should not be placing this burden on web developers.
> 
> If font-language-override is dropped from the spec, an alternative method exposing browsers default locl processing needs to be exposed to web developers, allowing web developers to override locl processing in some fashion.
> 
> Andrew
> 


Received on Wednesday, 1 June 2016 06:16:43 UTC

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