W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2005

Minutes 2005-02-24: ITS teleconference

From: Richard Ishida <ishida@w3.org>
Date: Fri, 25 Feb 2005 16:07:07 -0000
To: <public-i18n-its@w3.org>
Message-Id: <20050225160705.D67354F08C@homer.w3.org>

MINUTES: I18N ITS WG telcon, 2005-02-24

Masaki Itagaki (Invited Expert), Andrej Zydron (Invited Expert), Tim Foster (Sun), Diane Stoick (Boeing), Richard Ishida (W3C)

Yves Savourel


Callers introduced themselves.  Two new voices this time: Diane and Masaki

Spent time helping Masaki and Diane connect via IRC and email.



[1] http://people.w3.org/rishida/localizable-dtds/#direct-no-xlate
Tim: should add content that should not be word counted and
 text that shouldn't be segmented
 eg.  content of a program listing including java source code
RI: reinforces distinction between localization directives/tag set vs. localization properties; we are focussed on tags for inclusion in the document, not localization properties
AZ: has been dealing with properties in the past
 are we wedded to DTDs?
RI: we need to address both dtd and schema developers
AZ: restricted syntax of dtds leaves less room for maneouvre
TF: our solution would be the localization properties approach
  as a translation tools writer i'd like to not manually create these
MI: is there a case where it should not be segmented but should be translated?
TF: yes, eg. embedded text
TF: we have such a tag like this
 two possible approaches: 
 1] use pre translate="no"...span translate="yes" Hello World
 2] use pre translate="somehow" and use string extractors
 we need to choose best approach
 string extractor needs information about how to extract strings, if used
Discussion: we need to constantly weigh whether putting something in the tag set would impose too great a burden on schema developers or content authors - some things might be better described using a localization properties approach. 

[2] http://people.w3.org/rishida/localizable-dtds/#emphasis
TF: wanted to be sure that we aren't talking about providing tags like 'sarcasm', 'irony', etc.
Group agrees that this sort of stuff would likely be in guidelines
RI: we may be asked to provide suggestions of types of tags that dtd designers could use (in our guidelines)
TF: could be a battle to get people to stick to them
 could find that people are using tags for things that were'nt intended, because there is not enough information about how to use XLIFF, say, 
 we should learn from that and ensure that we clearly document the intended use of tags
AZ: documentation for XLIFF is in preparation

If you disagree with something in the minutes, or wish to add something, please write to the list using reply and the same subject.

If you want to create a discussion thread from an item in the minutes, please USE A NEW SUBJECT LINE and do not simply reply to the minutes. This is to help people locate minutes and follow threads more easily.

Richard Ishida

contact info:

W3C Internationalization:

Publication blog:
Received on Friday, 25 February 2005 16:07:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:04 UTC