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=65448#comment-65448 ] 

David Filip commented on XLIFF-43:

Couldn't reach consensus in the meeting of 7th March as Yves had to step out..
@Yves, please explain why ITS Locale filter attributes shouldn't be allowed on XLIFF structural.
Otherwise I'd suggest to change the spec to allow ITS Locale filter attributes on structural elements and keep the example

> 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: Ryan King
>            Priority: Critical
>              Labels: material, request_tc_discussion, work_required
>             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]