– DRAFT –
Internationalization Working Group Teleconference

<addison> trackbot, prepare teleconference

Agenda Review

addison: anything else?

Action Items

<addison> https://www.w3.org/International/track/actions/open

addison: 1183, discussion item later

addison: 1224, you see email from me, no reply yet
… seek more people to ask to check

addison: 1229, a bit more work, but writing some incl. for string-meta

addison: 1234, issues with meta charset in html, went back and read issues
… reviewed character set handling closely, original comment was to introduce charset into flagment sample whether to add charset or not
… could be nice to have one
… looking into all other charset stuff, I'd agree to close these issues
… in short, did action items, and to close

r12a: for these emails, some experiment, like latin-1 accent mark in html, I run into garbage depends on source location
… looked headers, no encoding there or utf-8 for some server

addison: for files, there are no header

addison: when I look at encoding in HTML, it seems full for me

r12a: even if in spec, what will happen when not doing so?

addison: to put in introduction, something like, to write utf-8 encoding

<addison> https://html.spec.whatwg.org/dev/introduction.html#a-quick-introduction-to-html

addison: do you want me to get back and write proposal?
… will try
… keep action item open, and make PR

Info Share

<r12a> openui/open-ui#600

r12a: came across with above issue, in open-ui
… forms works for vertical, which is good, but don't forget about Mongolian vertical-lr

<r12a> Japanese https://r12a.github.io/scripts/jpan/ja.html#interaction

<r12a> Chinese https://r12a.github.io/scripts/hani/zh.html#interaction

<r12a> Mongolian https://r12a.github.io/scripts/mong/mn.html#interaction

r12a: we don't have enough information for expectation, and made several examples
… if you come across this topic, see pictures
… also started gap reports on forms
… vertical text mentiones, and also for progress bars etc.

r12a: doing some work with @@@1
… new document as FPWD for Punjabi and Gurmukhi scripts, already have gap-analysis
… yesterday started with copying headings

<r12a> https://r12a.github.io/scripts/index.html#termbases

r12a: starting blocks from vocabulary
… been working well, and also changed UI to user friendly
… 151,331 entries there
… across 62 languages

<r12a> https://r12a.github.io/scripts/mong/mn_vocab.html

[example for script]

RADAR Review

<addison> https://github.com/w3c/i18n-request/projects/1

addison: we have rdf dataset canonicalization self review
… just a self review, I will have some questions on self review

addison: for in review, I have two issue for SPC

Pending Issue Review

<addison> w3c/i18n-activity#1647

addison: 1647 for SPC, they added number of items into data for request or return, our request is to add locale for example

<addison> w3c/i18n-activity#1648

addison: another, 1648 for SPC, they point an issue for display
… for us to decide whether to include issue into spec

r12a: having these should be useful

addison: will create an issue

Format of agendas in calendar

<addison> https://www.w3.org/events/meetings/be0342b6-7f8e-4050-af8a-0de6e86f8088/20230126T150000

r12a: looking into announcement around calendar, when agenda sent for this meeting, some are unlabelled

<r12a> https://www.w3.org/events/meetings/be0342b6-7f8e-4050-af8a-0de6e86f8088/20230126T150000

r12a: be prepared, that is the first for new users, and for agenda you have as headings and for agendabot

addison: top one is formattable, one for agendabot is picked by agendabot
… so agenda are in two places

r12a: that seems a bit strange

addison: agendabot recognizes 'topic:' and put into irc
… I can do another markup for 'topic:' and heading line

bert: if people likes to write agenda in heading style, could be inported into agendabot

[conversation on possible format, incl. adding comment between Topic: lines]

ACTION: addison: update the agenda format per discussion

<trackbot> Created ACTION-1235 - Update the agenda format per discussion [on Addison Phillips - due 2023-02-02].

Adding 't' labels to issues

r12a: I looked issue list and bunch does not have t: labels
… I've changed instructions for raising issues, highlighing t: labels
… when you raise issue, putting pending, try to find a section and put t: label
… anytime we get issue raised via PLH tools, need to add t: labels while removing pending
… I might need to send new instructions to him

<r12a> https://github.com/w3c/i18n-activity/issues/new?assignees=&labels=pending&template=add-a-review-comment--pending-discussion-by-i18n-wg-.md&title=Short_but_informative_title_here

addison: two pendings I raised, without t: label

<r12a> https://github.com/w3c/i18n-activity/issues/new?assignees=&labels=&template=create-a-tracker.md&title=Copy_the_title_of_the_WG_issue_here

r12a: check instruction shown in above link

r12a: in specdev, you have table of contents, which are picked for t: labels

String-Meta explainer

addison: in cooperation with conversations, and also for message format group
… will bring back to us once get something

AOB?

addison: any info about tracker bot?

r12a: no
… got message as stay tuned

addison: might need label for building dashboard

<Bert> (My bot is currently called GHURLbot, for GitHub-URL-bot, if you're interested. Looking for a better name...)

<JcK> .quit

rssagent, publish minutes