[OASIS Issue Tracker] (XLIFF-43) Inconsistent provisions for Locale Filter at structural elements

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

    [ https://issues.oasis-open.org/browse/XLIFF-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65658#comment-65658 ] 

David Filip commented on XLIFF-43:
----------------------------------

I pondered Yves argument and now agree that it's a bad idea to give ITS Module capable XLIFF agents the power to manipulate the immutable XLIFF core structure. So we should be fine with only inline presence of locale metadata if the datacat is not fully consumed by extraction.
I will fix the example that uses this datacat on structural and provide reference to the non-representation as the preferable handling. Hopefully, I'll manage to print by tomorrow's meeting..

> Inconsistent provisions for Locale Filter at structural elements
> ----------------------------------------------------------------
>
>                 Key: XLIFF-43
>                 URL: https://issues.oasis-open.org/browse/XLIFF-43
>             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/qbz32fdgklo4g4s7
>            Reporter: Yves Savourel
>            Assignee: David Filip
>            Priority: Critical
>              Labels: Proposed, editorial, request_tc_discussion, work_required
>             Fix For: 2.1_csprd03
>
>
> In section "5.9.6.3 Locale Filter":
> We say:
> [[
> For both structural and inline elements, use <mrk> or an <sm/> / <em/> pair with
> the following attributes: its:localeFilterList and
> its:localeFilterType.
> ]]
> And immediately below, the section "5.9.6.3.1 Structural Elements" goes on
> showing two examples, both where the its:localeFilterList
> is used on <unit> rather than <mrk> or <sm/>.
> Since the definition of its:localeFilterList does not mention <unit> as an
> element where it is used, I assume the examples in
> section 5.9.6.3.1 need to be fixed.



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