You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
Thank you!
So, taking a look at the file, it's basically an XML file.
The problem here is:
Its structure can contain multiple tags, so it would conflict with the internal app structure
It's a flat structure, and the app supports multiple nesting levels, then if the user accidentally adds a nested translation, it would result in a broken file
At the moment the app doesn't make any difference nor custom behaviour based on file formats.
It has some file adapters, that reads and writes to the correct format, and do the adaptation to the internal app format.
One another thing is that I don't know how many users actively use .xlf as translation files, so I don't know if worth it the effort to do that.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thank you for this great job!
Would it be a big effort to support xlf / xliff files?
Regards
The text was updated successfully, but these errors were encountered: