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-58) Error in ITS rules in its.sch

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

Felix Sasaki commented on XLIFF-58:

I added testing for the ITS rules to the test suite, see

its-rules-to-xslt-patterns.xsl takes its.sch as an input and generates an XSLT its-rules-generated-transformation.xsl

its-rules-generated-transformation.xsl is applied to withNotes_complex_for_ITS_Processors.xlf . The result is stored in withNotes_complex_for_ITS_Processors-its-rules-check.html

It seems that all rule are valid and match the correct nodes. However, the checking was only for the rules in withNotes_complex_for_ITS_Processors.xlf . If people have the bandwidth to create more test files, they can use the  its-rules-generated-transformation.xsl to do more checking. If there are changes to its.sch, then  its-rules-generated-transformation.xsl has to be regenerated.

> Error in ITS rules in its.sch
> -----------------------------
>                 Key: XLIFF-58
>                 URL: https://issues.oasis-open.org/browse/XLIFF-58
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Bug
>          Components: ITS Module
>    Affects Versions: 2.1_csprd04
>         Environment: http://markmail.org/message/gpylepw5b6sd3pbg?
>            Reporter: Yves Savourel
>            Assignee: Felix Sasaki
>              Labels: CFD, editorial
>             Fix For: 2.1_cs01
> Are we sure the ITS rules in its.sch (especially the locNoteRule ones) are correct?
> I’m getting syntax errors like “A location step was expected following the '/' or '//' token.” When trying to process them.
> I’m certainly no XPath expert, but the “//::” parts look odd.
> For example a rule like:
> //xlf:file//::xlf:source[ancestor::xlf:file[not(@appliesTo)]/xlf:notes/xlf:note[@priority=1]] | //xlf:file[not(@appliesTo)]//::xlf:target[ancestor::xlf:file[not(@appliesTo)]/xlf:notes/xlf:note[@priority=1]]

This message was sent by Atlassian JIRA

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