See also: IRC log
<scribe> Scribe: Addison Phillips
<scribe> ScribeNick: aphillip
<David> I didn't see an agenda
<David> should we add rescheduling for DST soon?
item: the language tags
... DST scheduling
HTML encoding detection
is anyone reading html5?
Richard: respond on our behalf to CSS on ruby issue
check back in a few weeks
addison: set up document edit transition with dan for ws-i18n
dan has the document, but his editor doesn't work... so getting xmlspy
richard: publish i18n-guide-frameword as (retired, obsolete) WD
told the change is made but not appearing yet... will keep tracking
will ping Ian again
addison: to write a response proposing new text for html5 immediately following call for forwarding today
agendum: bidi techniques pub
all: review HTML5 (rolling action item to be reviewed weekly)
idna folks just changed their charter
(ping mark for some update??)
richard: basically... I'd like to
... any objections?
<scribe> ACTION: Richard: publish bidi techniquest document [recorded in http://www.w3.org/2009/09/02-core-minutes.html#action01]
<scribe> ACTION: David: coordinate getting new dst scheduling [recorded in http://www.w3.org/2009/09/02-core-minutes.html#action02]
richard: looking for comments
richard: main change is in extended language subtag section
Prefix: ar Macrolanguage: ar
appears on one line instead of two
addison: written chinese is more complex than that
<andrewc> it depends on how exact you neeed to be with your langauge tagging
richard: mark mentioned
... i had written:
<r12a> As RFC 4646 co-author, Addison Phillips, writes, "For virtually any content that does not use a script tag today, it remains the best practice not to use one in the future".
<r12a> mark writes:
<r12a> I disagree with that. The better advice is
<r12a> You should not use a script code if the predominant usage of the language is with a single script, and you don't need a contrast to remove ambiguity.
<r12a> For example, either Latin or Cyrllic are appropriate for use with uz, because of 'a'. As another example, where audio and written content need to be distinguished, one can use the "en-Latn" for written content and "en-Zxxx" for audio content.
richard: and mark wrote:
<YvesS> sorry, could not make it before.
<andrewc> its a case by case basis.
<andrewc> maybe the rule of thumb is use the minimal langauge tag you need to provide the level of identification oyu need?
<andrewc> which seems ot cover all cases
Ultimately, it would probably be useful for the I18N WG to provide a reference about legacy encodings, superset encodings, and the famous "willful violation of CharMod" in HTML5, published as a WG Note.
<andrewc> they use legacy in multiple ways
<andrewc> slowly working through html5
<andrewc> not yet, but still need to go through a lot more of html5 first
<andrewc> maybe a start would be to write a HTML5 internationalisation cheatsheet based on our existing techniques documents, faqs, etc
use public list to share comments as you find them
<andrewc> although html5 like css3 is likely to be an ingremental implementation
<andrewc> at soem point the horse has bolted, but at what point?
<andrewc> esp since firefox and opera are starting to implement parts of it already ;)
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) Found Scribe: Addison Phillips Found ScribeNick: aphillip Default Present: David, addison, Richard, andrewc, YvesS Present: David addison Richard andrewc YvesS Regrets: DanC Got date from IRC log name: 02 Sep 2009 Guessing minutes URL: http://www.w3.org/2009/09/02-core-minutes.html People with action items: david richard[End of scribe.perl diagnostic output]