ever-traduora
ever-traduora copied to clipboard
allow to import template that will be used to translate
Is your feature request related to a problem? Please describe. in other translation platforms you need to import only template file, after that you can translate all strings from it to other languages. But in traduora i can't do that. Do you plan to add this feature, or how to do workflow? Template file create automatic via extracting strings from source code. When i'm use zanata i'm upload template file to it, and via web ui users translate it to other languages.
any plans to do that?
@vtolstov I'm not entirely sure what you mean. Could you post an example of this feature in Zanata or another software?
http://docs.zanata.org/en/release/user-guide/projects/project-types/ you can upload to zanata gettext pot file (po template) that contains non translated messages extracted from source file. After that via zanata ui you can translate this template to needed languages (en/ru/kr/jp) and download translations. In traduora i can upload pot file but ui says that i need to specify locale. But this file not have any locale, this is template that must be used to translate to locales. Mostly ui must import pot file and user can check what locales for project they want. After importing pot file traduora needs to check for never/removed strings and allow to translate new strings. In zanata i'm periodically upload never template and translate, before release i'm download translations and build my app.
any ideas?
To be honest I don't think this is a feature we are able to incorporate for the next milestone.
If anyone is feeling like contributing this would be a nice feature to start with.
can you suggest how the best to implement this stuff?