Open nijel opened 8 years ago
+1
Just for the sake of documentation, this is the status from translate-toolkit side: https://github.com/translate/translate/issues/3369
The issue has been standing at translate-toolkit for over 2 years now. Could a layer be implemented on Weblate's side instead?
It doesn't matter where the layer would be implemented, but somebody has to implement it :-). I prefer pushing things to translate-toolkit, pretty much all format improvements went there so far (side effect of that is that I'm among most active contributors to translate-toolkit these days). I see no reason to do xliff2 outside.
are there any updates?
We really should add support for Xliff2. The problem is that the format is not backwards compatible with Xliff and is not supported by translate-toolkit right now.
This should be implemented in the translate-toolkit, see https://github.com/translate/translate/issues/3369