W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

Re: Encoding: Referring people to a list of labels

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 29 Jan 2014 12:59:15 -0800
Message-ID: <CADnb78jygTTnJMmsc+p8_UY6rJ88+HOVtAZ0ywF9HwFr4y74vg@mail.gmail.com>
To: Andrew Cunningham <lang.support@gmail.com>
Cc: Henri Sivonen <hsivonen@hsivonen.fi>, WWW International <www-international@w3.org>, John Cowan <cowan@mercury.ccil.org>, Asmus Freytag <asmusf@ix.netcom.com>
On Wed, Jan 29, 2014 at 4:18 AM, Andrew Cunningham
<lang.support@gmail.com> wrote:
> Firefox provides no UI to switch graphite support on and off.

Why do you need to switch it off? Per
https://bugzilla.mozilla.org/show_bug.cgi?id=700023 it has been
enabled by default for a while now.

> An added complication is that some of the graphite fonts I use
> are both graphite and opentype fonts with the graphite support being both
> more flexible and more powerful than the openrype implementations.
> Unfortunately the CSS folks chose to only support opentype fonts explicitly
> in the font modules. Some rules will work others will not.
> It is pot luck whether graphite is supported or unsupported. There is
> nothing the web developer can do.
> They have no control.
> Maybe the CSS cascade can be used to provide both rules for opentype and
> graphite features. But such an approach is problematic and awkward.

Sounds like we need more tests.

> The reality is that the browser developers choose what they want to
> implement.  There are lots of useful and crucial components in CSS that have
> not been implemented or widely implemented.
> Both Firefox and blink use hb-ng.  So both could use graphite shapers,  but
> blink developers are not interested.
> Come to think of it,  hb-ng is far from up to date in blink.
> There is a reluctance to address these issuses within specs,  and there is a
> reluctance to extend multilingual web support among web developers.
> At the moment guidelines are being developed here for the development and
> deployment of multilingual government information. Some of the languages our
> government publishes in are languages that either need pseudo-unicode fonts
> or graphite Unicode fonts.
> I am really tempted to take your comments at face value and make a
> recomendation that government websites in our juristIction only support
> Firefox.
> Begs the question should governments do that.
> If it was one website...  or a small community....  maybe....
> But...  even Firefox has a fair way to go before it is an ideal tool for
> multilingual web typography.

If nobody starts using graphite fonts, Blink will not have a reason to
support it.

Received on Wednesday, 29 January 2014 20:59:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:04 UTC