Meeting minutes
Agenda Review
Action Items
<addison> #150
<gb> Action 150 add string-search to i18n-editors and get an echidna token (on xfq) due 2024-12-19
xfq: Needs a first publicationication before. I'll get that. But publ moratorium until next year.
ACTION: fuqiao: request FPWD of string-search
<gb> Cannot create action. Validation failed. Maybe fuqiao is not a valid user for w3c/i18n-actions?
ACTION: xfq: request FPWD of string-search
<gb> Created action #152
<addison> #149
<gb> Action 149 add a banner to string-search (on aphillips) due 2024-12-19
<addison> close #149
<gb> Closed issue #149
<addison> #148
<gb> Action 148 propose specdev text related to design-principles#464 discussion (on aphillips) due 2024-12-12
<addison> #147
<gb> Action 147 Follow up on normativity warnings about glossary (on aphillips)
<addison> #145
<gb> Action 145 publish timezone for wide review (on aphillips) due 2024-11-28
<addison> close #145
<gb> Closed issue #145
<addison> #143
<gb> Action 143 make comments on the encoding issue attached to i18n-activity#1940 (on aphillips) due 2024-11-28
<addison> #135
<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
<addison> #127
<gb> Action 127 make a list of shared topics of interest between TG2 and W3C-I18N (on aphillips) due 2024-09-30
<addison> #89
<gb> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<addison> #7
<gb> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github) due 18 Jul 2023
<addison> #4
<gb> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on aphillips) due 27 Jul 2023
Info Share
JcK: IETF working on tag registry. Looking for a reviewer.
addison: I can.
JcK: Review for registries and registration forms.
RADAR Review
<addison> https://
addison: Incoming request for 7 VC specs.
… We reviewed them previously, they ask for a review of the changes, until February.
xfq: I can review them.
bert: no progress on Media Capabilities review
xfq: I looked at IDN Registry Restrictions.
addison: I'll move it to Completed.
… Will you write to them to say it was completed?
JcK: Please copy me
addison: I'm working in WebCodecs
Some WAI-ACT and MathML Core issues
<addison> https://
<addison> w3c/
<gb> Issue 573 ACT does not require that the language of text is indicated (by bert-github) [i18n-needs-resolution]
addison: Should have a general note about the need for language metadata.
Bert: OK, will ask for that.
<addison> also should note that the description should be localizable/able to appear in more than one language. can be just a note
<addison> w3c/
<gb> Issue 572 How are rule identifiers matched to one another? (by bert-github) [i18n-needs-resolution]
addison: They say *must* be unique. So maybe point to charmod-norm
Bert: OK, I will tell them.
<addison> https://
addison: Names have been there for a long time, haven't they? Maybe intorduce logical names later and dprecate these?
WASM
addison: There is a PR to address the issue.
<xfq> WebAssembly/
<gb> Issue 1843 Unicode identifiers in the WAT format (by xfq) [i18n-needs-resolution]
xfq: Issue I raised in November.
… They support arbitrary Unicode in identifiers via escaping
… I asked why not use the characters directly.
… Their answer is that they support identifiers with quotes and those allow Unicode.
… But idents without quotes need escapes.
… Has to do with interchange format and resource constraints.
addison: Unicode identifier thing is complicated.
… Another approach is XMLNames, i.e., a list of characters allowed.
… That's the approach in MessageFormat2.
… There is a list of chars. The list may be crappy.
… But in the real world it is not so bad.
JcK: As long as there no politics involved.
addison: Relatively simple to implement.
… That approach would be my suggestion.
… If you have to escape it, it is not very readable so not very useful in the source.
xfq: You can use the chars if you put quote marks around.
xfq: Seems good enough.
… They quoted UAX31.
addison: Quotes do not solve the problem of matching identifiers.
<addison> > The burden would be on all tools processing the Wasm text format, and is unlikely to get implemented on all, causing fragmentation. In contrast, to understand quoted identifiers, tools merely need to implement UTF-8 decoding, which is a few lines of code.
addison: I disagree with some of what rossberg wrote in the issue: ^^
… If you describe correctly how to parse the thing, the rules can be clear.
… They don't want to implement the Unicode identifier thing.
… It doesn't have to be hard to implement.
… So shall we accept, because they allow quoted identifiers?
JcK: I have no solution, but I hear many variations of the discussion.
<xfq> https://
xfq: Seems they have published a CR already.
<xfq> https://
<addison> https://
addison: Should not happen while issues are still open.
ACTION: addison: ask PLH what happened with wasm-2 CR since we have an issue open
<gb> Created action #153
<addison> #define "non-ascii" vs. #define ascii
JcK: Makes no sense to have an identifier in quotes.
addison: So they say if you have a non-ascii ident, you'll have to quote it, or escape.
<addison> here's how MF2 solves it: https://
xfq: What do you say about matching identifers?
addison: Once you allow non-ascii in idents, you'll have to define matching.
… I don't know if they defined that in the spec.
atsushi: Only little-endian, so no byte-encoding issues.
… But wondering about escaping and presentation forms.
addison: A smart editor could show the character and escape it only on writing the file. A dumb editor would show the escape.
atsushi: Don't think we can require that from an editor.
atsushi: Depends on how much we want to make things safe.
addison: We want to make the world more friendly for non-ascii stuff.
atsushi: We can ask them to write about possibility of editors or systems to handle escaping.
addison: Their identifiers can contain almost anything.
<Zakim> Bert, you wanted to agree that quoting is an acceptable solution.
<addison> bert: let it go? the quoting solution is acceptable. we do the same in css in some places
if whitespace is in the way, then you quote stuff
bert: I'd say quoting is an acceptable solution.
addison: I will write to plh to talk about the puvlication wghile an issue is still open,
… but I also propose to close the issue.
JcK: Rule-based identifiers generally require the XML names.
Plaintext guidance?
addison: It is not that simple...
<gb> Issue 10871 Undeprecate <plaintext>, it is needed for portable text files (by safinaskar) [i18n-tracker]
addison: Somebody proposed to bring back the <plaintext> tag in HTML.
… Maybe not a good idea.
… If you add tags before the plain text, then it is not plain text anymore.
xfq: MIME type?
JcK: MIME types have the necessary machinery.
addison: Yes, headers have a way to do this.
JcK: And as you say, if you include it in the text, it is not plain text anymore.
atsushi: Couldn't understand the issue.
addison: E.g., to make clear that a plain text is Chinese and not Japanese, so that it displayes correctly , at least in a browser.
atsushi: Can use something like innertext in JavaScript to import plain text.
addison: Seems they want to pass along some metadata with plain text. And <pre> in HTML would require some escaping.
AOB?
addison: But <plaintext> has security issues.
addison: Next two telcons cancelled. Next one on Jan 9