– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

Action Items

<addison> https://github.com/w3c/i18n-actions/issues

<addison> #170

<gb> Action 170 reserve two days worth of meetings at tpac (on aphillips) due 2025-05-22

<addison> close #170

<gb> Closed issue #170

<addison> #168

<gb> Action 168 add instructions on dark mode to i18n-editors (on xfq) due 2025-05-01

<addison> close #168

<gb> Closed issue #168

xfq: did #168

Info Share

addison: I attended the ARIA planning call
… to talk about their aria key shortcut
… which was an open issue that we had
… after reviewing with them I agree that their text was probably fine
… they don't need to do anything about the issue

WebNN to Completed

BCP 47 Extension T in the Choosing a Language Tag article (Fuqiao)

<addison> fuqiao: richard gave me some suggestion

<addison> ... any suggestions?

addison: I had some different ideas to suggest

<addison> https://github.com/w3c/i18n-drafts/pull/658/files

<gb> Pull Request 658 Mention BCP 47 Extension T (by xfq)

addison: you're trying to mention mention the thing and give an example but you're not trying to write an exhaustive treaties on the thing

addison: at least give a tag that one would actually use

r12a: ja-t-it is a very rarely used thing
… and it's very vague as to what it means
… so I suggested that xfq uses a transcription
… like uk-Latn-t-uk-cyrl
… and there's the m0 stuff
… which could be used if you want to specify which transcription

<addison> https://www.unicode.org/reports/tr35/dev/tr35.html#unicode-bcp-47-t-extension

addison: I'd almost point at the section in TR35, but that's not super clear either

xfq: TR35 is not easy to understand

<addison> https://deploy-preview-80--i18n-glossary.netlify.app/#g

addison: 'glyph' definition
… I intend to use the same definition in specdev

xfq: "You can think of a font as a collection of glyphs." is not accurate
… also includes encoding information, hinting instructions, etc.
… and metrics (kerning, ascenders/descenders, etc.)

[Discuss the Unicode code point styling]

addison: base.css has Unicode code point styling, and this file has it too
… I'll find and eradicate that

Sequences with variation selectors in string-search (Fuqiao)

w3c/string-search#24

<gb> Pull Request 24 Sequences with variation selectors (by xfq)

https://deploy-preview-24--w3c-string-search.netlify.app/#variation-selectors

<r12a> https://deploy-preview-24--w3c-string-search.netlify.app/#variation-selectors

r12a: you're using graphics for the character code names, you should use the large size rather than the small size for VS17 and VS 18

xfq: do you have a link to the large size images?

Variation Selectors Supplement block

<r12a> https://r12a.github.io/c/Variation_Selectors_Supplement/large/E0100.png

<addison> https://github.com/w3c/i18n-drafts/blob/gh-pages/articles/language-negotiation/language-negotiation.md

addison: one more piece of homework
… I'd like to finish off the language negotiation thing

addison: I'm a member of Unicode's Technical Coordinating Group
… the TCG is considering how to reorganize the specs that Unicode produces
… historically they've been technical reports stored on /reports on the Unicode website
… what would make sense from our perspective wrt referring to Unicode standards if there were more than just the character encoding related ones in the report space
… you can think of this like IETF I-Ds and RFCs and BCP and STD etc.

r12a: are these the UAX documents?

addison: UAXs, UTSs, and others
… should they all be UTSs? should they continue to be numbered sequentially?
… MessageFormat looks nice in Markdown and HTML, but it looks clunky when it gets merged into CLDR

r12a: I don't imagine that they would change the URLs for any of these
… but they might change the Unicode 17 content to include the UAXs