See also: IRC log
koji: discussion with Kobayashi-san, should invite them to work at w3c
<r12a> http://www.w3.org/International/track/actions/open
<scribe> ACTION: addison: write to Korean folks and ask them to consider bringing work to our activity [recorded in http://www.w3.org/2012/09/19-i18n-minutes.html#action01]
<trackbot> Created ACTION-148 - Write to Korean folks and ask them to consider bringing work to our activity [on Addison Phillips - due 2012-09-26].
richard: can use a task force,
don't need to worry so much about member fees and such
... and addison should invite in his official capacity
close ACTION-109
<trackbot> ACTION-109 Check about Korean layout task force closed
ACTION-139: updated document but not completed just yet
<trackbot> ACTION-139 Update qa-byte-order-mark document targetting end-of-August for review notes added
Prepare some examples of ITS2NIF showing NFC issue for consideration next week
ACTION-145: set date to mid-october
<trackbot> ACTION-145 Prepare some examples of ITS2NIF showing NFC issue for consideration next week notes added
Norbert: yesterday TC39 approved
ECMAScript i18n API
... and sent to general assembly
... final standard soon!
richard: re-write line-break tests, made some fixes on line-break normal
<r12a> http://www.w3.org/blog/International/2012/08/30/new-tests-line-breaks-in-css3-text/
<r12a> http://www.w3.org/International/questions/new/qa-byte-order-mark-new.en.php
richard: started re-working
document
... taking onboard some feedback from Leif
... he'd favor encouraging the BOM all the time
... I'm not so sure
... but it no longer hurts so much
... started reworking the "display issues" document related to
this one
... and so this article combines the two together
... what do I need to know? potential issues? etc.
... could use help on potential issues
... these things are "fading gently away"
... but tend to be edge cases nowadays
andrewc: many pages made of
multiple files
... what happens when put together on the fly?
richard: text will continue to
change a bit
... potential issues with utf-8 bom: please send
recommendations
... read through as initial draft and send me comments
... not so much editorial comments
norbert: only at end mentioning
utf-32
... so mention 16/32 early
... and then talk about use as a signature for 8
... and flow from there
<matial> Sorry, but my phone connection is down and refuses to be come alive again.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16962
The I18N Core WG previously resolved that we did not agree with Ian's comments on or closing of 17857 and we don't agree with closing this item without addressing it. Please reconsider this bug.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16960
The I18N WG would like you to consider several ways of addressing the issues raised by the 'local date and time' microsyntax. One way of addressing it would be to define it in terms of a floating time value, although floating times are usually either a date (with no hour/minute/second value) representing an event such as a birthdate that is not ties to a specific time zone or to a time (with no day/month/year) which can be interpreted as a local wall time i
norbert: need to make a proposal
for how to integrate IANA time zones to HTML
... provide an element or attribute for time zone
... 8601 doesn't provide for time zone
<scribe> ACTION: Norbert: draft a proposal for adding time zone IDs to HTML5 [recorded in http://www.w3.org/2012/09/19-i18n-minutes.html#action02]
<trackbot> Created ACTION-149 - Draft a proposal for adding time zone IDs to HTML5 [on Norbert Lindenberg - due 2012-09-26].
addison: think 16960 should define relationship of local time to the "world of time"
richard: have a list of issues that we should review
<scribe> ACTION: addison: review list of HTML5 issues and publish a summary [recorded in http://www.w3.org/2012/09/19-i18n-minutes.html#action03]
<trackbot> Created ACTION-150 - Review list of HTML5 issues and publish a summary [on Addison Phillips - due 2012-09-26].
addison: perhaps glance at timed text's new document
richard: have quite a few html5 prep issues
<r12a> http://www.w3.org/International/track/issues/open?sort=product
addison: will review the .prep issues as part of making a summary
richard: koji, when doing
line-break tests...
... (looks for a link)
<koji> http://dev.w3.org/csswg/css3-text/#line-break
richard: in that section, here
are the line break properties
... strict, loose, normal
... and "here are some characters in Japanese" that should be
treated in a particular way
... not in the list are parens and ideographic full stop
... this list is only the ones that have special cases?
koji: yes, this is only the exceptions
richard: maybe insert a comment to that effect to make it clear
koji: will discuss with fantasai