- From: Fuqiao Xue <xfq@w3.org>
- Date: Wed, 06 Dec 2023 10:57:43 +0800
- To: www-international@w3.org
https://www.w3.org/2023/11/30-i18n-minutes.html
text version:
[1]W3C
[1] https://www.w3.org/
– DRAFT –
Internationalization Working Group Teleconference
30 November 2023
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b4e2462fb/20231130T150000/
[3] https://www.w3.org/2023/11/30-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]review localizable content PR
6. [9]Working with Time and Timezones
7. [10]Localizable Manifests
8. [11]Needs Attention issues for WG review
9. [12]AOB?
10. [13]Using GH Discussions
11. [14]Summary of action items
12. [15]Summary of resolutions
Meeting minutes
acribe+
Agenda Review
Action Items
<gb> Found actions in w3c/i18n-actions: #58, #57, #56, #53,
#47, #43, #35, #33, #18, #16, #12, #11, #8, #7, #5, #4
<addison> #58
<gb> [16]Action 58 revise localizable-manifests in light of
tpac conversation and new explainer (on aphillips) due
2023-11-09
[16] https://github.com/w3c/i18n-actions/issues/58
addison: agenda item for today, working on
<addison> close #58
<addison> #57\
<gb> Closed [17]action #58
[17] https://github.com/w3c/i18n-actions/issues/58
<gb> [18]Action 57 add localizable content definition to the
glossary (on xfq) due 2023-11-09
[18] https://github.com/w3c/i18n-actions/issues/57
xfq: raised a PR for this, PR is still open
addison: let's review today
<addison> close #57
<gb> Closed [19]action #57
[19] https://github.com/w3c/i18n-actions/issues/57
<addison> #56
<gb> [20]Action 56 check on permissions with w3ctag and follow
up with plh on looking for notifications (on xfq) due
2023-11-02
[20] https://github.com/w3c/i18n-actions/issues/56
<addison> close #56
<gb> Closed [21]action #56
[21] https://github.com/w3c/i18n-actions/issues/56
<addison> #53
xfq: done for permission at w3ctag
<gb> [22]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
[22] https://github.com/w3c/i18n-actions/issues/53
<addison> #47
<gb> [23]Action 47 make the CSSWG aware of Warichu (on frivoal)
due 2023-10-04
[23] https://github.com/w3c/i18n-actions/issues/47
<addison> #43
<gb> [24]Action 43 pull together the list of win/mac/etc apis
for setting base direction and/or language (on aphillips) due
2023-09-18
[24] https://github.com/w3c/i18n-actions/issues/43
addison: 53 and 47 is CSS
<addison> #35
<gb> [25]Action 35 make the edits of CSS #5478 (on fantasai)
due 2023-08-30
[25] https://github.com/w3c/i18n-actions/issues/35
addison: started on 43 but still working, pending
<addison> #33
<gb> [26]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[26] https://github.com/w3c/i18n-actions/issues/33
addison: 33, keep working on closing ones marked as close?
… added as agenda item
<addison> #18
<gb> [27]Action 18 Have informal explanation sessions about
counter style translations with csswg members (on frivoal,
fantasai)
[27] https://github.com/w3c/i18n-actions/issues/18
<addison> #16
<gb> [28]Action 16 Keep track of line-breaking in Korean for
i18n-discuss#11 (on aphillips)
[28] https://github.com/w3c/i18n-actions/issues/16
<addison> #12
<gb> [29]Action 12 Upgrade/edit the explainer to address issues
raised by google (on aphillips)
[29] https://github.com/w3c/i18n-actions/issues/12
<addison> #11
<gb> [30]Action 11 Triage all css properties to determine which
are logical, physical, or na by default (on frivoal)
[30] https://github.com/w3c/i18n-actions/issues/11
addison: 12, working, finish up with cleaning things, keeping
alive for a while
<addison> #8
<gb> [31]Action 8 Create pr against canvas formatted text (on
aphillips)
[31] https://github.com/w3c/i18n-actions/issues/8
<addison> #7
<gb> [32]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github)
[32] https://github.com/w3c/i18n-actions/issues/7
<addison> #5
<gb> [33]Action 5 Check into how to list questions at the top
of a digest and/or improve lang enablement communications (on
r12a)
[33] https://github.com/w3c/i18n-actions/issues/5
<addison> #4
<gb> [34]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on r12a)
[34] https://github.com/w3c/i18n-actions/issues/4
Info Share
<addison> [35]https://www.w3.org/2023/11/29-coga-minutes.html
[35] https://www.w3.org/2023/11/29-coga-minutes.html
addison: had call yesterday with COGA colleages, minutes above
… reasonable start with them
r12a: got with them on interesting action items, seeking for
another opportunity incl. finding experts for input to there
<gb> Cannot create action. Validation failed. Maybe addision is
not a valid user for w3c/i18n-actions?
ACTION: addison: follow up with julie rowe on next steps with
coga such as a work plan
<gb> Created [36]action #59
[36] https://github.com/w3c/i18n-actions/issues/59
<r12a> [37]https://w3c.social/@webi18n/111489082413507311
[37] https://w3c.social/@webi18n/111489082413507311
r12a: post on mastdon above, on supporting fonts
[r12a described about images and backgrounds]
RADAR Review
<addison> [38]https://github.com/w3c/i18n-request/projects/1
[38] https://github.com/w3c/i18n-request/projects/1
addison: nothing here
… some in awaiting comment resolution could be marked as
completed...
review localizable content PR
<xfq> [39]w3c/i18n-glossary#57
[39] https://github.com/w3c/i18n-glossary/pull/57
xfq: PR above
xfq: added localizable content entry to glossary
<xfq> [40]https://
deploy-preview-57--i18n-glossary.netlify.app/#dfn-localizable-c
ontent
[40]
https://deploy-preview-57--i18n-glossary.netlify.app/#dfn-localizable-content
xfq: definition is adopted from localizable text
… didnot merged two entries, since both are used for different
envoirnment
r12a: second 'contents' should be single form?
addison: depending on what 'document' is
addison: localizable text could be string content or text
content
xfq: will update text around document
Working with Time and Timezones
<addison> [41]https://www.w3.org/TR/timezone
[41] https://www.w3.org/TR/timezone
addison: have a WG note, long standing one on timezone
<addison> [42]https://w3c.github.io/timezone/
[42] https://w3c.github.io/timezone/
addison: working for revision on this note
addison: couple of things wanted to do, publish WG draft over
WG note, for getting comments
addison: super happy to get feedback on this document
[silent for comment]
r12a: is there any used styling in 2.4?
addison: historical. just glossary one
<r12a> [43]https://www.w3.org/International/articles/
definitions-time/index.en.html
[43]
https://www.w3.org/International/articles/definitions-time/index.en.html
addison: we will want to go through this article
r12a: don't want to change, but perform checking
Localizable Manifests
<addison> [44]https://
deploy-preview-16--localizable-manifests.netlify.app/
[44] https://deploy-preview-16--localizable-manifests.netlify.app/
addison: deploy preview as above
… some material should go to another document, but not yet
addison: both miniapp and manifest are active, and we need to
update /TR/ one
… number of addition as 2.1
… section 3 is new, indicating language and direction
addison: some part could live in string-meta, but need to be in
specific document alos
xfq: some text are mentioned as in string-meta, but @@@@
addison: merge this and publish to /TR/?
<xfq> [45]https://github.com/w3c/localizable-manifests/pull/
16#discussion_r1395147047
[45]
https://github.com/w3c/localizable-manifests/pull/16#discussion_r1395147047
xfq: +1 to merge
… added a PR for definitions
addison: all in glossary one
Needs Attention issues for WG review
<addison> [46]i18n-activity#1763
[46] https://github.com/w3c/i18n-activity/issues/1763
<gb> [47]Issue 1763 Make computation of directionality account
for Shadow DOM. (by w3cbot) [close?] [tracker] [s:html]
[needs-attention] [i:bidi-text] [alreq] [hlreq] [t:bidi_markup]
[47] https://github.com/w3c/i18n-activity/issues/1763
addison: issues marked as close? but asking for review around
addison: 1763, has middle sized thread with implementation
issues
r12a: to consult with fantasai?
<addison> [48]i18n-activity#1361
[48] https://github.com/w3c/i18n-activity/issues/1361
<gb> [49]Issue 1361 input-purpose `language` should reference
BCP47 (by w3cbot) [close?] [needs-attention] [needs-resolution]
[s:adapt] [t:lang_values]
[49] https://github.com/w3c/i18n-activity/issues/1361
addison: older issue related to CR or something
… question is whether something needs to be performed?
addison: associated to long thread in [50]whatwg/html#6519
[50] https://github.com/whatwg/html/issues/6519
<gb> [51]Issue 6519 [not found]
[51] https://github.com/w3c/i18n-actions/issues/6519
<gb> [52]Issue 6519 [not found]
[52] https://github.com/w3c/html/issues/6519
<gb> [53]Issue 6519 4.10.18.7 Autofill & the language value (by
johnfoliot) [i18n-tracker]
[53] https://github.com/whatwg/html/issues/6519
<addison> [54]i18n-activity#1006
[54] https://github.com/w3c/i18n-activity/issues/1006
<gb> [55]Issue 1006 Informal spellings in specifications (by
w3cbot) [close?] [tracker] [needs-attention]
[55] https://github.com/w3c/i18n-activity/issues/1006
addison: 1006, CSS general purpose one in spellings
… just to look into from translations point of view
xfq: will take this
… English usage in CSS specs
RESOLUTION: We consider informal spellings to be typos to be
fixed when found and avoided if possible
addison: or maybe more general usage
r12a: this is CSS resolution, but not of us
… sounds good to me
<addison> [56]i18n-activity#404
[56] https://github.com/w3c/i18n-activity/issues/404
<gb> [57]Issue 404 Should generalYear (etc.) be gregorianYear
(etc.)? (by aphillips) [close?] [s:owl-time] [needs-attention]
[needs-resolution] [t:loc_time]
[57] https://github.com/w3c/i18n-activity/issues/404
addison: 404 is old one, on naming
… if they use general, many other calendars exist
… it seems they did not consider my comment
<addison> [58]sdw#888
[58] https://github.com/w3c/sdw/issues/888
<gb> [59]CLOSED Issue 888 should generalYear (etc) be
gregorianYear (etc)? (by aphillips) [i18n-needs-resolution]
[time]
[59] https://github.com/w3c/sdw/issues/888
<r12a> +1 to close from me
+1 to close, looking at spec text...
xfq: from the last comment, it seems they support only
gregorian, but not others
addison: they tended to support others, but not included yet
xfq: spec text says, not limited to number used for gregorian
<xfq> +1 to close
addison: moving on?
<addison> [60]i18n-activity#370
[60] https://github.com/w3c/i18n-activity/issues/370
<gb> [61]Issue 370 Standardized way to add indications of text
direction (by r12a) [close?] [s:shacl] [needs-attention]
[needs-resolution] [t:lang_declaration]
[61] https://github.com/w3c/i18n-activity/issues/370
addison: this is about standalization of text direction in
data-shapes
… quite old as 2017
<addison> close [62]i18n-activity#370
[62] https://github.com/w3c/i18n-activity/issues/370
<gb> Cannot close issue #370. Forbidden.
r12a: I think we've discussed with them whether this is ok or
not
<addison> [63]https://lists.w3.org/Archives/Public/
public-i18n-core/2023OctDec/0075.html
[63]
https://lists.w3.org/Archives/Public/public-i18n-core/2023OctDec/0075.html
addison: item in above email, comment in next call
AOB?
Using GH Discussions
r12a: kida-san is interested in Discussions feature
… discussions in thread, could be interested for us also
… can have comments, and comments to a comment
… could be useful for jlreq-d discussions
… one issue is notification, and xfq and I are talking with Dom
for notification email
<xfq> [64]https://github.com/w3c/jlreq-d/discussions
[64] https://github.com/w3c/jlreq-d/discussions
addison: in message format group, we are using issue and
discussion, also
… had some success in past, but tend not to use recently
r12a: having some wiki pages, but cannot have comments there
xfq: will talk with Dom
ACTION: xfq: follow up with dom about github discussion
notifications
<gb> Created [65]action #60
[65] https://github.com/w3c/i18n-actions/issues/60
r12a: any info for upward arrow?
xfq: there are also thumb-up button etc.
<xfq> [66]https://github.com/w3c/jlreq-d/discussions
[66] https://github.com/w3c/jlreq-d/discussions
addison: will be shown as order with clicking 'top'
Summary of action items
1. [67]addison: follow up with julie rowe on next steps with
coga such as a work plan
2. [68]xfq: follow up with dom about github discussion
notifications
Summary of resolutions
1. [69]We consider informal spellings to be typos to be fixed
when found and avoided if possible
Received on Wednesday, 6 December 2023 02:57:46 UTC