Re: [xliff-comment] XLIFF 2.1 csprd01: Editing hints — validation based on segment state

[David Filip <david.filip@adaptcentre.ie>]

Thanks, Jano,

please follow the disposition here:

https://issues.oasis-open.org/browse/XLIFF-13

We will strive to resolve/apply resolution by early Dec

Any further comments please post in this thread

Cheers and thanks

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 Wed, Nov 16, 2016 at 2:46 PM, Ján Husarčík <jan.husarcik@gmail.com> wrote:

Hello,

in relation to https://issues.oasis-open.org/browse/XLIFF-10 and https://lists.oasis-open.org/archives/xliff-comment/201611/msg00003.html could you please consider different type of validation of editing hints based on segment state?

- initial state, no target present: no validation
- translated /reviewed: report warning

- final state: report error

In case you decide to accept the suggestion, could you please update Processing Requirements in
http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#editinghints and reference them (at least) in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#state?

Thanks,

Jan