Description of problem: Java .properties files often contain entries which are not meant to be translated, but are instead a form of configuration. (Sometimes it's the entire file, sometimes not.) We should implement a mechanism which would allow developers to mark up sections of .properties files as non-translatable, so that they won't be imported into Zanata and modified by translators, creating additional work and potentially introducing runtime bugs. This page describes a suggested scheme: http://wiki.eclipse.org/Eclipse_Globalization_Guidelines#Non-translatable_Message_Strings We already have an implementation for this scheme in Zanata (in PropReader), it just needs to be integrated into the REST client.
Implemented in https://github.com/zanata/zanata/commit/02e9482314bfc7088bd410d9d347b1668e2fcef3 (master branch)
Test cases: 1. WeldCore 1.1> jboss_as/build.property # START NON-TRANSLATABLE # END NON-TRANSLATABLE Sandwich the whole string 2. WeldCore 1.1> examples/build.property ## START NON-TRANSLATABLE ## END NON-TRANSLATABLE Sandwich the 1st string 3. WeldCore 1.1> environments/servlet/tests/jetty/src/test/debug-resources/META-INF/jboss-test-harness " # START NON-TRANSLATABLE" " # END NON-TRANSLATABLE " Sandwich the 1st string " # # START NON-TRANSLATABLE" " # # END NON-TRANSLATABLE " Sandwich the 3rd string "# START NON-TRANSLATABLE" is above the 5th string Passed. VERIFIED with client API version: 1.5.0-alpha-2, server API version: 1.5.0-alpha-3-SNAPSHOT