[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: subState question
Hi XLIFF TC, As a module, translation candidates support is not required. In the case where it is not used, if a target segment has been auto-translated, can subState be something like this: <segment state="translated" subState="xyz:mt" id="1"> <source>This tutorial teaches you how to create a simple "Hello, world" app.</source> <target>Este tutorial te enseña cómo crear un simple "Hola, mundo" app.</target> <segment> Basically use the values defined for match.type (http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html#candidates_type)
as subState values? I see the following processing requirement for extension mechanisms, but not sure if this is intended to apply to subState or other “sub” values:
·
A user extension, whether implemented using
<mda:metadata> or using a custom namespace, MUST NOT provide the same functionality as an existing XLIFF core or module feature, however it MAY complement an extensible XLIFF core
feature or module feature or provide a new functionality at the provided extension points. Thanks, Ryan |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]