– DRAFT –
Internationalization Working Group Teleconference

<addison> trackbot, prepare teleconference

Agenda Review

Action Items

addison: noticed about github repository for idn/http

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

addison: 1094, depends on TAG

addison: 1133, not yet done, need some time for update
… 1134, will work this week

addison: 1137?

r12a: have to go back to the discussion last week

addison: saw comment on the issue

r12a: did comment on the thread, will follow later

addison: 1138, i did and all of them were satisfied, and closed

<addison> action-1138?

<trackbot> action-1138: Addison Phillips to Check indexeddb issues -- due 2022-04-14 -- OPEN

<addison> close action-1138

<trackbot> Closed action-1138.

Info Share

<r12a> https://w3c.github.io/i18n-drafts/articles/ruby/styling.en

r12a: link above, an article, last update 2016
… started working on this again, this week
… haven't posted updates yet

addison: what is focus on your revision?

r12a: first section is for basic configurations, what you will do what will happen
… tends how Japanese use, and Chinese uses
… following sections are tweaks, like below or above
… trying to a bit more information, about when you will do rather than just you can, for reason you want to do
… syntax on test on your browser, more inline like MDN docs
… plus, updating information what browsers support
… rb parsing also on Chrome, so update with that information
… havn't updated along with MDN docs

addison: cool to have tests in the page. people can check with these

r12a: not hard to do, just to place things

RADAR Review

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

r12a: I know people are discussing on ruby terminology, not to stop these, but back them later

addison: no new request for review
… xfq put number of pending issues on webgpu, wait for next week

addison: SPC, got email to set phone call later today
… expect to move this item somewhere else

addison: any resolution?

addison: CSS-cascade, in 2020, to mark as closed - all issues closed

addison: no objection, move to completed

addison: also for css-logical

request to approve preparation of new WG Note for English ruby terminology and to have a new repository

atsushi: reported last week, in JLTF call this week
… discussed ruby terminology
… most attendees have some reaction to japanese terminology
… not so interested in English
… most positions neutral, but okay to proceed
… kida-san is performing last review on explainer on terms we want to propose
… want to propose to have separate draft of WG-Note and want new W3C repo
… not easy to a list of terms, one term with short description
… concluded to propose to start drafting dedicated document

https://github.com/w3c/jlreq/pull/331

richard: link to the text?

atsushi: ^^^

atsushi: once new repo, seek comments from wider community including clreq and css

richard: not sure about having separate repo
… might want to integrate with i18n-glossary
… helpful to have examples and a bit more than we'd have in glossary

<r12a> https://www.w3.org/International/questions/qa-ruby.en

richard: one is that we have an article "what is ruby"
… it's a short article, but has some on japanese ruby
… article I mentioned in info share and its companion have some examples
… another possibility is that rather than writing a new document that we write an article
… we have essential concepts for character encoding, other topics, could have one

addison: is the goal to have something in the TR space??

atsushi: want to refer to definitions from css-ruby

<r12a> https://www.w3.org/International/articles/ruby/markup.en#mono_group_etc

atsushi: glossary is one possibility, but something in /TR is desired

richard: definitions need to cover japanese, chinese, and mongolian
… possibly not Korean but maybe

atsushi: for this time we want to have language-independent
… something in simple-ruby is not in our scope

addison: don't want to force it; using japanese words is okay if there is nothing better (cf. mojibake, ruby)

richard: some other examples.... at bottom
… we've been calling this "tabular ruby" (calls out "layered")

atsushi: murata-san's idea was concept independent, not sure where want to go

richard: when it comes to things like 'para ruby', might be useful, move away from japanese because not explanatory
… making more general so fits other languages is a good goal
… people who find it think it can be used for glossing text in any language
… any interlinear == ruby is not a good idea
… move a little way but not too far

atsushi: have both terms, interlinear and ruby? some people complain about mixing
… at this moment want brought terms

fantasai: want to mention if this were a doc on the TR pages
… no opinion if in glossary or in a standalone doc
… useful to have explanation with terms

richard: were talking about alternatives, we have an article that explains ruby
… 2 more about styling et al
… these are other things we can look at
… have to have this terms in the i18n-glossary, but it's just a link source, not a doc you'd read
… glossary can point out to docs

(addison points out that it *does* point out)

fantasai: murata-san's goal is to have it ref from jlreq, clreq, etc. plus outside W3C

richard: that's what glossary is

<r12a> i18n-glossary

https://github.com/w3c/i18n-glossary/

richard: too generalized is not helpful

<fantasai> “intermittent ruby”

richard: some sort of term like maybe "inline annotation"
… mechanism in ja/zh/etc. is ruby

fantasai: try to draft a pull request

richard: ruby is a technique for doing inline annotations
… it's a *way* of doing it

ACTION: atsushi: convert ruby terminology to wiki page for direct comments and track progress for i18n

<trackbot> Created ACTION-1139 - Convert ruby terminology to wiki page for direct comments and track progress for i18n [on Atsushi Shimono - due 2022-04-21].

AOB?