How does a language tag reach the font's 'locl' glyph substitutions and OpenType language-system tables, and where can that link silently break?
OpenType 1.9.1 defines 'locl' as localized glyph forms that should always be applied and be driven by language metadata that selects a language-system (LangSys) table; language-system tags are typographic-convention tags, not language codes, and a run uses the specific LangSys or the script default, not both. CSS Fonts 4 requires renderers to derive the OpenType language system from the content language, keeps locl on by default, and provides font-language-override for cases where the font lacks the language; unknown override tags are silently ignored. HarfBuzz documents that shaping input is a (direction, script, language) triple per run with BCP 47 language tags, and activates locl by default. The three layers state their strength differently (OpenType 'may', CSS 'required', HarfBuzz API parameter).
Structured fields
{
"citations": [
{
"url": "https://learn.microsoft.com/en-us/typography/opentype/spec/features_ko",
"note": "candidate evidence excerpts"
},
{
"url": "https://learn.microsoft.com/en-us/typography/opentype/spec/languagetags",
"note": "candidate evidence excerpts"
},
{
"url": "https://learn.microsoft.com/en-us/typography/opentype/spec/chapter2",
"note": "candidate evidence excerpts"
},
{
"url": "https://www.w3.org/TR/css-fonts-4",
"note": "cited at https://www.w3.org/TR/css-fonts-4/; candidate evidence excerpts"
},
{
"url": "https://github.com/harfbuzz/harfbuzz/blob/3f9ee71433c6324719c4fe0bb843d4c193d0b5f7/docs/usermanual-buffers-language-script-and-direction.xml",
"note": "candidate evidence excerpts"
},
{
"url": "https://github.com/harfbuzz/harfbuzz/blob/3f9ee71433c6324719c4fe0bb843d4c193d0b5f7/docs/usermanual-opentype-features.xml",
"note": "candidate evidence excerpts"
},
{
"url": "https://github.com/harfbuzz/harfbuzz/blob/3f9ee71433c6324719c4fe0bb843d4c193d0b5f7/docs/usermanual-shaping-concepts.xml",
"note": "candidate evidence excerpts"
},
{
"url": "https://www.w3.org/TR/css-fonts-4/",
"note": "observed URL (dated/alias form of the cited catalogue source; canonical identity retained)"
}
]
}Evidence claims
- [sourced_fact] OpenType 1.9.1 defines 'locl' as localized glyph forms that should always be applied and be driven by language metadata that selects a language-system (LangSys) table; language-system tags are typographic-convention tags, not language codes, and a run uses the specific LangSys or the script default, not both. CSS Fonts 4 requires renderers to derive the OpenType language system from the content language, keeps locl on by default, and provides font-language-override for cases where the font lacks the language; unknown override tags are silently ignored. HarfBuzz documents that shaping input is a (direction, script, language) triple per run with BCP 47 language tags, and activates locl by default. The three layers state their strength differently (OpenType 'may', CSS 'required', HarfBuzz API parameter). · locator: candidate evidence excerpts source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |
Linked records
- cites → https://github.com/harfbuzz/harfbuzz/blob/3f9ee71433c6324719c4fe0bb843d4c193d0b5f7/docs/usermanual-buffers-language-script-and-direction.xml
- cites → https://github.com/harfbuzz/harfbuzz/blob/3f9ee71433c6324719c4fe0bb843d4c193d0b5f7/docs/usermanual-opentype-features.xml
- cites → https://github.com/harfbuzz/harfbuzz/blob/3f9ee71433c6324719c4fe0bb843d4c193d0b5f7/docs/usermanual-shaping-concepts.xml
- cites → https://learn.microsoft.com/en-us/typography/opentype/spec/chapter2
- cites → https://learn.microsoft.com/en-us/typography/opentype/spec/features_ko
- cites → https://learn.microsoft.com/en-us/typography/opentype/spec/languagetags
- cites → https://www.w3.org/TR/css-fonts-4