MHonArc v2.5.0b2 -->
















xliff message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: RE: [xliff] Proposal to allow a translator to indicate that a translation has had to be grouped across more than one trans-unit




From: "Gerard Cattin des Bois" <gcatt@windows.microsoft.com>
To: "Andrzej Zydron" <azydron@xml-intl.com>,<xliff@lists.oasis-open.org>
Date: Thu, 15 Apr 2004 13:04:50 -0700






Hello Andrzej,
We have experienced this many times. 

This is in part the reason for doing localizability validation (pseudo-localized builds and BVTs). Typically, these broken strings are logged as localizability issues, and are not passed to localizers until fixed. 

I don't believe that localization should be fixing localizability issues. They are truly core development team issues that should be resolved there. The developer needs to write localizable code, and after separating code and localizable strings, the next item of importance is to have complete sentences submitted to localization. 

My take on the proposal is that Xliff is the wrong place to fix the problem.
Cheers,
-G�rard
Families are living sanctuaries