Exported .ts files are corrupted (Missing Context)

I'm experiencing the same thing, it makes the .ts support mostly useless (people can translate, but translations are unusable). Is this a configuration problem or a zanata bug?

translation type always remains in type "unfinished"

This was fixed in db3327e5c915b3555604175cb029fa96ff1e199f (https://github.com/zanata/zanata-platform/pull/834, master) but not yet released.

missing context -> that corrupts the .ts file

This is a bug in Zanata, on a missing writer.handleEvent(event) in the TSAdapter.java.

wrong setting of "language" ->always "en_US"

This seems to be the more difficult problem to solve, as the locale property provided by TSFilter is read-only. I'll investigate this further.

Thanks for the bug report, and apologies for the inconvenience this has caused.

thanks for the rapid reaction, do you have an ETA on 4.5.0?

we're tagged a final for 4.5, and are heading into deployment stages, so if all goes well a "personally pessimistic ETA" would be two weeks. This will contain the fix for the missing contexts.

The "unfinished" issue is located in master, which will be 4.6 and we don't have a definite release date for that one yet. The locale issue is still being worked on - the Okapi filter property seems to be read-only and I have a somewhat "unpleasant" workaround that will need some tightening.

I deployed this and I can confirm this fixes the context problem. Thanks for the quick release!