- From: Yves Savourel <ysavourel@translate.com>
- Date: Fri, 16 Jul 2004 10:22:38 -0600
- To: <aphillips@webmethods.com>, "'Sue Ellen Wright'" <sewright@neo.rr.com>, "'Tex Texin'" <tex@xencraft.com>, <www-international@w3.org>
> 1. What is the nature of the deliverables? To put something in a > charter, we need to know exactly what the working group would deliver. I can think of one possible deliverable: a namespace for localization directives. But I'm not sure exactly where it belongs, since it seems to be between "localizability of W3C technologies" (such as XHTML or XML) and "localization technologies" (like TMX, XLIFF, etc.). [In a few words: Localization directives are information inside a document that helps the localization process, for example identifying run of text not to be translated, marking up "terms", etc. Having a common namespace for this could lead to more control by the authors/developer of the source material on how the localization is done. For example, one can imagine any authoring application using XML has repository to provide a function to markup not-translatable parts the same way you can apply a character style. And all localization tools being able to take advantage of it.] While this certainly does not replace following guidelines in creating localizable document types, it still is an important part of creating documents that are more easily localizable. So, I'm not sure where such specification should be done, but seems to be a possible deliverable for the W3C. And if the W3C would decide not to take on this task, it would also be helpful as this would make clear another group has to do it then. As far as participation, I can't be sure, but from the level of interest I'm seen for such namespace in various companies, I would guess such work would find some volonteers. -yves Yves Savourel ENLASO Corporation http://www.translate.com
Received on Friday, 16 July 2004 12:23:19 UTC