xliff-comment message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Undefined default for state attribute
- From: "Josep Condal" <pcondal@apsic.com>
- To: <xliff-comment@lists.oasis-open.org>
- Date: Tue, 17 May 2011 12:08:01 +0200
Dear
TC,
We find ambiguous
that in version 1.2 the state attribute has an undefined default value. This
renders to fully compliant XLIFF documents where it is not possible to tell if
the target text is or is not the translation of the source text, preventing
interoperability and reliability of key QA functions.
For example, with
the current specification, a tool maker could have a valid XLIFF file
where each source value has a target value, but for some cases, the target text
is the real translation and in other cases, it is merely the source text that
has been primed there.
We propose that the
XLIFF specification does not allow ambiguity in attributes that do not need it,
to avoid that such ambiguity may hinder or effectively prevent interoperability.
In most cases, defining a default value should be enough to prevent
ambiguity.
Regards,
Josep.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]