Internationalization Working Group Teleconference

16 Jan 2013


See also: IRC log


Addison, Richard, Emile, Koji, Felix, Norbert, Jan, Mati, David
Addison Phillips
Addison Phillips


Agenda and Minutes

Action Items

close ACTION-167

<trackbot> Closed ACTION-167 Review john daggett/david baron's case tests and suggest any changes/additions needed.

<r12a> http://www.w3.org/International/track/actions/open

close ACTION-171

<trackbot> Closed ACTION-171 forward comments on case sensitivity to CSS.

<David> I saw the CSS case (in)sensitivity discussions, but had little to add.

Info Share

<scribe> chair: welcomes two new members

richard: MLW workshop in rome in march
... you should register soon, as seats are filling

<r12a> http://www.multilingualweb.eu/rome

What Time Is This Meeting At?

> There's a zakim crush at 16:00 due to large telecons starting up. If we want > to spill over, even a little, past the hour allocated, we may need to move the > start of the telecon forward, since we will be unpopular if we go past the top > of the hour.

<Norbert> http://www.doodle.com/848xxp36vvhtd32f#table

propose thursdays

Pending Reviews


ITS v2 review




Norbert: translate attribute
... didn't see anything about other items that need localization
... e.g. a color or an image that need localizatoin but aren't *translated*
... is there an attribute that allows to make localizable?

<fsasaki> http://www.w3.org/TR/2012/WD-its20-20121206/#LocaleFilter

felix: there is a locale filter that could select items for localization

norbert: need a way to markup and manage items that need to be localized, but not for translators to make different words

<fsasaki> http://www.w3.org/TR/2012/WD-its20-20121206/#externalresource

felix: would be useful to have examples

Norbert: bidi
... active discussion about isolates
... and ITS has directionality
... depend on HTML5?

<fsasaki> http://tinyurl.com/its20-testsuite-dashboard

felix: on direction, our test suite dashboard
... lists what's been done
... first table has row for dir
... ENLASO and U.Limerick working on it
... don't render, but do pass
... worry about ruby
... no implementations working on

r12a: concern why direction section is non-normative, should it just be in BP doc?
... ruby continues to change in HTML5
... understood that those sections there
... possible to edit before release
... to reflect latest thinking
... can change because non-normative
... v1 of ITS did implement

norbert: what's in ITS 2 doesn't match ITS 1 or what will be in HTML5
... needs extension spec?

direction: keep, note that developments are coming

ruby: take out as unimplemented

direction needs to be normative if present

r12a: largest issue
... discussion "what about dfn and <term>"?
... stuff about relationship of ITS to HTML5 goes to BP doc?
... unclear on objectives viz HTML5
... move unclear stuff to BP document was my understanding
... but document objectives suggest that ITS would document how ITS relates to HTML5

felix: aim is to show how ITS native metadata in HTML5
... some exceptions
... @translate attribute maps directly to/from HTML5
... also @lang
... those exceptions have clear mapping
... point about stuff like dfn or term
... HTML can use for different purposes than ITS uses for
... HTML <dt> was focued on
... not a straight-forward mapping

<fsasaki> http://www.w3.org/TR/xml-i18n-bp/#relating-its-plus-xhtml

felix: hard to justify hardcoding a rule such as the dt rule

Norbert: should be note on "similar" elements to describe potential mappings

r12a: if it's only situations where normative relationships can be drawn between HTML5 constructs and ITS constructs, then the ITS spec needs to make point much more clearly


Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2013-01-16 17:23:42 $