Ignore or mark when importig terms with Translatable=false flag in xml
I would like the ability to distinguish translatable terms from non-translatable one's by translatable=false flag in xml.
Arguably they shouldn't be added to the terms list at all.
The ability to mark an existing term as non-translatable would be an added bonus.
Romans Pokrovskis
shared this idea
We’ve added support for the translatable=“false” flag. It’s described here how to set it: https://poeditor.com/kb/how-to-set-strings-as-non-translatable-in-android-localization-projects
-
Miguel Aragues
commented
This is a must have for Android projects
-
Victor Neves
commented
Totally agree. Just spent some time using the tool and all seems very promising. However, not having such feature make things so difficult for us as we have many "keys" not translatable kept in the strings.xml .
-
We are aware of this attribute, but you have to know that it is not a standard, but a convention.
As you may have already realized, the projects are cross-platform, so we can't do much filetype-related customization without affecting the others. If you could put them within the same language file and not translate them, it would be great. -
Mo Chawich
commented
This is totally needed!
Our project is linked with Github, after translators are 100% done and exported we got building errors. That is because those terms marked with `translatable=false` were also translated. Finding them one by one to make sure they are not translated is obviously not fun.