See also: IRC log
<r12a> hi addison
<r12a> trackbot can help with meeting setup
okay... shoot :-)
<r12a> by starting zakim and rrsagent automatically
<scribe> Scribe: Addison Phillips
<scribe> ScribeNick: aphillip
<r12a> see Starting a telecon at http://www.w3.org/2005/06/tracker/irc
<r12a> it should be a big time saver :-)
Ask the Korean HTML5 Interest Group what should happen if "word-break: keep-all" is used with "word-wrap: break-all"
Change the language tags article to say that now there is an extension defined, and describe it briefly
set due date in Feburary
Check on HTML5 language tag validator and send any comments
Convey to Unicode desire to keep UTR#20 as a joint publication with identical versions
Nudge everyone to ensure everyone review non-translate email by next week
Update review radar and ping www-international seeking comments
<kennyluck> close ACTION-6
<trackbot> ACTION-6 Convey to Unicode desire to keep UTR#20 as a joint publication with identical versions closed
richard: report available........
<r12a> ACTION-4 due Feb 2 2011
<trackbot> ACTION-4 Change the language tags article to say that now there is an extension defined, and describe it briefly due date now Feb 2 2011
richard: the workshop report on multilingual web workshop
language tag references. would prefer text on BCP 47
richard proposed: "A user agent displaying metadata is expected to choose a preferred language/locale to display from among those available, following matching algorithms in BCP 47 (currently RFC 4647)."
<kennyluck> aphillip: It's not the metadata of the font but rather the localized text for the license.
scribe: such as the Lookup algorithmn in BCP 47
norbert: might want to go beyond lookup..
<r12a> following a matching algorithm such as lookup in BCP 47
[b] Description of text elements
[c] Use of attributes for human readable text
we'd prefer them to use elements for localizable text instead of attributes (for dir and other markup)
[d] Localization mechanism too restricted
scribe: although I'd say "although you allow non-ASCII..."
[e] Paragraphs and inline content
provide paragraph and span elements in description and other textual elements
aharon: should bdi also be allowed?
<aharon> ok, no bdi
[f] Direction attributes needed
[g] OpenType feature preservation
richard will raise issues this evening
scribe: if you have a description
... can contain multiple "text" elements
... each of which has a separate @lang attribute
richard: first, why not
... however, I think this is similar to widget spec
... better not to use xml:lang in those cases
<aharon> I have a tight time limit. I will need to get off in 8 minutes.
<scribe> chair: any objections?
WG endorses comments
aharon: sent some messages to WG list
aharon: saying that good news is
that most proposals (nearly all) were accepted
... some with modifications
... so going well
... have online document that summarizes proposals
... and status
... next step is to close the bugs that are satisfied
... or don't need further work
... if there are bugs that we are unsatisfied with
... then we need to re-raise
<scribe> ACTION: aharon to publish list of bugs with status closed and then a separate list with bugs that there is potential working group objection for review at next meeting [recorded in http://www.w3.org/2010/12/15-i18n-minutes.html#action01]
<trackbot> Created ACTION-9 - Publish list of bugs with status closed and then a separate list with bugs that there is potential working group objection for review at next meeting [on Aharon Lanin - due 2010-12-22].
richard: put info in google doc
into our Note document?
... and then "this is what happened"
aharon: agree, but want to wait
... may need a note to browser makers about things that couldn't go into HTML or CSS but which they should be aware of
... canoical example is scrollbar location
... another document or mod to existing is recommendations for how to do bidi using the new markup
richard: put into existing tutorial?
addison: also nice to have a good short summary published
richard: this is a potential difference between xml:lang and "here is some localized content"
lang then xs:language
<text lang="es-419"><p xml:lang="en">...</p><p>...</p></text>
<text market="419" lang="es-419">
richard: on holiday through 10
... get agenda out early
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/7 january/10 january/ Found Scribe: Addison Phillips Found ScribeNick: aphillip Default Present: [Microsoft], gwyneth, +1.617.466.aaaa, kennyluck, freedom, Richard, +922.214.171.124aabb, matial, aphillip, +972.5.424.5aacc, aharon, +44.141.888.aadd, David, Norbert Present: [Microsoft] gwyneth +1.617.466.aaaa kennyluck freedom Richard +9126.96.36.199aabb matial aphillip +972.5.424.5aacc aharon +44.141.888.aadd David Norbert Agenda: http://lists.w3.org/Archives/Member/member-i18n-core/2010Dec/0010.html Got date from IRC log name: 15 Dec 2010 Guessing minutes URL: http://www.w3.org/2010/12/15-i18n-minutes.html People with action items: aharon[End of scribe.perl diagnostic output]