Add "attranslate" to "Localization" - Improve support for "polyglot architectures"
fkirc opened this issue · comments
attranslate is a new tool for "synchronizing" translation-files: https://github.com/fkirc/attranslate
Now you might ask: Why do we need yet another translation-tool?
The short answer is that the landscape of iOS-development changed significantly over the last years.
Right now, there exist tools like https://github.com/netbe/Babelish or https://github.com/metasmile/strsync for "synchronizing" iOS translations.
Those tools are perfectly fine for "traditional" apps that use only Android-XML-files and iOS-string-files.
However, due to frameworks like https://capacitorjs.com/ or https://flutter.dev/, so-called "polyglot architectures" have become increasingly common.
"Polyglot architectures" are not just a theoretical spin. In fact, I observed real apps that use JSON-translations, iOS-translations and XML-translations within one and the same project.
To support such "polyglot architectures", I wrote attranslate: https://github.com/fkirc/attranslate
Of course, attranslate works as well for any traditional iOS apps.
I preferred to open an issue instead of a PR, because this might be a little bit controversial for "traditional" iOS developers.