- From: Andrew Cunningham <andj.cunningham@gmail.com>
- Date: Thu, 7 Sep 2017 12:35:17 +1000
- To: "Michael A. Peters" <mpeters@domblogger.net>
- Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <CAOUP6KkK=wN7mnZa1K92YHWnRF2k7_DTonVeSFPhox8MP8x_-g@mail.gmail.com>
Language tag and locale tag are two different things for different purposes. Both use BCP47. Although language tags don't need the -u- extension. In your example the country code is irrelevan in terms of glyph selection in a font. The only significant part of tag is the 'en' subtag which would match either default OT script or a specific OT language system. And an OT language system is not the se as either a locale or language tag. Andrew On Thursday, 7 September 2017, Michael A. Peters <mpeters@domblogger.net> wrote: > Browser language settings include locale, e.g. en-US vs en-GB etc. > > On 09/06/2017 01:38 PM, Andrew Cunningham wrote: > >> >> >> On Wednesday, 6 September 2017, Michael A. Peters >> <mpeters@domblogger.net <mailto:mpeters@domblogger.net>> wrote: >> >> Don't need to map to a different glyph based on locale. Plenty of >> localization scripts exist for software. >> >> >> >> Selecting a glyph in a font would be based on language not on locale. >> >> Although if a cvNN feature was available in a font you could modify a >> localisation script to change the css to target a specific glyph. >> >> But considering potential font fallback issues ... using a textual label >> can be problematic. >> >> Andrew >> >> >> >> >> -- >> Andrew Cunningham >> andj.cunningham@gmail.com <mailto:andj.cunningham@gmail.com> >> >> > > -- Andrew Cunningham andj.cunningham@gmail.com
Received on Thursday, 7 September 2017 02:35:41 UTC