OASIS XML Localisation Interchange File Format (XLIFF) TC

Hi,

as some values/constraints/PRs cannot be validated using standardized
validation artifacts (e.g. value of srcLagn/trgLang) and custom code is
required, would it be possible to explicitly state it in the specs for each
such case?

Thanks,
Jan

Thanks for this, Jano,

Please follow the disposal of this comment here
https://issues.oasis-open.org/browse/XLIFF-56

If you want to follow up, please keep to this thread
http://markmail.org/thread/hnc4g2akchkt2cbz

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 Tue, May 16, 2017 at 1:32 PM, Ján Husarcík <jan.husarcik@gmail.com>
wrote:

> Hi,
>
> as some values/constraints/PRs cannot be validated using standardized
> validation artifacts (e.g. value of srcLagn/trgLang) and custom code is
> required, would it be possible to explicitly state it in the specs for each
> such case?
>
> Thanks,
> Jan
>

Thanks for this, Jano, Please follow the disposal of this comment here https://issues.oasis-open.org/browse/XLIFF-56 If you want to follow up, please keep to this thread http://markmail.org/thread/hnc4g2akchkt2cbz 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 Tue, May 16, 2017 at 1:32 PM, Ján Husarcík < jan.husarcik@gmail.com > wrote: Hi, as some values/constraints/PRs cannot be validated using standardized validation artifacts (e.g. value of srcLagn/trgLang) and custom code is required, would it be possible to explicitly state it in the specs for each such case? Thanks, Jan