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-35) Issues related to ITS Localization Note

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

Felix Sasaki commented on XLIFF-35:

- Position of section: I don’t know what the proper section would be. This needs further discussion.

- Warning for for <sm> and <em>: I agree that there should be no warning in this section, but rather one for all data categories.

- Scope problem of XLIFF / missing semantic equivalence:  one could express the requirement via rules that express the two cases of appliesTo. But these rules would need to cover the various position „notes“ and „note“ can appear in. Not sure if this is feasible.

- Current ITS rule in
http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd02/schemas/its.sch : agree that this rule is not adequate. 

General: The missing semantic equivalence makes it hard to make the ITS Localization Note to XLIFF. One solution may be to say: this is not mapped to XLIFF but there are only best practices and examples for extracting notes. 

> Issues related to ITS Localization Note
> ---------------------------------------
>                 Key: XLIFF-35
>                 URL: https://issues.oasis-open.org/browse/XLIFF-35
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Improvement
>          Components: ITS Module, validation artifacts
>    Affects Versions: 2.1_csprd02
>         Environment: http://markmail.org/thread/tjnzclkiomfcers2
>            Reporter: Yves Savourel
>            Assignee: Felix Sasaki
>              Labels: AdoptionBlocker, request_tc_discussion, work_required
>             Fix For: 2.1_csprd03
> The ITS Localization Note data category in section: Localization Note.
> There are various issues IMO with it:
> -- Wrong category?
> That is in the set of data categories "that have a partial overlap with XLIFF
> features", but there is no ITSM elements or attribute
> defined. So what is the 'partial overlap'? If that data category can be mapped
> using only ITS rules and XLIFF elements/attributes it
> should be in the category " ITS data categories available through XLIFF Core and
> other Modules". If that is not the case then it
> should be in the category "ITS data categories not represented in XLIFF"
> -- Warning for for <sm>:
> The second paragraph of the warning the the section says:
> "While XLIFF Core <note> elements apply to the whole content of the structural
> element where it was placed in the business sense, it
> doesn't technically inherit in the XML sense. The scopes of the Comment
> Annotation mechanism will differ where the unextended ITS
> Processors cannot identify pseudo-spans formed by <sm/> / <em/> pairs, the scope
> will be the same on the well-formed <mrk> spans.
> The content and type of the Localization Note will be always mapped properly."
> Why this specific warning. It's no different than for all ITS data categories.
> But the other data categories don't have a specific
> warning.
> The term "unextended ITS processor" is very confusing: We should not assume
> anything about extension of ITS processors.
> The term "in the business sense" is also very weird.
> IMO: There should be one general note about the issue of the <sm> scope that
> explains the problem and states the limitation of the
> ITS processor with that element (with any data category).
> -- The scope problem of XLIFF <note>:
> The scope <note> and the one for ITS Localization Note are different. In XLIFF
> <note> applies to either to source or target (and--I
> assume--to everything if appliesTo is not defined (the default)).
> For IT'S THE note applies to the textual content of the element, including child
> elements, but excluding attributes.
> So essentially kind of the same as when appliesTo is not defined.
> Unless there is a way to have a ITS rules that manage to handle the
> appliesTo='source' and appliesTo='target' we don't have a
> semantics equivalence.
> -- ITS rule in
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd02/schemas/its.sch
> Currently we have:
> <its:locNoteRule selector="//xlf:note" localizationNotePointer="self::*"
> locNoteType="description"/>
> But that doesn't take XLIFF priority into account, nor appliesTo.

This message was sent by Atlassian JIRA

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