Helps to connect developers and translators.
In particular it helps to cover two typical use-cases:
- to provide translators with texts to translate
- to incorporate texts came from those translators
Source codes and resources are likely complicated. Translators are usually too far from app sources. So we are used to send texts in data sheets (CSV, Excel, ODS, etc.).
The tool now uses CSV to export and import texts.
thelper.pl n --android <path_to_android_app_project> --lang es --out-csv <path_to_csv>
- path_to_android_app_project is path at which android app project resides
- "es" langauge is just an example, of course.
- path_to_csv is path to write exported CSV to
thelper.pl a --android <path_to_android_app_project> --lang es --in-csv <path_to_csv> --out-xml <path_to_xml>
- path_to_android_app_project is path at which android app project resides
- "es" langauge is just an example, again.
- path_to_csv is path to CSV file to read importing texts from
- path_to_xml is path to write new string resource XML file to
Indeed, it is. The tool doesn't cover whole variety of Android project string resources. Instead it assumes the following:
- texts are kept in
strings.xmlfiles, i.e. tool to look at the following files only valuesfolder language modificator is the only modificator, e.g.values-es-sw600dpis not the case
Freaky string resource case could be covered by using aliases.
Texts marked as non-translatable are skipped.
And xliff:g is ignored.
Yup, Android app project was just an example too.
The tool could work with iOS app project.
Just use --ios option instead of --android one.
For iOS app project the tool works with <lang>.lproj/Localizable.strings and <lang>.lproj/Localizable.stringsdict.
en.lproj is treated as the default translation.
There's thelper.exported.pl file which is standalone version of the tool. Thanks to fatpack