- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 08 Sep 2023 10:54:17 +0800
- To: www-international@w3.org
https://www.w3.org/2023/09/07-i18n-minutes.html
text version:
– DRAFT –
Internationalization WG Teleconference
07 September 2023
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/c5b143d1-0a5b-4adb-8d60-0f5f9bfe5a41/20230907T150000/
[3] https://www.w3.org/2023/09/07-i18n-irc
Attendees
Present
Addison, Atsushi, Eemeli, Fuqiao, JcK, Richard
Regrets
-
Chair
Addison Phillips
Scribe
xfq
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issue Review
6. [9]TPAC Planning
7. [10]WCAG 2.2
8. [11]RDF-star prep
9. [12]Verifiable Credentials localization
10. [13]AOB?
Meeting minutes
Agenda Review
Action Items
<gb> Found actions in w3c/i18n-actions: #41, #39, #36, #35,
#33, #32, #18, #16, #15, #13, #12, #11, #10, #9, #8, #7, #5, #4
<addison> #41?
<gb> [14]Action 41 propose new specdev text on strings for xml
(on aphillips) due 2023-09-07
[14] https://github.com/w3c/i18n-actions/issues/41
<addison> #39?
<gb> [15]Action 39 develop best practice guidelines for
name-like fields (on aphillips) due 2023-08-31
[15] https://github.com/w3c/i18n-actions/issues/39
<addison> #36?
<gb> [16]Action 36 follow up with murata-san about wcag status
(on aphillips) due 2023-08-31
[16] https://github.com/w3c/i18n-actions/issues/36
<addison> #35?
<gb> [17]Action 35 make the edits of CSS #5478 (on fantasai)
due 2023-08-30
[17] https://github.com/w3c/i18n-actions/issues/35
<addison> #33?
<gb> [18]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[18] https://github.com/w3c/i18n-actions/issues/33
addison: I've closed ~40 issues
… I've been marking issues with needs-attention
… we have ~100 issues marked 'close?'
… making progress
<addison> #32?
<gb> [19]Action 32 Approve the character markup PR (on
fantasai) due 2023-08-17
[19] https://github.com/w3c/i18n-actions/issues/32
<addison> #18?
<gb> [20]Action 18 Have informal explanation sessions about
counter style translations with csswg members (on frivoal,
fantasai)
[20] https://github.com/w3c/i18n-actions/issues/18
<addison> #16?
<gb> [21]Action 16 Keep track of line-breaking in Korean for
i18n-discuss#11 (on aphillips)
[21] https://github.com/w3c/i18n-actions/issues/16
<addison> #15?
<gb> [22]Action 15 Get character styling into w3c stylesheet
(on aphillips)
[22] https://github.com/w3c/i18n-actions/issues/15
<addison> #13?
<gb> [23]Action 13 Make sure generics are comfortable to read
in the content language (on frivoal)
[23] https://github.com/w3c/i18n-actions/issues/13
<addison> #12?
<gb> [24]Action 12 Upgrade/edit the explainer to address issues
raised by google (on aphillips)
[24] https://github.com/w3c/i18n-actions/issues/12
<addison> #11?
<gb> [25]Action 11 Triage all css properties to determine which
are logical, physical, or na by default (on frivoal)
[25] https://github.com/w3c/i18n-actions/issues/11
<addison> #10?
<gb> [26]Action 10 With florian triage richard's article into a
list of potential generics (on fantasai)
[26] https://github.com/w3c/i18n-actions/issues/10
<addison> #9?
<gb> [27]Action 9 Follow up with ecma-402 on next steps and
start tc39 discussion (on aphillips)
[27] https://github.com/w3c/i18n-actions/issues/9
<addison> #8?
<gb> [28]Action 8 Create pr against canvas formatted text (on
aphillips)
[28] https://github.com/w3c/i18n-actions/issues/8
<addison> #7?
<gb> [29]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github)
[29] https://github.com/w3c/i18n-actions/issues/7
<addison> #5
<gb> [30]Action 5 Check into how to list questions at the top
of a digest and/or improve lang enablement communications (on
r12a)
[30] https://github.com/w3c/i18n-actions/issues/5
<addison> #4
<gb> [31]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on r12a)
[31] https://github.com/w3c/i18n-actions/issues/4
Info Share
RADAR Review
<addison> [32]https://github.com/w3c/i18n-request/projects/1
[32] https://github.com/w3c/i18n-request/projects/1
addison: we have no new incoming requests
Pending Issue Review
addison: that's probably not suprising since there's a
publishing moratorium and everyone is preparing for TPAC
<addison> [33]https://github.com/w3c/i18n-activity/issues
[33] https://github.com/w3c/i18n-activity/issues
[34]w3c/i18n-activity#1756
[34] https://github.com/w3c/i18n-activity/issues/1756
addison: I had a conversation with AnneVK about applying
dirname to some input fields that don't currently have their
name
… telephone was one
… and buttons
… passwords were the only one left
… RDF is still trying to define string again
… Verifiable Credentials Data Model really don't want to use
@language in @context
… to set the default language in a JSON document
… if everybody invents their own mechanism because they don't
like @context
… we end up with 12 different ways of specifying this document
is in English
<addison> [35]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Aneeds-attention
[35]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:needs-attention
addison: if you look at the end of the link
… you'll see that there are 20 issues
TPAC Planning
addison: r12a and xfq might want to have a look and go through
these issues
<addison> [36]https://github.com/w3c/i18n-actions/wiki/
2023-TPAC-Planning
[36] https://github.com/w3c/i18n-actions/wiki/2023-TPAC-Planning
addison: we now have a number of meetings
… on Mon, we will meet with webapps in the afternoon
… it's confirmed
… on Tue, we will meet with RDF-star
… and with APA
… on Thursday we will meet with CSS at the end of morning
r12a: this is all great
… it would be great if we could put some links in here to give
some idea of what the topic of discussion would be
… so that we can prep beforehand
… is that possible?
addison: in some cases it is
… like webapps and RDF-star
… we have a lot of open issues with CSS
… I'm going through and closing those as quickly as I can
r12a: I'm suprised it starts at 8:00
addison: I've changed the wiki page to 9 for now
<r12a> [37]https://www.w3.org/2023/09/TPAC/#schedule
[37] https://www.w3.org/2023/09/TPAC/#schedule
r12a: this is the official schedule for TPAC 2023
… it says group meetings from 9:30 every day
addison: I did not call out Wednesday
… Eemeli has a breakout session on DOM Localization on
Wednesday
… not that we're sponsoring it as a group, but it's i18n
related
r12a: Monday is the biggest problem for me because we have a
team event
… Tuesday for me is not such a big problem
<r12a> and on Monday people such as myself will need to
register at 9am
<addison> [38]https://github.com/w3c/i18n-actions/wiki/
2023-TPAC-Planning#proposed-css-joint-agenda
[38]
https://github.com/w3c/i18n-actions/wiki/2023-TPAC-Planning#proposed-css-joint-agenda
WCAG 2.2
addison: has anybody else taken a look?
r12a: as a WG we're trying to unblock it
addison: some groups claim that issues they ignored previously
are now backwards compatibility
r12a: plh was on vacation when he signed off the transition and
he admits that he missed
… that's a component of the problem
addison: it's a single point of failure
r12a: it has occurred to me that we're not closing a lot of
stuff and yet people are flying through transitions
… and we need to look more closely at that
addison: green color doesn't mean that we put that label
addison: I'm gonna schedule some time maybe on Monday morning
<r12a> [39]https://www.w3.org/2023/09/TPAC/
schedule.html#tuesday
[39] https://www.w3.org/2023/09/TPAC/schedule.html#tuesday
RDF-star prep
addison: there are 2 things going on in that space
… one is their attempts to define what a string is
… a matter of Unicode terminology
… the other thing is the need to add directional metadata to
fields
… I'll try to dig out the issues and put them in our agenda so
that you can all be prepared
Verifiable Credentials localization
addison: VC is the other thing I want to bring up
… they're trying to do the right things somewhat
… although they use JSON-LD
… they want to allow people to process the credentials using
regular old JSON
… regular JSON processor would not know how to apply natural
language string
… problem 2 is they're concerned that @language should not be
applied to non-language strings and feel that this is required
by @context
r12a: if there are only 2 strings would it work just to have
the language and direction that associateed with those 2
strings?
addison: yes, it would
… but they've been unwilling to encoding it for every iteration
of name and description
… there *is* a way to associate metadata with the string
… but you can also just decode the string with no metadata
… because presumably they're all in the same language
… every other JSON-based format will have exactly the same set
of problems
… some of them won't even be JSON-LD processors at all
AOB?
addison: I will see some of you in Seville in a few days
JcK: I wish you all pleasant travels and a wonderful and
relaxing and productive meeting
addison: safe travels!
Received on Friday, 8 September 2023 02:54:19 UTC