See also: IRC log
trackbot, prepare teleconference
<trackbot> Date: 25 July 2012
<scribe> Scribe: Addison Phillips
<scribe> ScribeNick: aphillip
2 adds from richard
action-81: in progress
<trackbot> ACTION-81 Create blog post on what's going on with IRI notes added
<trackbot> ACTION-108 Remind everyone to read and comment on IRI documents closed
<trackbot> ACTION-118 Read and comment on bidi tutorial update at http://www.w3.org/International/tutorials/new-bidi-xhtml/Overview-inline.en.php#where (AND ALL GROUP MEMBERS) closed
<trackbot> ACTION-120 Remind WG members to read http://www.w3.org/International/docs/ruby/editme.html with a mind to publishing FPWD (AND GROUP MEMBERS) closed
<trackbot> ACTION-123 Remind all group members to review other bidi documents in the Core Pipeline for wide review by next week (AND ALL GROUP MEMBERS) closed
<trackbot> ACTION-127 (AND ALL GROUP MEMBERS) study additional bidi controls proposal and express support or lack of support for it at Unicode closed
<trackbot> ACTION-137 Make a wiki page with the basis for general guidelines for everyone to pile on closed
richard: if you work with the
UnicodeData.txt file at all
... see above blog entry
... have a new tool for parsing and displaying the data
... checks for valid syntax in the data file
... and you can edit a line and generate a new version of UnicodeData.txt
... useful if you want to propose a character
... another thing I did
... was expand Uniview slightly
... gives more info about scripts and such
richard: third and most important
thing I did in Geek Week
... was update test results pages
... see above link for current
... and new version:
richard: now pulls data live from
... makes it really fast to make a page
... some bad results need cleanup and such
... at some point need to convert pages over
11. Example Document http://www.w3.org/TR/html-polyglot/#example-document The i18n WG would prefer the example code in section 11 to have a visible encoding declaration (ie. <meta charset="utf-8"/>. This would illustrate the points made in section 3.
addison: support this
<matial> no pb
richard: do we need to start
clearing .prep issues out?
... favor sending/forwarding comments that no one asks to close or discuss
<scribe> ACTION: addison: send email(s) to the winter list asking for any .prep issues that need closing or discussion [recorded in http://www.w3.org/2012/07/25-i18n-minutes.html#action01]
<trackbot> Created ACTION-141 - Send email(s) to the winter list asking for any .prep issues that need closing or discussion [on Addison Phillips - due 2012-08-01].
norbert: how many?
richard: 19 or so
norbert: not so bad
richard: started trying to work
through bugzilla issues
... hixie is moving away from HTML5 towards HTML-next
... so assigning off remaining reports
... so do we continue threads on bug reports?
<r12a> sounded fine to me
felix: look at these pages: give background on editors and such
however; time + zones are used as political footballs and are thus subject to very + whimsical policy decisions.</p>
<scribe> chair: objections to closing as satisfied?
okay to close
<r12a> close Issue-165
<trackbot> ISSUE-165 Add character encoding declaration to section 11 closed
Because I wrote the example and know to what event the example refers, and the example happened on the east coast. And the spec says so. There's no way to know this just from the date, but as mentioned in the #1 above, that's just a limitation of the ISO format.
One millisecond after noon on October 14th 1979, in the time zone in use on the east coast of the USA during daylight saving time.
addison: insert "which might be"
<r12a> One millisecond after noon on October 14th 1979, in the time zone in use, which might be on the east coast of the USA during daylight saving time.
<r12a> One millisecond after noon on October 14th 1979, in the time zone in use, which might, for example, be on the east coast of the USA during daylight saving time.
well, more like: One millisecond after noon on October 14th 1979, *which might be* in the time zone in use on the east coast of the USA during daylight saving time.
It should be made clear that a zone offset is not the same thing as a time zone. Mention should be made of the need for separate time zone information when working with real date and time values in use cases that depend on it (see our note "Working with Time Zones")
just adding "which might be" is not sufficient
richard: need to suggest
Note: the zone offset is not a complete time zone specification. When working with real date and time values, consider using a separate field for time zone, perhaps using IANA time zone IDs.
and @ref WWTZ note
section 18.104.22.168: probably needs a note
norbert: file a separate ticket to say that IANA time zones need accomodation
<scribe> ACTION: addion: file a ticket on HTML5 asking for accommodation of IANA time zone IDs [recorded in http://www.w3.org/2012/07/25-i18n-minutes.html#action02]
<trackbot> Sorry, couldn't find user - addion
<scribe> ACTION: addison: file a ticket on HTML5 asking for accommodation of IANA time zone IDs [recorded in http://www.w3.org/2012/07/25-i18n-minutes.html#action03]
<trackbot> Created ACTION-142 - File a ticket on HTML5 asking for accommodation of IANA time zone IDs [on Addison Phillips - due 2012-08-01].
mark this one as "not yet satisfied"?
<fsasaki> <its:localeFilterRule selector="//legalnotice[@role='Canada']" localeFilterType="include" localeFilterList="en-CA, fr-CA"/>
addison: consider extended filtering?
*-CA covers other languages spoken in Canada, such as Inuktitut, etc.
<scribe> ACTION: felix: convey to ITS feedback about considering using of extended filtering in ITS 2.0 [recorded in http://www.w3.org/2012/07/25-i18n-minutes.html#action04]
<trackbot> Created ACTION-143 - Convey to ITS feedback about considering using of extended filtering in ITS 2.0 [on Felix Sasaki - due 2012-08-01].
richard: keep direction in separate thread
<scribe> ACTION: addison: satisfied with language but not with direction using separate emails on the separate threads [recorded in http://www.w3.org/2012/07/25-i18n-minutes.html#action05]
<trackbot> Created ACTION-144 - Satisfied with language but not with direction using separate emails on the separate threads [on Addison Phillips - due 2012-08-01].
remind on writing-mode
read turtle for next week's agenda?
turtle it is
richard: include that we are looking for IG comments too
addison: will generate boilerplate
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/linke/link/ Succeeded: s/issues out/issues out?/ Succeeded: s/useing/using/ Found Scribe: Addison Phillips Found ScribeNick: aphillip WARNING: No "Present: ... " found! Possibly Present: Norbert Note P18 P26 ScribeNick aaaa action-81 addison andrewc felix fsasaki https i18n joined matial r12a richard trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Regrets: David Agenda: http://lists.w3.org/Archives/Public/www-international/2012JulSep/0046.html Found Date: 25 Jul 2012 Guessing minutes URL: http://www.w3.org/2012/07/25-i18n-minutes.html People with action items: addion addison convey email felix s send[End of scribe.perl diagnostic output]