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: RE: [xliff] ITS rules syntax


I’ve started to look at why our okapi ITS processor was getting a null pointer.

It looks like it’s because the rules are have an attribute localizationNotePointer instead of locNotePointer.

So one more typo to correct.

 

I’m not sure the expressions work though: I get no error, but no notes associated with nodes either (so far).

 

Yves Savourel
Localization Solutions Architect
| t: 303.951.4523 | f: 303.516.1701 | ENLASO®

 

From: David Filip [mailto:david.filip@adaptcentre.ie]
Sent: Wednesday, June 21, 2017 6:43 PM
To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF Main List <xliff@lists.oasis-open.org>
Subject: Re: [xliff] ITS rules syntax

 

Yves, Soroush, Felix, all

 

Are the rules working now? Was it an easy syntax fix attributable to a typo or export error, but no actual ambiguity as to where on the XLIFF tree the rules apply?

 

Please let us know, it seems to me that the cs01 fate hinges on the answers to the above questions..

 

Cheers

dF 


Dr. David Filip

===========

OASIS XLIFF OMOS TC Chair

OASIS XLIFF TC Secretary, Editor, Liaison Officer

Spokes Research Fellow

ADAPT Centre

KDEG, Trinity College Dublin

Mobile: +420-777-218-122

 

 

On Mon, Jun 19, 2017 at 12:07 AM, Yves Savourel <ysavourel@enlaso.com> wrote:

Thanks Soroush.

 

I get some null pointer now, but that may be a bug in our ITS engine implementation.

Somehow the selector return null. I’ll have to go debug that…

 

-ys

 

From: Soroush.Saadatfar [mailto:Soroush.Saadatfar@ul.ie]
Sent: Sunday, June 18, 2017 4:02 PM


To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF Main List <xliff@lists.oasis-open.org>
Subject: Re: [xliff] ITS rules syntax

 

Dear Yves,

 

I believe it was supposed to be 

 

//xlf:file//xlf:source…

//xlf:file[not(@appliesTo)]//xlf:target...

 

to select all sources and targets of a file respectively.

 

Soroush. 

 

 

On Jun 18, 2017, at 5:10 PM, Yves Savourel <ysavourel@enlaso.com> wrote:

 

Thanks Soroush & Felix.

 

Did you really mean “//:” by “/”? (seems to get errors too)

Or “//::” by “/” (seems to be pass, syntactically).

 

Thanks

-yves

 

From: Felix Sasaki [mailto:felix@sasakiatcf.com] 
Sent: Sunday, June 18, 2017 1:33 PM
To: Yves Savourel <ysavourel@enlaso.com>
Cc: XLIFF Main List <xliff@lists.oasis-open.org>
Subject: Re: [xliff] ITS rules syntax

 

Hi Yves, all,

 

you are right, this is not the correct syntax, probably due to export from Oxygen editor? Anyway replacing //: by / should help.

 

- Felix

 

2017-06-18 18:42 GMT+02:00 Yves Savourel <ysavourel@enlaso.com>:

Hi all,

 

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]]

 

Does not pass any online XPath evaluators/validators I’ve tried.

 

Thoughts?

-yves

 

 



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