[OASIS Issue Tracker] (XLIFF-26) Example 22. Populating XLIFF Core targets with raw MT along with ITS MT Confidence metadata:

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/XLIFF-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Filip updated XLIFF-26:
-----------------------------

    Fix Version/s: 2.1_csprd03
                       (was: 2.1_cs01)

> Example 22. Populating XLIFF Core targets with raw MT along with ITS MT Confidence metadata:
> --------------------------------------------------------------------------------------------
>
>                 Key: XLIFF-26
>                 URL: https://issues.oasis-open.org/browse/XLIFF-26
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Bug
>          Components: ITS Module
>    Affects Versions: 2.1_csprd02
>         Environment: http://markmail.org/thread/t7kt53dq5ecnujl2
>            Reporter: Yves Savourel
>            Assignee: David Filip
>            Priority: Minor
>              Labels: Approved, editorial, work_required
>             Fix For: 2.1_csprd03
>
>
> Example 22. Populating XLIFF Core targets with raw MT along with ITS MT
> Confidence metadata:
> -- The text above the examples should not be bold (Original:, Extracted text...,
> etc.)
> -- Also:
> <source xml:lang="EN">
>       Some human authored text for translation.
> </source>
> Should be:
> <source xml:lang="EN">Some human authored text for translation.</source>
> Otherwise the text doesn't match exactly the text in match.
> -- Also: there is an extra </mtc:match> after <mtc:matches>
> -- Also: in <mtc:match ref="#m1" matchQuality="67.8"... the ref points to
> no-existing span of text. It should be ref="#t=m1" to
> point to a span in the <target>.
> I WOULD RECOMMEND TO VALIDATE ALL EXAMPLES in the ITS and CTR modules: they do
> not seem to have been checked with a validator.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)