OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-omos message

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

Subject: Content of source/target

Hi all,


Looking at https://github.com/oasis-tcs/xliff-omos-jliff/blob/master/JLIFF-schema-draft/jliff-example3-0.9.3.json


We have:


"source": [ { "text": "Quetzal" } ]


But shouldn’t that be the content set as a separate object in “source”?

Something like:


"source": {

  "cnt": [


      "text": "Quetzal"





The reason being that both source and target can have an xml:lang and/or an xml:space field in addition to their content.

Even if we decide that the xml:space field applies always to both and could be set on the parent sub-unit, we cannot do this for xml:lang, which is mostly set with different values. Or we would have to carry two sub-unit-level fields instead (e.g. srcLang and trgLang), which may be better.

But even in that case, target has also an order field in addition to its content.

I suppose that field could be also carried at the sub-unit level.





Yves Savourel
Localization Solutions Architect | ENLASO®
4888 Pearl East Circle | Suite 300E | Boulder | Colorado 80301
303.945.3759 | f: 303.516.1701
An ISO 9001:2015 certified company


Confidentiality Notice
The information in this transmittal may be privileged and confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this transmittal, in any form, is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal.


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