Using Xliff notes instead of context group
Activity
Dragos Varovici 1 June 2018 at 14:50
Do not need to edit comments in Zanata. Only to pass them to Zanata.
Sean Flanigan 1 June 2018 at 01:27
Hi
Yes, unfortunately Zanata's XLIFF support is quite ad hoc, and essentially specific to the XLIFF subset used by the spacewalk-frontend project (apparently XLIFF 1.1).
SimpleComment was somewhere to store context-group in Zanata, rather than the other way around. Note that Zanata currently has no UI for editing or creating SimpleComments which are attached to source TextFlows.
We implemented that XLIFF support before we added integration with the Okapi project, which provides a much better solution for things like this.
Adding XLIFF 1.2 support via Okapi sounds like a good idea. Our existing integrations all extend org.zanata.adapter.OkapiFilterAdapter if you want to take a look.
Dragos Varovici 21 May 2018 at 23:22
https://serge.io/ - Free, Open-Source Solution for Continuous Localization by Evernote
Dragos Varovici 21 May 2018 at 23:21
http://okapiframework.org/ - The Okapi Framework is a cross-platform and free open-source set of components and applications that offer extensive support for localizing and translating documentation and software.
Details
Details
Assignee
Reporter
Tested Version/s
Components
Priority
unspecified
At this moment Zanata makes use of context group in order to store the comment (SimpleComment). However this is different from how other translation software providers (open source: Mojito, Pootle) or commercial (Crowdin, Transifex, PhraseApp) are storing the comment (the xliff note). This also prevents Serge.io from using xliff as translation interchange fomat.
My approach to solve this issue would be to implement a new format called Xliff 1.2 (Xliff 2.0 is not backwards compatible) and use okapi framework as the parsing framework instead of it's own parsing. This format would store the comment in the xliff note.