- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 05 Jul 2024 09:02:43 +0800
- To: www-international@w3.org
https://www.w3.org/2024/07/04-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
04 July 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/b40424a9-1664-4b61-965c-27712bb6a648/20240704T150000/
[3] https://www.w3.org/2024/07/04-i18n-irc
Attendees
Present
addison, Atsushi, Bert, Fuqiao, JcK, Richard
Regrets
-
Chair
Addison Phillips
Scribe
atsushi
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issue Review
6. [9]Publish FPWD of various layout requirements
7. [10]Normativity of i18n-glossary (redux)
8. [11]String-Meta: BPs for Consumers
9. [12]Draft PRs
10. [13]AOB?
11. [14]Summary of resolutions
Meeting minutes
Agenda Review
Action Items
<addison> [15]https://github.com/w3c/i18n-actions/
issues?q=is%3Aopen+is%3Aissue
[15] https://github.com/w3c/i18n-actions/issues?q=is:open+is:issue
<addison> #110
<gb> [16]Action 110 create new latin lreq document to host dpig
contents (on r12a) due 2024-06-27
[16] https://github.com/w3c/i18n-actions/issues/110
<addison> close #110
<gb> Closed [17]issue #110
[17] https://github.com/w3c/i18n-actions/issues/110
<addison> #108
<gb> [18]Action 108 talk to jlreq about *default* behavior of
line breaking with small kana (cf. csswg-drafts#10363) (on
himorin) due 2024-06-25
[18] https://github.com/w3c/i18n-actions/issues/108
addison: #110 done, close
<xfq> [19]https://github.com/w3c/jlreq/discussions/436
[19] https://github.com/w3c/jlreq/discussions/436
<gb> [20]Discussion 436 JLReq TF meeting notes 2024-6-25 (by
kidayasuo)
[20] https://github.com/w3c/jlreq/discussions/436
<addison> atsushi: some discussion, kida-san had some comments
last week
<addison> close #108
<gb> Closed [21]issue #108
[21] https://github.com/w3c/i18n-actions/issues/108
atsushi: #108 discussed and commented, close
<addison> #106
<gb> [22]Action 106 write to ietf group about rfc9457 (on
aphillips) due 2024-06-20
[22] https://github.com/w3c/i18n-actions/issues/106
<addison> #93
<gb> [23]Action 93 create best practices for consumers in
string-meta (on aphillips) due 2024-04-25
[23] https://github.com/w3c/i18n-actions/issues/93
<addison> #90
<gb> [24]Action 90 steal some of henri's text from
scroll-to-text-fragment for string-search (on aphillips) due
2024-04-18
[24] https://github.com/w3c/i18n-actions/issues/90
<addison> #89
<gb> [25]Action 89 update i18n specs to support dark mode (on
xfq) due 2024-04-18
[25] https://github.com/w3c/i18n-actions/issues/89
<addison> #79
<gb> [26]Action 79 schedule a follow-up call with WHATNOT in
~April (on aphillips) due 2024-03-07
[26] https://github.com/w3c/i18n-actions/issues/79
xfq: #89, yes blocked
<addison> #78
<gb> [27]Action 78 compare infra to i18n-glossary export list
and report back (on aphillips) due 2024-03-07
[27] https://github.com/w3c/i18n-actions/issues/78
<addison> #33
<gb> [28]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[28] https://github.com/w3c/i18n-actions/issues/33
addison: covers gap, since it's comparison and diff, still not
sending to INFRA
addison: #33, evergreen one
<addison> #8
<gb> [29]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[29] https://github.com/w3c/i18n-actions/issues/8
<addison> #7
<gb> [30]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[30] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [31]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on aphillips,
r12a) due 27 Jul 2023
[31] https://github.com/w3c/i18n-actions/issues/4
Info Share
[silent]
RADAR Review
<addison> [32]https://github.com/orgs/w3c/projects/91/views/1
[32] https://github.com/orgs/w3c/projects/91/views/1
addison: new incoming
bert: take vibration API
addison: anything else?
Pending Issue Review
<addison> [33]https://github.com/w3c/i18n-activity/issues
[33] https://github.com/w3c/i18n-activity/issues
<addison> [34]i18n-activity#1879
[34] https://github.com/w3c/i18n-activity/issues/1879
<gb> [35]Issue 1879 should default reset/submit button text and
default summary text use node's language rather than being
locale-specific? (by w3cbot) [pending] [tracker] [s:html]
[35] https://github.com/w3c/i18n-activity/issues/1879
addison: one interesting pending issue, above
… on HTML
… language of the document or locale
<addison> [36]whatwg/html#10437
[36] https://github.com/whatwg/html/issues/10437
<gb> [37]Issue 10437 should default reset/submit button text
and default summary text use node's language rather than being
locale-specific? (by dbaron) [topic: forms] [i18n-tracker]
[37] https://github.com/whatwg/html/issues/10437
addison: long standing one, on document language and browser
xfq: clreq discussed recently similar on date picker
… use language of user agent instead of the page
… This makes the internationalization state of this component
independent of the internationalization state of the rest of
the page.
… it's kind of similar item
addison: lots of controls are behaving as a part of content
… and sometimes it looks something strange
… whether to allow controls to have document language or set to
locale of browser, is good question
xfq: author should be able to express override
addison: will chime in this
Publish FPWD of various layout requirements
<r12a> [38]https://www.w3.org/International/typography/
gap-analysis/language-matrix.html
[38]
https://www.w3.org/International/typography/gap-analysis/language-matrix.html
r12a: what I am doing, starting from language matrix, supposed
to list from gap-analysis document
… gap-analysis document changes over, and applied to matrix
… in addison, also 4/5 left to do
… for Latin, each of Latin languages are in separate
gap-analysis document
… like 20 document for Latin
… not good for maintaining
… tried to improve Latin document
… contain all languages into one Latin gap-analysis document
… items are labelled
… gap-analysis and lreq documents are built from scripts for
now
… much easier for maintenance
addison: can separate languages if we need?
… just thinking around
JcK: if it is one language to one script, its ok, but for
language to multiple scripts, we need some
r12a: see some examples, French, Dutch, has different columns
… we can see issues per set of language or script
… data is in github issue, with label, and can be selected per
target
[detail with arabic]
r12a: for publication, not publish urdu one, putting into
nastaliq group
… Latin lreq and gap-analysis are for publication approval
r12a: so, Latin lreq, Latin gap-analysis, hebrew gap-analysis
… beng lreq
… hebrew lreq
<addison> proposed: publish as FPWD hebrew, latin, bengali,
devanagari lreq and latin gap
r12a: devanagari lreq
<addison> +1
<Bert> +1
+1
<xfq> +1
<r12a> +1
<JcK> +0.5
RESOLUTION: publish Latn, Hebr, Beng, Deva LREQ and Latn gap
analysis as FPWD
r12a: nastalq?
addison: arabic as parent and others as children are some
complex
addison: how do you do if these are not separated
r12a: multiple lines in arabic part, columns will have
different like for nastaliq
<Bert> (All the links in the matrix in the Arab section
currently link to cher-gap.)
Normativity of i18n-glossary (redux)
addison: one issue filed to i18n-glossary for normative citing
… use glossary entry as term definition in normative part
… glossary already have a note on this, don't cite in
normative, but copy text
… or refer Unicode or else
… i18n-glossary have composed list from various places
… reconsider these requests, and make some sort of rec-track or
not, with evergreen CRS or something
addison: sometimes just tell them to copy
addison: want to say, document is not in rec-track, and cannot
define normative term. if you want to define normativelly, do
it yourself
[chat about normative/rec-track]
xfq: referncing non-normative text in normative part is not
prohibited?
String-Meta: BPs for Consumers
addison: as you remember, we had guidance on consumers section
<addison> [39]https://pr-preview.s3.amazonaws.com/aphillips/
string-meta/pull/87.html#bp-consumers
[39]
https://pr-preview.s3.amazonaws.com/aphillips/string-meta/pull/87.html#bp-consumers
addison: added edits, and result as above URL
addison: main change is in examples
Draft PRs
<addison> [40]w3c/i18n-drafts#591
[40] https://github.com/w3c/i18n-drafts/pull/591
<gb> [41]Pull Request 591 QA Native Direction (edits) (by
aphillips)
[41] https://github.com/w3c/i18n-drafts/pull/591
addison: couple of articles in progress
<addison> [42]https://
deploy-preview-591--i18n-drafts.netlify.app/questions/
qa-direction-native.html
[42]
https://deploy-preview-591--i18n-drafts.netlify.app/questions/qa-direction-native.html
addison: is this PR ready to merge?
… any objection?
xfq: feedback section?
addison: change link to the same as leave a comment
<addison> [43]https://github.com/aphillips/i18n-drafts/blob/
gh-pages/articles/language-negotiation/language-negotiation.md
[43]
https://github.com/aphillips/i18n-drafts/blob/gh-pages/articles/language-negotiation/language-negotiation.md
addison: language negotiation part still in markdown
… please comment or give suggestion on this draft
xfq: having two article on this target is not good
addison: different target, doing the same
r12a: if you wanted to xxx, go yyy?
AOB?
[none]
Summary of resolutions
1. [44]publish Latn, Hebr, Beng, Deva LREQ and Latn gap
analysis as FPWD
Received on Friday, 5 July 2024 01:02:44 UTC