w3c / amlreq Goto Github PK

Lowercase characters were introduced in Unicode 8.0, to cover growing use of bicameral content in modern typesetting, as well as some older texts such as the Cherokee New Testament. The lowercase text above is likely to be displayed as tofu (boxes), since it is currently difficult to find a font that includes lowercase forms.

The shapes of the upper- vs. lower-cased letters don't change radically (as they do in Latin or Cyrillic). The lowercase letters are often simply smaller, however they may have ascenders and descenders in some fonts.

Fonts that existed prior to Unicode 8.0 need updating to support lowercase characters.

Tests & results:

This page shows Mac and Windows OS pre-installed fonts that support Cherokee and tests them for lowercase support.

Mac OS X 10.15 has:

• Plantagenet Cherokee
• Galvji
• Geneva
• Noto Sans Cherokee

All except Plantagenet Cherokee support lowercase characters.

Windows 10 has:

• Plantagenet Cherokee
• Gadugi

Gadugi is the default installed font, and it supports lowercase letters. Plantagenet Cherokee does not.

Priority:
Marking this as advanced, since most of the pre-installed fonts do support the lowercase characters. For users of the Plantagenet font, font fallback should produce visible text (although it may not match well the uppercase letters).

This issue is applicable to most languages.

Vertical text may occur for special effects (the spine of a book, table column headings, etc). Typographically, it is simply horizontal text that is rotated. There is no way to do this effectively until browsers support the new CSS properties.

For more details, see this GitHub issue, which is being used to track this gap. Please add any discussion there, and not to this issue.

ᑖᓂᓯ! I work on making (Western) Cree syllabics more accessible on the web, and I can share my thoughts and experiences with you all. I'm not super sure how to do that, so I'm openning up this issue, and you can pester me about items labelled as "Needs Research".

One somewhat recent innovation in writing Cree syllabics is to use U+202F NARROW NO-BREAK SPACE as a morpheme separator. For example (see: https://crk-orthography.readthedocs.io/en/stable/#:~:text=Hyphens%20in%20Cree%20words).

This mirrors the hyphen's usage in the standard Roman orthography; e.g, ê-wâpamât is ᐁ ᐚᐸᒫᐟ in syllabics.

Why U+202F?

• it should render as visually thinner than U+0020 — preferablly U+0020 is as wide a full syllabic character, such as ᐃ, and U+202F should render half as wide as U+0020
• it should NOT be considered a space in word segmentation; indeed, using the Unicode Standard Annex #29§4.1 Default Word Boundary Specification, U+202F does not break words. IT also passes the "triple-click test"!
• precedent set in Mongolian orthography

This issue applies to all languages that use letter-spacing.

Currently browsers that apply letter-spacing do so by adding a space after every letter in the text that is tracked. This results in a superfluous space at the end of the range, which creates an inappropriate gap before the following text. Letter spacing at the end of a line makes the line look misaligned in justified or right-justified text. It also has implications for text that has other styling, such as an outline or a coloured background, at the same time as being stretched.

Example in German:

For more details, see this GitHub issue, which is being used to track this gap. Please add any discussion there, and not to this issue.

This issue is common across all languages that use the q element.

When an English page contains a quotation in another language, the quotation marks used around that quotation (and inside it for embedded quotes) should be the English ones – not those of the language of the quotation. The same applies for other languages.

Currently, if the language of the quotation is declared on the q tag in HTML and that tag has a lang attribute, browsers instead set the quotation marks based on the language of the quote.

For more details, see this GitHub issue, which is being used to track this gap. Please add any discussion there, and not to this issue.

CSS text transforms (uppercase, lowercase, capitalize) don't work on legacy Edge. However, they do now work on Gecko, Blink, and Webkit browsers, including the new Edge.

Tests & results:
i18n test suite, upper/lowercase transforms

i18n test suite, capitalization