See also: IRC log
WOFF added
Finish edits and convert time zones document to HTML
Talk with Bert about how to deal with change marks in Ruby spec
not yet. they have their f2f currently. two weeks
Rewrite response with new proposal to do normalization in comparison
Forward revised normalization letter to CSS including information about namespaces
One piece of information for "infoshare": there will be a conference about multilingual technologies (including both i18n related topics but also language technologies like machine translation, various European and international language communities, politicians etc.) at the end of June in Budapest. This may be of interest for some of you.
(above from Felix)
<r12a> http://www.w3.org/International/track/products/1
r12a: chris sent some responses... let's take them one by one
<r12a> http://www.w3.org/International/track/issues/2
r12a: why aren't you using
xml:lang? but maybe not xml:lang, since for identifying
localizations
... so might be a language attribute
... they want to use xml:lang
... last email has their formal response
Several elements store their data in text child elements; this is to support localization. The text elements MAY be given a lang attribute in the XML namespace [XML]. For backwards compatibility, lang attributes in the default namepsace are also accepted in older content, and SHOULD be treated the same as xml:lang. New content SHOULD instead use xml:lang.
r12a: legacy content can use @lang to be interpreted as xml:lang
addison: don't have any
restrictions with "MAY"?
... do they define 'match' using bcp47?
<scribe> chair: consensus?
richard: think that it shouldn't
have been an xml:lang
... could use <span> to tag content contained in another
language
no objections
<matial> no pb
http://www.w3.org/International/track/issues/4
http://www.w3.org/International/track/issues/5
they rejected
r12a: they rejected because it would invalidate existing content; agree in principle, but can't do it
addison: can't have externally applied dir or lang
r12a: "well, we tried..."
... made our point clearly and they understand, but still
decided this way
addison: so disagree, but will not object
http://www.w3.org/International/track/issues/6
r12a: other information could
appear in different languages
... that is not localizable
... things like vendor credit and licensee
... all represented by elements but only one can appear
... their response: could just use parenthesized aside
addison: works only if you have two
r12a: arabic, hebrew, urdu, etc... mixed direction text probably wouldn't look right (like with parens!)
BIDI FONT CO (english)
addison: so, push back?
<r12a> WERBEH w3c (world wide web consortium)
r12a: I would probably
http://www.w3.org/International/track/issues/7
<scribe> done what we asked
http://www.w3.org/International/track/issues/8
<scribe> done
http://www.w3.org/International/track/issues/9
just decided to accept our wording
"The automatic removal of OpenType features such as GPOS and GSUB information at any stage in the process of deploying a WOFF file is strongly discouraged. Many writing systems around the world rely on these features for very basic display of text in the script that they use."
we want to push back on 2 and 6, and we object to 5 but will not pursue
we want to push back on 6 but not 2
<scribe> ACTION: richard: reply to WOFF indicating our acceptance/non-acceptance of issues per 2011-06-01 telecon [recorded in http://www.w3.org/2011/06/01-i18n-minutes.html#action01]
<trackbot> Created ACTION-44 - Reply to WOFF indicating our acceptance/non-acceptance of issues per 2011-06-01 telecon [on Richard Ishida - due 2011-06-08].
http://www.w3.org/International/questions/qa-personal-names
richard: wrote a blog post awhile
ago and so converted to this document
... and here it is
... should we move to wide review?
... did put some feedback in
http://inter-locale.com/whitepaper/IUC26-a302-Names.pdf
addison: think it's ready for wide review
aharon: fascinating article
... not sure that specific recommendations are always something
that can be implemented
... may not be practical solutions
... if you can, use single name field
... if you need sort name, greeting/salutation, etc.
... you end up asking lots of questions or to repeat
information
... confusing user
<r12a> addison: if you build a full solution it's really complicated, so you need to look at your user's needs, and decide on the scope you need
richard: make the "general guidelines" aspect more obvious
<aharon> not really
addison: ready for wide review still? or want to think about it?
richard: no, it is what review is
for....
... will look at Mark's comments first
<scribe> ACTION: richard: publish qa-personal-names for wide review [recorded in http://www.w3.org/2011/06/01-i18n-minutes.html#action02]
<trackbot> Created ACTION-45 - Publish qa-personal-names for wide review [on Richard Ishida - due 2011-06-08].
(addison summarizes....)
<aharon> can you throw some urls at us?
http://lists.w3.org/Archives/Public/www-international/2011AprJun/0060.html
http://lists.w3.org/Archives/Public/www-international/2011AprJun/
<matial> who is the owner of charmod-norm?
we are the owners
http://www.w3.org/TR/charmod-norm/
move to note path from rec track
richard: publish a new working
draft; plus wiki page stating current thinking
... WD says "work in progress"
finding source is first hurdle
could dump source and start with html version
basically update status of the document
<scribe> ACTION: addison: dump charmod-norm and add disclaimer paragraph, dates, etc. so that we can publish an interim working draft [recorded in http://www.w3.org/2011/06/01-i18n-minutes.html#action03]
<trackbot> Created ACTION-46 - Dump charmod-norm and add disclaimer paragraph, dates, etc. so that we can publish an interim working draft [on Addison Phillips - due 2011-06-08].
keep same, change status, dates, and from rec to note
richard will do it starting two weeks from now if addison works on the wiki in the meantime
http://www.w3.org/International/docs/timezones/Overview.html