The client will get all source files that match the includes pattern. Then, it will try to find all translation files using the given rule patterns. Multiple mapping rules are possible. The rules will be available in zanata.xml only. Existing projects are still handled in the current way. The client will try to apply the mapping pattern to any found translation file, and based on that result it will choose a source document to upload to. This is only for translation files. Available placeholders: {path}/{filename}/{locale}/{localeWithUnderscores}/{extension} (The placeholder delimiter is TBD, but {} sounds like a good fit.)
placeholder {path} is anything between src-dir and filename. For example, if src-dir is my/directory and the source file found is my/directory/foo/bar/message.pot, then {path} is "foo/bar", {filename} is "message", {extension} is "pot". Given locale "de-DE", trans-dir "trans" and rule "{path}/{filename}_{local_with_underscore}.po", The final translation file will be put under: trans/foo/bar/message_de_DE.po
This bug will also address bug 1098836. For gettext project it will auto covert '-' to '_' in locale code.
https://github.com/zanata/zanata-client/pull/31
VERIFIED with https://github.com/zanata/zanata-client/commit/07f42ed1ac87976f8a68a5109aa2c91d6e404011
*** Bug 1098836 has been marked as a duplicate of this bug. ***