OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

David Filip commented on XLIFF-43:

As we didn't get to this issue in the meeting today, I am making this CFD
Please review
Processing Requirements and examples in the editors' draft:

The currently implemented solution will be considered approved by consensus of the TC if no material objection raised by Sat 25th March 2017, 23:59 PDT.

> 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: CFD, Proposed, material
>             Fix For: 2.1_csprd03
> In section " 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 " 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 need to be fixed.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]