Internationalization Working Group Teleconference

07 Apr 2016


See also: IRC log


Felix, Addison, Richard, JcK
Steve, JcK
Addison Phillips
Addison Phillips


<r12a> http://w3c.github.io/i18n-activity/projects/


Action Items



<trackbot> action-174 -- Addison Phillips to Write article about floating times in HTML -- due 2013-01-30 -- OPEN

<trackbot> http://www.w3.org/International/track/actions/174

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



<trackbot> action-461 -- Richard Ishida to Re-read issue-80 and evaluate whether to reopen as a github issue or not -- due 2015-09-10 -- OPEN

<trackbot> http://www.w3.org/International/track/actions/461

richard: should mark as closed
... looked at another thing

richard: wrote to ebook list and www-international about quotes

<r12a> https://lists.w3.org/Archives/Public/public-digipub-ig/2016Apr/

<r12a> https://lists.w3.org/Archives/Public/public-digipub-ig/2016Apr/0022.html

close action-461

<trackbot> Closed action-461.


<trackbot> action-503 -- Addison Phillips to Add unicode-xml to project radar -- due 2016-04-07 -- OPEN

<trackbot> http://www.w3.org/International/track/actions/503

close action-503

<trackbot> Closed action-503.

Info Share

felix: share progress xliff/its integration
... xliff 2.1 finalizing in june
... supports its 2.0
... ITS-IG has helped move forward

process stuff

<r12a> https://lists.w3.org/Archives/Member/member-i18n-core/2016Apr/0005.html

richard: echidna could work for docs not on req
... can publish a Note as a Note, but not the WDs :-(
... maybe in 2-3 weeks could do that
... meantime need WG agreement to publish using echidna

addison: (waxes enthusiastic)

addison: proposal to adopt echidna-based publishing to TR for all WG documents from now on

<fsasaki> big +1

<David> +1

<Addison> +1

<r12a> big +1

addison: (chair hat) so approved, since there were no objections raised over email either during the past week

richard: send your comments by github and against latest dated version in TR
... can't produce a dated version in github we thought
... but possible to do for a specific commit

<fsasaki> [sorry, have to go, for this topic either way is fine for me]

richard: 2 scenarios
... for charmod and clreq
... TR far behind github
... text is more up to date
... closer to issues list
... other scenario is unicode-xml
... it's published as a Note and martin is making edits
... very messy

addison: only use TR for like FPWD or Last Call?

richard: well, the unicode-xml might be a different case

The "Quotation Thing"

<r12a> https://lists.w3.org/Archives/Public/public-digipub-ig/2016Apr/0013.html

richard: what do you do whne you have multiple nested quotes in multiple languages
... clear if in one language

Mais Lucy répond: «Embrassez George de ma part - seulement une fois. Dites-lui, ‹Embrouille.› ».

Mais Lucy répond: «Give George my love – once only. Tell him, 'Muddle.' ».

richard: sent do www-international and e-books
... consensus so far is "if you start the para in say French, you use throughout"
... avoids confusion

<r12a> https://lists.w3.org/Archives/Public/public-digipub-ig/2016Apr/0022.html

richard: just sent the above
... how do you actually make happen
... CSS and HTML don't produce this
... wanted to get you thinking about this
... what punct. goes where?
... "am I in a quotation" and then am I dealing with a q with a lang
... if inside a quote and have a lang, then ignore it
... not quite sure how to do that in css yet

addison: agenda next week to discuss?

<scribe> ACTION: addison: remind group to study quotation mark behavior for next call [recorded in http://www.w3.org/2016/04/07-i18n-minutes.html#action01]

<trackbot> Created ACTION-506 - Remind group to study quotation mark behavior for next call [on Addison Phillips - due 2016-04-14].


richard: might have come through in my comments
... not sure, putting some ideas out for feedback
... starting to wonder if focus of document is clear
... talking about confusables, is a problem...
... but wondering how relevant
... is our focus on the syntactic elements rather than the text content
... findtext is bigger labyrinth
... other question in my mind
... can see why users might expect visual vs. encoding
... some many languages where you can expect that

addison: (expounds at length)


Summary of Action Items

[NEW] ACTION: addison: remind group to study quotation mark behavior for next call [recorded in http://www.w3.org/2016/04/07-i18n-minutes.html#action01]

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/04/12 11:14:13 $