[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: JLIFF files, fragment, groups, units, subunits
All I’ve been looking at this a little this morning and the ability to wrap the choice of ‘files’, ‘fragment’, ‘groups’, ‘units’ and ‘subunits’ introduces
a lot of complexity into code both during serialization/deserialization and also utility methods such as something which would GetAllSegments(). From what I can see the anonymous wrapper object (named ‘jliff’ in my library) would need a ‘content’ or ‘body’ property which stores instances of
an interface which ‘files’, ‘units’, ‘subunits’, etc. would conform to. This is fine but I think then each of these possible contents would need a ‘type’ property so that my serialization library can figure out what concrete type to instantiate during deserialization. I’ll play with it a little more to see if I can refine it a bit. Phil
From: Robert van Engelen [mailto:engelen@genivia.com]
Hi, The JLIFF schema 0.9.4 is updated on GitHub. Added are the `srcDir` and `trgDir` properties to the JSON JLIFF “wrapper” object, each with `ltr`, `rtl`, or `auto` enumerated string values. I’ve restructured the JLIFF object schema by providing a choice of `files`, `fragment`, `groups`, `units`, and `subunits` properties. I’ve tested the changes with schema validators and examples. These (unofficial) tests passed. See the modified `jliff` object type in the schema somewhere defined at the top. - Robert |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]