w3c / eurlreq

European language enablement
7 stars 3 forks source link

Georgian uppercase transforms fail #30

Open r12a opened 2 years ago

r12a commented 2 years ago

This issue is applicable to modern Georgian.

Dedicated mtavruli Unicode characters were only introduced in Unicode v11 (2018). Prior to that, authors had to use special fonts with the mkhedruli code points in order to write mtavruli letters, and CSS text-transforms (ie. to uppercase) had no effect. Unicode 11 introduced not just the new characters, but also mappings from mkhedruli (lowercase) to mtavruli (uppercase).

This was particularly problematic in pages that are translations of content that was originally in the Latin script, and which applied CSS text-transforms to some text. Prior to Unicode11, there was no need to remove the CSS styling from translated pages, since no text-transform had any effect. Post Unicode 11, however, the mapping to mtavruli characters was being applied and tends to produce tofu.

This situation lead Chrome and Firefox in 2018 to add workarounds to their browsers that prevented the conversion of Mkhedruli characters to Mtavruli when using CSS text-transform:uppercase. (Conversion from Mtavruli to Mkhedruli works, however.) This workaround is still in place, even though there is now better support for Mtavruli in pre-installed fonts on both the Mac and Windows platforms.

Note that Mtavruli is only used for ALL CAPS typography, and is not used at the beginning of a sentence or for proper nouns, so this only affects the uppercase value of text-transform.

Specs: css-text-3 describes the text-transform property. There is no information specifically relating to Georgian.

Tests & results: i18n test suite, Georgian mkhedruli/mtavruli

Results for all uppercase conversion tests:

For information about font support for Mtavruli characters, see https://github.com/w3c/eurlreq/issues/19

Browser bug reports: GeckoBlink

Priority: Basic priority applied because, although Mtavruli characters are only used for ALL CAPS, there is no reason that Georgian users should be forced to use uppercase code points rather than using a transform.

r12a commented 2 years ago

The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the document. Proposals for changes or discussion of the content can be made in comments below this point.

Relevant gap analysis documents include: Georgian