Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

[FEATURE] #406

Open
yoazerty opened this issue Aug 21, 2020 · 1 comment
Open

[FEATURE] #406

yoazerty opened this issue Aug 21, 2020 · 1 comment
Labels

Comments

@yoazerty
Copy link

Thank you for this great job!
Would it be a big effort to support xlf / xliff files?

Regards

@gilmarsquinelato
Copy link
Owner

Hello @yoazerty,

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants