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

Re: Encoding: Referring people to a list of labels

From: Andrew Cunningham <lang.support@gmail.com>
Date: Mon, 27 Jan 2014 23:14:00 +1100
Message-ID: <CAGJ7U-W7B6dC-qpOC_PjCBvaS7dXL3PB7UE6mW-MHpwox4pRuQ@mail.gmail.com>
To: Henri Sivonen <hsivonen@hsivonen.fi>
Cc: www-international@w3.org
On 27/01/2014 10:20 PM, "Henri Sivonen" <hsivonen@hsivonen.fi> wrote:
> On Mon, Jan 27, 2014 at 11:35 AM, Andrew Cunningham
> <lang.support@gmail.com> wrote:

> If the character-to-glyph mapping of a writing system is trivial
> enough for it to be feasible to use @font-face and to commandeer e.g.
> the Latin-1 Supplement (whether encoded in UTF-8 or windows-1252) or
> to use the PUA (in UTF-8), then it is feasible to use the right code
> points with @font-face without the browser having special support for
> those code points (yes, even if the right code points are on astral
> planes).

There are a whole range of assumptions there that do not always hold true.

Legacy fonts using glyph based  encodings may involve 1 to many and many to
one relationships with Unicode codepoints. In Unicode the glyphs may need
to be reordered or repositioned or be rendered with required ligatures.

Although 8-bit encodings and pseudo-Unicode encodings don't need complex
rendering the Unicode require complex rendering. Sometimes this will
require opentype support,  sometimes it may require graphite support when
opentype support isn't sufficient at the time.

If I add the need for syllable or word boundary itentification for line

Most browsers still have a long way to go.


> --
> Henri Sivonen
> hsivonen@hsivonen.fi
> https://hsivonen.fi/
Received on Monday, 27 January 2014 12:14:32 UTC

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