- From: r12a <ishida@w3.org>
- Date: Thu, 10 Jan 2019 14:56:12 +0000
- To: www International <www-international@w3.org>
https://www.w3.org/2019/01/10-i18n-minutes.html
text extract follows:
- DRAFT -
Internationalization Working Group Teleconference
10 Jan 2019
[2]Agenda
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2019Jan/0000.html
Attendees
Present
Katy, atsushi, addison, r12a, David, Bert
Regrets
JcK
Chair
Addison Phillips
Scribe
addison
Contents
* [3]Topics
1. [4]Agenda and Minutes
2. [5]RADAR and Active Work Review
3. [6]One-and-a-half new articles about HTTP/meta
language info
4. [7]Planning 2019 activities
5. [8]AOB?
* [9]Summary of Action Items
* [10]Summary of Resolutions
__________________________________________________________
trackbot, prepare teleconference
<agendabot> clear agenda
<David> can you hear me on Webex?
<Katy> Yes, I can hear your David
Agenda and Minutes
[11]https://www.w3.org/International/track/actions/open
[11] https://www.w3.org/International/track/actions/open
<scribe> scribenick: addison
RADAR and Active Work Review
<atsushi> happy new year all!
[12]https://github.com/w3c/i18n-activity/projects/1
[12] https://github.com/w3c/i18n-activity/projects/1
[13]http://w3c.github.io/i18n-activity/projects/
[13] http://w3c.github.io/i18n-activity/projects/
richard: possible work on african languages/scripts
<r12a> * line-breaking tests rewritten to incorporate
educational results pages, clear indications of exploratory vs
not, and show workings (including externalised js) – tests
addressed include:
<r12a> * Line-breaking
[14]https://w3c.github.io/i18n-tests/results/line-breaking,
[14] https://w3c.github.io/i18n-tests/results/line-breaking,
<r12a> * Non-tailorable line breaking,
[15]https://w3c.github.io/i18n-tests/results/line-breaks-glwj,
[15] https://w3c.github.io/i18n-tests/results/line-breaks-glwj,
<r12a> * word-break,
[16]https://w3c.github.io/i18n-tests/results/word-break,
[16] https://w3c.github.io/i18n-tests/results/word-break,
<r12a> * Japanese & Chinese line breaks,
[17]https://w3c.github.io/i18n-tests/results/line-breaks-jazh
[17] https://w3c.github.io/i18n-tests/results/line-breaks-jazh
<r12a> * the results pages for the above were all adapted to be
more readable, to better support educational and gap analysis
work
richard: rewrote the line breaking tests
... seems like florian is writing i18n-related tests for css
... trying to figure out line breaking
... getting over to platform tests
... improved the results pages
... putting in more explanatory text
... so someone use them for pedagogical reasons
... can also use as a source for line breaking
One-and-a-half new articles about HTTP/meta language info
[18]https://lists.w3.org/Archives/Member/member-i18n-core/2019J
an/0002.html
[18]
https://lists.w3.org/Archives/Member/member-i18n-core/2019Jan/0002.html
[19]https://www.w3.org/International/questions/qa-http-and-lang
.en
[19] https://www.w3.org/International/questions/qa-http-and-lang.en
[20]http://w3c.github.io/i18n-drafts/questions/qa-text-processi
ng-vs-metadata.en
[20]
http://w3c.github.io/i18n-drafts/questions/qa-text-processing-vs-metadata.en
richard: as I mentioned, there is an article
... which was put together quickly a long time ago
... there was a recent complaint
... took article and rewrote it
<r12a>
[21]http://w3c.github.io/i18n-drafts/questions/qa-http-and-lang
-TEST.en
[21]
http://w3c.github.io/i18n-drafts/questions/qa-http-and-lang-TEST.en
katy: significantly easier to read
... covered meta element quickly
... only lightweight thing was "links for futher info"
... so could link directly
<r12a>
[22]http://w3c.github.io/i18n-drafts/questions/qa-text-processi
ng-vs-metadata.en
[22]
http://w3c.github.io/i18n-drafts/questions/qa-text-processing-vs-metadata.en
<r12a> OLD VERSION:
[23]https://www.w3.org/International/questions/qa-http-and-lang
.en
[23] https://www.w3.org/International/questions/qa-http-and-lang.en
<scribe> ACTION: richard: publish new/replacement articles on
http meta lang by Wednesday, incorporating new WG comments as
appropriate
<trackbot> Created ACTION-770 - Publish new/replacement
articles on http meta lang by wednesday, incorporating new wg
comments as appropriate [on Richard Ishida - due 2019-01-17].
[24]http://w3c.github.io/i18n-activity/reviews/
[24] http://w3c.github.io/i18n-activity/reviews/
Planning 2019 activities
richard: prioritize the things lying around
<r12a> [25]http://w3c.github.io/i18n-activity/projects/
[25] http://w3c.github.io/i18n-activity/projects/
understand status by next telecon
[26]https://github.com/w3c/charmod-norm/issues
[26] https://github.com/w3c/charmod-norm/issues
richard: will edit string-meta
... remove ITS IG
... add article/site design under E&O
... remove encoding
<atsushi> just chat-ish info, we (ja) had a year-beginning
face-to-face greeting this week... (and had some chat on ruby)
richard: get whatwg to implement ruby the way we want
... that would have been chaals
... anyone notice if he did that?
<scribe> ACTION: addison: ping chaals about syncing whatwg ruby
support
<trackbot> Created ACTION-771 - Ping chaals about syncing
whatwg ruby support [on Addison Phillips - due 2019-01-17].
AOB?
david: email address issue raised at tpac, where is it?
richard: year beginning f2f in ja, what was mentioned?
atsushi: agree that we know about long term outstanding issues
with ruby
... maybe need to discuss and do something?
... summarize existing issues
... especially for ebooks
richard: who?
atsushi: murata-san, etc.
richard: can reply, some things have happened
Summary of Action Items
[NEW] ACTION: addison: ping chaals about syncing whatwg ruby
support
[NEW] ACTION: richard: publish new/replacement articles on http
meta lang by Wednesday, incorporating new WG comments as
appropriate
Summary of Resolutions
[End of minutes]
Received on Thursday, 10 January 2019 14:56:15 UTC