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

Yves Savourel commented on XLIFF-43:

The issue I posted merely point out that the spec contained two examples for  its:localeFilterList in <unit>, while all the conformance text and the validation artifacts of the current draft say it's allowed only in <mrk> and <sm/>.  That is a simple editorial fix.

Now if you want to make a feature change and allow it in <unit>, you may want to make a case for it. (Maybe you did during the call).

My opinion on having ITS data categories on structural elements is as before: I'm not sure it's a good idea because it implies yet again more inheritance (the true bane of XLIFF processors). I don't think any other ITS data categories is allowed on <unit>.

I'm also not really eager to see *any* localeFilter data (structural or inline) in an XLIFF file: The core was designed to be bilingual, relying on an optional module to implement conditional targets is asking for trouble: If you create such file, most tools will not process it properly.

It is *a lot* better to create specific XLIFF document for each target. I'm surprised there is actually no text in the locale Filter section about that recommendation.

> 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: Yves Savourel
>            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]