W3C home > Mailing lists > Public > public-i18n-its-ig@w3.org > July 2008

Re: ITS to XLIFF conversion and roundtripping

From: Lieske, Christian <christian.lieske@sap.com>
Date: Wed, 30 Jul 2008 13:00:52 +0200
Message-ID: <79B53B59C99E7743A0F9DE98407704F1ED8244@dewdfe1g.wdf.sap.corp>
To: <public-i18n-its-ig@w3.org>

Hi Felix,

You wrote ..

===
Hi all,

I have worked on ITS to XLIFF conversion and roundtripping, see

http://www.w3.org/International/its/wiki/ITS_Translate_Decorator#XLIFF_generation_and_roundtripping

There is still a lot to do, but this might be enough so that people can
play with it. I'm looking forward esp. towards feedback about the XLIFF
format.
===

This is great. From my understanding it is an important additional step towards supporting ITS adoption.

Support for adoption from my point-of-view can amongst others be provided by addressing and exemplifying
two facets of working with the Internationalization Tag Set (ITS):

1.	Explain how to use ITS with an existing format 

Examples: 

	a. specify mappings in a formal way or to actually operationalize the mapping for conversion between formats (e.g. use "its:translate" to indicate which elements need to appear in an XML document which contains nothing but translatable content) 

	b. show how ITS can serve as a facilitator to bridge between a native format and XLIFF as the general purpose localization-related interchange format

2.	Give hints on how to build ITS processors

Example:

	Show (by means of a sample application) how to compute the ITS information that pertains to a node in an XML document (requires attention for support for selection mechanism, defaults / inheritance / overriding characteristics, and precedence). 

I wonder if it would make sense to address these two facets loosely coupled. With regard to the page/information you have put
together, this could boil down to tackling the decorator (which is related to 2. above) as one activity, and tackling the bridge
from the decorated XML to XLIFF (which is related to 1. above) as a separate activity. This separation of concerns could help with
a division of labour. It would for example enable an XLIFF expert to refine the sample transformation you have crafted.

Cheers,
Christian

===

Christian Lieske
Knowledge Architect
SAP Language Services (SLS)
SAP Globalization Services
SAP AG
Raiffeisenring 44
D-68789 St. Leon-Rot
Germany
T +49 (62 27) 7 - 6 13 03
F +49 (62 27) 7 - 2 54 18
mail to:christian.lieske@sap.com
www.sap.com 
Sitz der Gesellschaft/Registered Office: Walldorf, Germany 
Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/Co-CEO), Léo Apotheker
(Sprecher/Co-CEO), Werner Brandt, Erwin Gunst, Claus Heinrich, Bill McDermott,
Gerhard Oswald, John Schwarz, Jim Hagemann Snabe, Peter Zencke
Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner 
Registergericht/Commercial Register Mannheim No HRB 350269 
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt.
Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. 
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
Received on Wednesday, 30 July 2008 11:03:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:33:00 GMT