See also: IRC log
close ACTION-139
<trackbot> ACTION-139 Update qa-byte-order-mark document closed
close ACTION-148
<trackbot> ACTION-148 Write to Korean folks and ask them to consider bringing work to our activity closed
<r12a> http://www.w3.org/International/track/actions/open
richard: if you want to speak at/attend MLWeb conf in Rome, send application now
felix: making you aware that they
want to go to LC Dec 4 or Dec 11
... so features need to be complete and with ed staff in next
two weeks
... have a plan for a f2f meeting in prague 23-24 January
<matial> I would like to have the bidi stuff next, since I must leave in 20 mns
felix: can richard perhaps participate
http://www.w3.org/International/wiki/Html-bidi-isolation
richard: proposal to have a blog
post
... aharon wrote most
... includes new attrs
... and things we discussed in html wg
... aharon not convinced that suggestions are all valid
... such as css being used to get around backwards compat
... need to add more info about backwards compat
... and that aharon and I think rli/lri are good values for
@dir
... need to decide where to publish
... please look at it
<scribe> ACTION: addison: remind everyone to review Html-bidi-isolation blog post for next week [recorded in http://www.w3.org/2012/11/21-i18n-minutes.html#action01]
<trackbot> Created ACTION-160 - Remind everyone to review Html-bidi-isolation blog post for next week [on Addison Phillips - due 2012-11-28].
mati: read about 2/3 of it
... like it, buy the arguments
https://lists.w3.org/Archives/Member/member-i18n-core/2012Nov/0012.html http://www.w3.org/International/tutorials/new-bidi-xhtml/Overview-inline-2.en.php
richard: if you scroll down you
see pink background bits
... these cover html5
... propose that
... this document proposes that you use markup everywhere dir
changes
... propose that we hide the html5 stuff for now
... because html5 is still changing
addison: want to ensure that markup should be consistent going forwards
norbert: any breaking changes?
richard: shouldn't be
... don't want to say <bdi><cite> if we then change
to <cite dir="rli">
... also changed some of article structure
... added some of norbert's suggestions and such
... old structure was more complicated
... so simplified
<scribe> ACTION: addison: remind everyone to review new-bidi-xhtml document for next week [recorded in http://www.w3.org/2012/11/21-i18n-minutes.html#action02]
<trackbot> Created ACTION-161 - Remind everyone to review new-bidi-xhtml document for next week [on Addison Phillips - due 2012-11-28].
http://www.org/International/questions/new/qa-byte-order-mark-new.en.php
richard: similar story here
... think this is ready for wide review
... perhaps look at it first
... want to incorporate any additional issues folks are aware
of
... may want to deprecate the other article we have
<r12a> http://www.w3.org/International/questions/qa-utf8-bom
<scribe> ACTION: addison: remind everyone to review qa-byte-order-mark-new for next week [recorded in http://www.w3.org/2012/11/21-i18n-minutes.html#action03]
<trackbot> Created ACTION-162 - Remind everyone to review qa-byte-order-mark-new for next week [on Addison Phillips - due 2012-11-28].
richard: above link is article to obsolete
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17918
http://lists.w3.org/Archives/Public/www-international/2012OctDec/0074.html
For example, a user agent might support numeric input in the user's local format, converting it to the format required for submission as described above. This might include handling different grouping or decimal separators (such as "12.456,78", as customary in many European locales) or local digit shaping (such as the use of digits in Arabic, Persian, Devanagari, Thai, and other scripts) or a combination thereof.
norbert: concerned about:
User agents must not allow the user to set the value to a non-empty string that is not a valid floating-point number. If the user agent provides a user interface for selecting a number, then the value must be set to the best representation of the number representing the user's selection as a floating-point number. User agents should allow the user to set the value to the empty string.
"user agents must not interpret user input to set the value to a non-empty string that is not a valid..."
"user agents must not interpret input..."
"user agents must not set the value..."
user's input not desired in the conversation, it's just the user-agent's interactoin with the value
richard: "the internal representation of the value supplied by the user"
value => string
12345,67
<input lang=fr type=numeric>
scribe: but browser is set to spanish... then fr should win
123.456
123,456
norbert: will send an email about things to be careful about in uts35