Internationalization Core Working Group Teleconference

Action Items

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

close ACTION-79

<trackbot> ACTION-79 Draft a blog post about HTML5 need for translate attribute, including why a language attribute can't do it closed

Info Share

<r12a> http://w3c-test.org/framework/results/i18n-html5/

richard: test framework stuff moving along
... this test suite is not complete
... and it's only one of several test suites I'm planning to put up
... need some coding on framework to allow to work without manual intervention

<r12a> http://www.w3.org/International/tests/html-css/character-encoding/results-basics

richard: no one to do that, which means i'm currently dead in the water until resources are available
... results summary pages
... will offer to html5 folks to use in their test suites

IRI Progress and Status Report from IETF82

peter: had a session at IETF meeting
... didn't talk much about work to be done at w3
... mostly work on 3987bis and 4395bis
... no one complained that W3C would work on iri reference/parsing document
... if anyone would like to provide feedback, need to get clear on that

richard: help to step back of outline of the documents

peter: had discussions about spinning up IRI WG
... wanted a document about parsing IRIs and URIs
... not something we've succeeded in IRI WG
... so move to W3C??
... other items on IETF's plate
... mainly 3987bis
... most difficult issues at IETF are:

peter: protocol vs. presentation element
... other issues, minor wording changes
... Larry Masinter and Martin Duerst working on that
... also have 4396-bis
... procedures for registering URI schemes
... updating to fit IRIs into that world
... and process related issues/descriptions in line with best practice and consensus on how it should work
... make it easier to register schemes
... some split out items
... one on bidi processing
... one on processing-but-not-parsing
... may merge back to 3987bis
... hope to finish early next year

addison: done means go to last call?

peter: yes. (explains IETF process)

<anne> http://tools.ietf.org/html/draft-abarth-url

<anne> is one such document

<r12a> document about how to properly parse an iri into constituent bits (Barth document)

<anne> abarth actually started from scratch

<stpeter> http://dvcs.w3.org/hg/url/raw-file/tip/Overview.html

peter: discussion with paul and sam at tpac
... want to pull out into separate document and work from there

<r12a> ... mike smith was going to take the point on this

<r12a> ... would be referenced by other specs

addison: just concerned that someone is on receiving end

peter: mike stepped up, we/html needs to figure out

richard: mike also had some questions

addison: do you see core spec dependent on parsing spec?

peter: no, but needs to coordinate, pay attention to same issues

anne: needs to be a REC
... unclear why split out from IRI?

<scribe> ACTION: addison: invite mike or set up supplementary call to discuss progress on IRI [recorded in http://www.w3.org/2011/11/23-i18n-minutes.html#action01]

<trackbot> Created ACTION-82 - Invite mike and martin or set up supplementary call to discuss progress on IRI [on Addison Phillips - due 2011-11-30].

richard: ask if a better day/time

JLReq

richard: heads up
... next tuesday will publish new working draft of JLReq
... task force is keen to press ahead
... not clear if WG needs to approve

<scribe> Chair: any objections to publishing this document?

<r12a> http://www.w3.org/TR/2011/WD-jlreq-20111129/Overview.html

richard: plan is to publish so we have dated version of WD, but short name will take you to the old version
... changes are there is a part 4

koji: agree to publish

mati: don't disagree

norbert: no objections to publishing a WD

<scribe> chair: WG approves publication

Review Felix's Blog Entry

http://lists.w3.org/Archives/Member/member-i18n-core/2011Nov/0006.html

richard: read and think it is pitched incorrectly
... what we really need is something that summarizes pros/cons in bugzilla thread
... so we can get MS and Google people on same page

norbert: can't tell what @translate would do/not do
... from article

addison: need examples

richard: first part of second para... this is not a problem of translation agenices (etc.)
... is a problem for them, but needs to be solved before it gets to them

norbert: they do care, but cannot fix it

richard: obtained a contact at google about this topic

<scribe> ACTION: richard: talk to felix about fixing draft of blog article on 'translate' attribute [recorded in http://www.w3.org/2011/11/23-i18n-minutes.html#action02]

<trackbot> Created ACTION-83 - Talk to felix about fixing draft of blog article on 'translate' attribute [on Richard Ishida - due 2011-11-30].

ECMAScript Globalization Progress

norbert: lot going on last week
... had meeting of i18n ad hoc to work on standard
... discussion was focused on making things less specified
... allowed for alternative algorithm for "best fit"
... went to TC39 next day
... and they feel things are too loosely specified
... and they want same behaviro for a given locale
... lots of discussion
... in particular setting global locale
... but there are problems with that
... another person wants pattern or skeleton instead of options
... still working on es-discuss to try and resolve

AOB?