See also: IRC log
http://www.w3.org/International/track/actions/open
action-440?
<trackbot> action-440 -- Richard Ishida to Follow up with daniel about ethiopic information -- due 2015-05-14 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/440
close action-440
<trackbot> Closed action-440.
richard: did this, waiting for a response from him
action-441?
<trackbot> action-441 -- Richard Ishida to Write back to fantasai/csswg and propose a way to organize layout information -- due 2015-05-14 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/441
richard: did chat with fantasai, need to type up results
close action-441
<trackbot> Closed action-441.
https://www.w3.org/International/wiki/Review_radar
https://www.w3.org/International/wiki/Project_radar
richard: put "rangefinder" into radar?
addison: will do
richard: adding some of your
guidelines to document, will post soon
... just throwing them in, not "carefully crafting"
... "you have been warned"
... counter styles: plan to change hebrew
... css will reissue and we'll need to track
... some updating on articless
... use of <b> and <i>
... syncing text quotes from html5 to the document
... message remains the same
<r12a> http://www.w3.org/2014/Process-20140801/#last-call
addison: proposal to change this WG to the 2014 process
<scribe> ACTION: addison: remind working group to read new process document for adoption voting at next week's teleconference [recorded in http://www.w3.org/2015/05/14-i18n-minutes.html#action01]
<trackbot> Created ACTION-442 - Remind working group to read new process document for adoption voting at next week's teleconference [on Addison Phillips - due 2015-05-21].
richard: fantasai from css
... asked if we can warehouse information about non-latin
script
... specifically justification rules
... how this or that script does it
... sounds reasonable
... doing this in layout requirements
... other information outside layout reqs tho
... could make small documents for other scripts
... but when you get lots and lots of documents it gets harder
to maintain/keep track of
... thing to point to might be wiki
<r12a> https://www.w3.org/International/wiki/Typography
richard: above wiki page points
to different requirements and spec descriptions and tests and
such
... also external information as well
... for latin and non-latin
... ideas for how to move forward?
... possibility of getting an ethiopic layout requirements
document
addison: desire for an arabic script document
richard: was approached at IUC about possibility, might get back to that
<scribe> ACTION: richard: contact interested parties about starting an Arabic script layout task force [recorded in http://www.w3.org/2015/05/14-i18n-minutes.html#action02]
<trackbot> Created ACTION-443 - Contact interested parties about starting an arabic script layout task force [on Richard Ishida - due 2015-05-21].
richard: if you know about information about non-latin script, please send links
Media Capture and Streams
https://www.w3.org/International/track/products/78
issue-464?
<trackbot> issue-464 -- 'label' needs direction and language metadata ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/464
issue-465?
<trackbot> issue-465 -- Human readable message not localizable? ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/465
Generating JSON from tabular data
https://www.w3.org/International/track/products/79
issue-466?
<trackbot> issue-466 -- Can JSON data be generated from non UTF-8 encoded CSV data ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/466
steve: no mention if csv has to
be encoded in utf-8
... model allows legacy encodings
addison: implicit
conversion
... not even Encoding spec, since they support *any*
encoding
richard: should have health warning about conversion
steve: "be explicit"
issue-467?
<trackbot> issue-467 -- What are the rules for string equality when column names are matched with annotations ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/467
steve: can have names in
columns
... what are the rules for identifier equality?
... no statement
... normailized or not?
issue-468?
<trackbot> issue-468 -- Do Unicode Strings get normalized when placed into JSON data ⓟ -- open
<trackbot> http://www.w3.org/International/track/issues/468
steve: when generating json data,
are they normalizing?
... no mention
... NFC required? or implementation detail?
addison: 1. use a normalizing
transcoder
... 2. don't normalize text already in a unicode encoding
steve: will propose text
... probably all of this appliable to the RDF spec too
Web payments use cases
richard: sent an email out
<r12a> http://lists.w3.org/Archives/Public/www-international/2015AprJun/0057.html
richard: items I found were not
specifically i18n
... will send these along
http://w3c.github.io/charmod-norm/
https://lists.w3.org/Archives/Public/www-international/2015AprJun/0059.html
addison: reorder sections
https://lists.w3.org/Archives/Public/www-international/2015AprJun/0061.html
wildebeest->resource
namespace->vocabulary
addison: will post changes this week