Hi all, The Okapi prototype for JLIFF now implements an initial output for the Translation Candidates and the Validation module. There is a couple of interesting twists for that last module: - Rules are inherited and additive: If we have a rule A declared in the <file> and a rule B declared in a child <unit>, both rules apply to the unit. I assumed that the JLIFF output for the unit lists only the rules declared in the unit. Not sure if it’s the right thing to do. - There is a set of attributes in XLIFF that are mutually exclusive and determine the type of rule. The prototype implement them as a single type field and also output them in JLIFF as a single field. Any thoughts on this? The online XLIFF->JLIFF conversion utility is here:
http://okapi-lynx.appspot.com/jliff The latest build of the toolkit is here:
http://okapiframework.org/snapshots/okapi-xliffLib_JLIFF_1.1.6-SNAPSHOT.zip Note that working on JLIFF allowed to catch a few bugs and to make a few improvements in the core library. Those updates are in both the “dev” branch (main branch) and the “jliff” branch (and actually also in the “v21” branch that carries the XLIFF 2.1 work). Cheers, -yves