- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 03 Nov 2023 09:55:16 +0800
- To: www-international@w3.org
https://www.w3.org/2023/11/02-i18n-minutes.html
text version:
[1]W3C
[1] https://www.w3.org/
– DRAFT –
Internationalization Working Group Teleconference
02 November 2023
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/c5b143d1-0a5b-4adb-8d60-0f5f9bfe5a41/20231102T150000/
[3] https://www.w3.org/2023/11/02-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, JcK, r12a, Richard
Regrets
-
Chair
Addison Phillips
Scribe
addison, xfq
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]RADAR Review
6. [9]Pending Issue Review
7. [10]Handling name-like fields in specdev
8. [11]vc-json-schema and name/description
9. [12]AOB?
10. [13]Summary of action items
Meeting minutes
Agenda Review
Action Items
<addison> gb, list open actions
<gb> Found actions in w3c/i18n-actions: #56, #55, #54, #53,
#48, #47, #43, #39, #35, #33, #18, #16, #12, #11, #8, #7, #5,
#4
<addison> #56
<gb> [14]Action 56 check on permissions with w3ctag and follow
up with plh on looking for notifications (on xfq) due
2023-11-02
[14] https://github.com/w3c/i18n-actions/issues/56
<addison> xfq: sent an email but no reply yet
<addison> #55
<gb> [15]Action 55 work out new time slot for i18n/CSS call (on
xfq) due 2023-11-01
[15] https://github.com/w3c/i18n-actions/issues/55
[16]https://doodle.com/meeting/organize/id/aOZ9ZpEe
[16] https://doodle.com/meeting/organize/id/aOZ9ZpEe
<addison> xfq: sent a doodle poll
<addison> ... waiting on addison
<addison> #54
<gb> [17]Action 54 read Murata-san's ruby-t2s-req and Chinese
requirements and Zaima and see what we're going to do (on xfq)
due 2023-11-01
[17] https://github.com/w3c/i18n-actions/issues/54
<addison> xfq: starting reviewing today, need time
<addison> #53
<gb> [18]Action 53 come up with a set of information CSS want
the i18n group to provide support for generic font families (on
frivoal, fantasai) due 2023-11-01
[18] https://github.com/w3c/i18n-actions/issues/53
<addison> #48
<gb> [19]Action 48 work with clreq to investigate or produce a
generics proposal (on xfq) due 2023-10-05
[19] https://github.com/w3c/i18n-actions/issues/48
xfq: propose to close because we decided to wait for css wg to
work on the registry framework
close #48
<gb> Closed [20]action #48
[20] https://github.com/w3c/i18n-actions/issues/48
#47
<gb> [21]Action 47 make the CSSWG aware of Warichu (on frivoal)
due 2023-10-04
[21] https://github.com/w3c/i18n-actions/issues/47
#43
<gb> [22]Action 43 pull together the list of win/mac/etc apis
for setting base direction and/or language (on aphillips) due
2023-09-18
[22] https://github.com/w3c/i18n-actions/issues/43
#39
<gb> [23]Action 39 develop best practice guidelines for
name-like fields (on aphillips) due 2023-08-31
[23] https://github.com/w3c/i18n-actions/issues/39
#35
<gb> [24]Action 35 make the edits of CSS #5478 (on fantasai)
due 2023-08-30
[24] https://github.com/w3c/i18n-actions/issues/35
#33
<gb> [25]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[25] https://github.com/w3c/i18n-actions/issues/33
#18
<gb> [26]Action 18 Have informal explanation sessions about
counter style translations with csswg members (on frivoal,
fantasai)
[26] https://github.com/w3c/i18n-actions/issues/18
#16
<gb> [27]Action 16 Keep track of line-breaking in Korean for
i18n-discuss#11 (on aphillips)
[27] https://github.com/w3c/i18n-actions/issues/16
#12
<gb> [28]Action 12 Upgrade/edit the explainer to address issues
raised by google (on aphillips)
[28] https://github.com/w3c/i18n-actions/issues/12
#11
<gb> [29]Action 11 Triage all css properties to determine which
are logical, physical, or na by default (on frivoal)
[29] https://github.com/w3c/i18n-actions/issues/11
#8
<gb> [30]Action 8 Create pr against canvas formatted text (on
aphillips)
[30] https://github.com/w3c/i18n-actions/issues/8
#7
<gb> [31]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github)
[31] https://github.com/w3c/i18n-actions/issues/7
#5
#5
<gb> [32]Action 5 Check into how to list questions at the top
of a digest and/or improve lang enablement communications (on
r12a)
[32] https://github.com/w3c/i18n-actions/issues/5
#4
<gb> [33]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on r12a)
[33] https://github.com/w3c/i18n-actions/issues/4
Info Share
JcK: IETF is next week
… so I may not be on the call
<r12a> [34]https://typo.social/@ri/111311675323086386
[34] https://typo.social/@ri/111311675323086386
r12a: last week I mentioned that I was working on the font
lister page and the samples page
… the work is done
… see the link ^
… I added about 20 scripts
… improved the UI in a number of ways
<r12a> [35]https://typo.social/@ri/111311572521610006
[35] https://typo.social/@ri/111311572521610006
r12a: this is the font lister update
… I reloaded all the fonts on my system
… and snaps of them
… there are over 800 pictures of the text for a lot of scripts
… there are 20 new scripts approximately
… macOS Ventura, doesn't support macOS Sonoma yet
… a number of UI improvements
<r12a> [36]https://typo.social/@ri/111311616598455406
[36] https://typo.social/@ri/111311616598455406
r12a: you can increase and decrease the size of the font
… as well as the images
… if you click the icon to the left of the font name, like the
Windows icon
… all the other fonts will disappear
… and you'll only see the Windows font
addison: Unicode Technology Workshop is next week
… it is an in-person event in Mountain View
[37]https://unicode.org/events/utw/program/#tue
[37] https://unicode.org/events/utw/program/#tue
addison: if you're not there I'll let you know if you missed
anything
r12a: it would be nice to know who's gonna be speaking there
addison: if you are paying attention to the MessageFormat work,
there's a balloting going on
<r12a> [38]https://r12a.github.io/scripts/fontlist/
[38] https://r12a.github.io/scripts/fontlist/
addison: I've been the chair
… please vote
r12a: I'm going to suggest that these are the generic fallback
… this font page only looks at fonts that are available on
Windows and macOS and Noto fonts and SIL fonts
… and it doesn't look at anything else
RADAR Review
[39]https://github.com/w3c/i18n-request/projects/1
[39] https://github.com/w3c/i18n-request/projects/1
addison: we have no new incoming
… I did move VC JSON Schema to Awaiting comment resolution
… atsushi, thank you for filing the issue
… I adjusted the tags slightly
RADAR Review
Pending Issue Review
[40]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[40]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
Handling name-like fields in specdev
[41]w3c/bp-i18n-specdev#121
[41] https://github.com/w3c/bp-i18n-specdev/pull/121
[42]https://
deploy-preview-121--bp-i18n-specdev.netlify.app/#markup
[42]
https://deploy-preview-121--bp-i18n-specdev.netlify.app/#markup
addison: this is something we discussed
… I did a significant rewrite
… I reorganised the sections completely
… I've retitled the section that used to be called "markup &
syntax"
… it's now called "Document formats, markup & syntax"
… I'll point out the Japanese example is from Google Translate
p.myClassName and p.私のクラス名
JcK: I don't see issues on skimming
vc-json-schema and name/description
JcK: from my standpoint, go ahead and merge it
… I'll try to review the merged version
[43]w3c/i18n-activity#1775
[43] https://github.com/w3c/i18n-activity/issues/1775
<gb> [44]Issue 1775 `name` and `description` fields need
language and direction (by aphillips) [pending]
[t:bidi_strings] [t:lang_strings] [s:vc-json-schema]
[44] https://github.com/w3c/i18n-activity/issues/1775
addison: OK. We've accomplished something.
addison: the VC JSON Schema document is telling people how to
write JSON Schemas of a particular credential
[45]https://www.w3.org/TR/vc-json-schema/#name
[45] https://www.w3.org/TR/vc-json-schema/#name
addison: if you look at that location in vc-json-schema ^
… and then you scroll down just a little bit and you'll see
example 6 of an example of a JSON schema
… the name and description are in English
… therefore I would think that we would want VC JSON Schema to
say, you should use, for example the context to provide
language and direction metadata for these fields
… you should label these in different languages
… they should address the localizability of schemas that people
produce
… maybe make them in more than English
… and maybe tell people what language they're in
atsushi: I totally agree
<atsushi> +1
addison: any other thoughts on #1775?
<gb> [46]Issue 1775 [not found]
[46] https://github.com/w3c/i18n-actions/issues/1775
addison: any objections?
AOB?
addison: I'll make that comment then
<r12a> [47]https://www.w3.org/International/articles/
language-tags/index.fr.html
[47]
https://www.w3.org/International/articles/language-tags/index.fr.html
r12a: I just published a French translation
… for this article ^
… if you go to the English version, I reorganised the text
somewhat
… based on the suggestion of the French translator
… the French translation looks a bit different from the English
one
… but it's all good, I think
… but it was an interesting exercise
… mostly moved stuff a around a bit
<r12a> [48]https://www.w3.org/International/articles/
language-tags/index.en.html
[48]
https://www.w3.org/International/articles/language-tags/index.en.html
r12a: Gwendoline Clavé is the translator
[49]w3c/localizable-manifests#13
[49] https://github.com/w3c/localizable-manifests/issues/13
<gb> [50]Issue 13 Broken links (by xfq)
[50] https://github.com/w3c/localizable-manifests/issues/13
(thanks from the working group!!)
xfq: @@1
ACTION: xfq: add localizable content definition to the glossary
<gb> Created [51]action #57
[51] https://github.com/w3c/i18n-actions/issues/57
ACTION: addison: revise localizable-manifests in light of tpac
conversation and new explainer
<gb> Created [52]action #58
[52] https://github.com/w3c/i18n-actions/issues/58
Summary of action items
1. [53]xfq: add localizable content definition to the glossary
2. [54]addison: revise localizable-manifests in light of tpac
conversation and new explainer
Received on Friday, 3 November 2023 01:55:18 UTC