Meeting minutes
Agenda Review
daniel: per attendee, ARIA-notify for next week
… safer
aria translatable attributes
<Daniel> w3c/
daniel: direction/lang attribute for translatable one
… detail in PR
xfq: brief background, relatively comment issue
… natural language string in aria description, but they don't have land/dir metadata
… since it's not possible to change attribute as element, so adding some text to spec document may be possible
addison: text mostly looks good, this is true thing over all attribute
… for language/dir metadata
… it's best you can do for this situation
… probably good to have note
daniel: thx xfq for putting good place for having note
addison: we may have additional one for lang/dir for some cases
… you might want to have something for rendering in a11y tech, such as attribute should be bidi isolated
… for rendering as text
daniel: these will be exposerd to a11y tree, so wondering how to apply for this specific case
eemeli: theoretical problem, or has been idenrified?
… number of cases on locale from current element would not be correct
… could not find any example whether is the exact issue
addison: common case is text localized along with original source language comment
eemeli: like page localized with partial non-localized text
addison: yes
<r12a> https://
r12a: theoretical, point of this kind of issue, link target, with title from target page in other language
… usually page author stick with title retrieved, but not align with language or localized at the page
addison: any next step? of course, we could have additional comment to the PR
daniel: discuss also next week, includig other points
[detail conversation on real examples/use cases]
addison: strong guidance is to use the same laguage for aria attribute as host content language and direction
… for displaying them correctly
… if not, opposite direction text would appear
addison: for direction, it's just for display purpose but not for like readout, so isolated shall be considered as default, and having some note could be better
Action Items
<addison> https://
<addison> #222
<gb> Action 222 Review dictionary proposal and draft response (on aphillips, r12a)
Info Share
addison: NSS in loading language
ah,, miss.ed in double fixing...
[character code in file systems]
<r12a> https://
r12a: had edited MDN ruby position document
… PR accepted recently for bcd table
Review RADAR Review
<addison> https://
addison: no new
Pending Issue Review
<addison> i18n-activity#2158
<gb> Issue 2158 Examples are USA-centric (by aphillips) [pending] [needs-resolution] [t:loc_examples_x] [wg:vc] [s:vc-recognized-entities]
addison: this document contains examples but mostly USA-centric ones
… editorial but need to be updated
[no objection]
<addison> i18n-activity#2159
<gb> Issue 2159 `legalName` does not permit a "language value object" (by aphillips) [pending] [needs-resolution] [t:bidi_strings] [t:lang_strings] [wg:vc] [s:vc-recognized-entities]
addison: VC for lang/dir metadata, but couple of issues remains, so asking them
<addison> i18n-activity#2160
<gb> Issue 2160 Show some non-ASCII/non-English examples and label the English (by aphillips) [pending] [needs-resolution] [t:loc_examples_x] [wg:vc] [s:vc-recognized-entities]
Jck: issue on domain name, no such attribute
PR Reviews
<addison> w3c/
<gb> PR 185 Add guidelines for writing examples (by aphillips) [Agenda+] [Best Practice] [normative]
<addison> https://
addison: added examples and new section at the end
<addison> https://
addison: rather than intermixing examples
xfq: had look last time, and seems good
r12a: should refer HTML instead of current ITS spec?
addison: could change
r12a: code elements are not translated in default
<r12a> https://
<addison> w3c/
<gb> PR 188 Refine string definitions and usage guidelines (by xfq)
<xfq> https://
xfq: this is for string definition, link to preview above
<xfq> https://
xfq: changed few thing in this PR, string definition section and changed masturd around string, description of USV string
… some editorial fixed on code point around surrogates, removed non-character concepts
xfq: already got some comments
addison: you need to be a bit careful here, for specdev and infra
… historically, we probably point USVstring instead of Unicode, UCS2 has sequesnces of 16bit ones
… in general recommendation is DOMstring, and USVstring is when really needed
… you can see in third mustard
… this kind of recommendations are kind of tricky
AOB?
<addison> homework:
<xfq> w3c/
<gb> PR 931 Add language metadata article (by xfq)
xfq: one new PR for review, on language metadata article
addison: do we need to have dedicated article, or language metadata altoghether, for better noticable by reader?
xfq: could merge, but may want to change shortname to something else
… and have redirection
addsion: mentioning each other, which is already in
r12a: using info class for paragraph, to state more information in these paragraphs