Internationalization Working Group Teleconference

Agenda?

Action Items

http://www.w3.org/International/track/actions/open

felix: any news on ACTION-284

action-284

<trackbot> action-284 -- Felix Sasaki to Write back to xliff and its-ig with summary of our discussion -- due 2014-02-13 -- OPEN

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

Info Share

richard: went to Oman
... MLWeb conference
... in Madrid last week
... spoke about the layout requirements documents that we've been developing

<r12a> http://www.multilingualweb.eu/documents/2014-madrid-workshop/2014-madrid-program

richard: oman meeting
... google is working on solutions
... not highest priority
... but being worked on
... microsoft as well
... took copious notes
... want to write a summary
... for example, looking at handling IDNs in gmail
... I talked about URLs as a whole
... and that brings additional things
... they were mostly concerned about top two levels of IDNs

jck: gmail folks have said in various places that they won't support non-ASCII local parts

richard: why percent escaping for domain part of web address?

addison: larry masinter notes that this is seen in DNS server logs

richard: maybe push for punycode all the time
... some folks suggested punycode all the time for local part (user name)

addison: apis produce percent encoding

jck: mail servers have to be specifically set up to accept punycode local part
... only utf-8 through consistent

richard: order of email addresses in RTL
... email addresses show RTL
... and HTTP on the right side
... also want to get rid of the "http://" part
... and 'www' because they are ASCII

addison: spoke at SFGlobalization

http://www.meetup.com/sf-globalization/events/174718202/

http://bit.ly/sfglobalization-the-multilingual-web

Review Radar

https://www.w3.org/International/wiki/Review_radar#Scheduled_Last_Call_reviews

Tracking DNT, CSS Variables, DOM Parsing

<r12a> http://w3c.github.io/csvw/syntax/index.html#parsing

richard: work going on on CSV metadata
... went to a talk by Ivan Hermann
... want to publish more widely in about four weeks
... mgiht be simpler if we comment now

richard to shepherd

richard: also a requirements document somewhere. will send link

<r12a> http://w3c.github.io/csvw/use-cases-and-requirements/index.html#can-req

<scribe> ACTION: richard: write a trip report/summary of the universal access meeting [recorded in http://www.w3.org/2014/05/15-i18n-minutes.html#action01]

<trackbot> Created ACTION-305 - Write a trip report/summary of the universal access meeting [on Richard Ishida - due 2014-05-22].

action-284

<trackbot> action-284 -- Felix Sasaki to Write back to xliff and its-ig with summary of our discussion -- due 2014-02-13 -- OPEN

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

felix: now part of the XLIFF TC

Encoding

https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=__open__&content=Encoding&list_id=36917&order=component&product=WHATWG&query_format=specific

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16691

richard: could get get Anne to put notes in the spec where there are open issues?

<scribe> ACTION: addison: ping Anne about adding notations for where bugs are located [recorded in http://www.w3.org/2014/05/15-i18n-minutes.html#action02]

<trackbot> Created ACTION-306 - Ping anne about adding notations for where bugs are located [on Addison Phillips - due 2014-05-22].

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16685

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21057

Proposed solution: Define a replacement encoding that decodes all possible byte values to the REPLACEMENT CHARACTER. Make the known labels for ASCII-incompatible encodings that exist but aren't part of the Encoding Standard aliases for the replacement encoding.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23971

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17053

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25339

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19961

<JcK> The other problem with going further down the path of legitimizing sometimes-deliberate violations of what the encoding identifiers are intended to mean is that I'm seeing increasing amounts of email with an encoding that is labeled in various ways but I've started describing as UTF-2312.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23317

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21556

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23154

richard: follow up to see if anything has happened on that since september

AOB?

<r12a> addison, don't forget slide 30 ;-)