RE: [xliff-comment] Schematron and 'canDelete' in untranslated files

["Rodolfo M. Raya" <rmraya@maxprograms.com>]

 

Iâm indeed observing a different behavior. Current XLIFF Core Schematron rules donât check segment state.

 

FWIW, Iâm using the official ISO 2016 stylesheets to test the XLIFF Schematron set, not Oxygen. Validation should not depend on a closed source commercial tool. It should be based on open code so anyone can check what is being validated.

 

Regards,

Rodolfo

--

Rodolfo M. Raya     Â rmraya@maxprograms.com

Maxprograms      https://www.maxprograms.com

 

From: David Filip <david.filip@adaptcentre.ie>
Sent: Friday, April 5, 2019 10:15 PM
To: Rodolfo Raya <rmraya@maxprograms.com>
Cc: xliff-comment@lists.oasis-open.org
Subject: Re: [xliff-comment] Schematron and 'canDelete' in untranslated files

 

Hi Rodolfo,

The intended behavior for the core Schematron rules is that editing hints such as canDelete are not evaluated in the segment state "initial", throw warnings in the states "translated" and "reviewed", and throw errors in the state "final".

If you find anything contrary to this, please let us know. This should be fixed in 2.2.

Cheers dF

 

Cheers dF

 

On Fri, Apr 5, 2019, 21:30 Rodolfo M. Raya <rmraya@maxprograms.com> wrote:

Schematron for XLIFF Core throws error when an inline element in <source> has âcanDeleteâ attribute set to ânoâ and there is no <target> (untranslated <segment>).

 

Is it correct to consider untranslated files invalid?

 

Regards,

Rodolfo

--

Rodolfo M. Raya       rmraya@maxprograms.com

Maxprograms      https://www.maxprograms.com