MobileRead Forums - View Single Post

eureka · 01-15-2012, 10:57 AM

Most challenging stages of migration are successfully passed (I've marked them with ✔ at Wiki page), but migration isn't finished yet.

@ixtab, I've discovered that:

source files with source_lang = en are appearing as en_US files on Transifex.net after pushing
on pulling all translations (including source files) are landed into appropriate files with locale code name suffix

It means that pushing of source files without locale code name suffix, which are listed in .tx/config with source_lang = en, is leading to appearing of additional files with en_US name suffix after pulling with option --source. And that exceptional source file com/amazon/ebook/util/resources/SimpleTextListFormatResources_en.properties is "transformed" into com/amazon/ebook/util/resources/SimpleTextListFormatResources_en_US.properties.

This could be of no problem for us (who are using only Git repo), as we can just refrain from pulling of source files. But those, who are using just .tx/config, will receive file tree differed from file tree of Git repo.

I've already pushed these resources to Transifex.net, so you can see that source files have en_US locale code. You could also take a look at .tx/config used in pushing and source files (they are located at framework-rc-migration branch in Git repo).

So, what are you thinking about it? Should I continue migration as-is?

01-15-2012, 10:57 AM	#99
eureka but forgot what it's like Posts: 741 Karma: 2345678 Join Date: Dec 2011 Location: north (by northwest) Device: Kindle Touch	Most challenging stages of migration are successfully passed (I've marked them with ✔ at Wiki page), but migration isn't finished yet. @ixtab, I've discovered that: source files with source_lang = en are appearing as en_US files on Transifex.net after pushing on pulling all translations (including source files) are landed into appropriate files with locale code name suffix It means that pushing of source files without locale code name suffix, which are listed in .tx/config with source_lang = en, is leading to appearing of additional files with en_US name suffix after pulling with option --source. And that exceptional source file com/amazon/ebook/util/resources/SimpleTextListFormatResources_en.properties is "transformed" into com/amazon/ebook/util/resources/SimpleTextListFormatResources_en_US.properties. This could be of no problem for us (who are using only Git repo), as we can just refrain from pulling of source files. But those, who are using just .tx/config, will receive file tree differed from file tree of Git repo. I've already pushed these resources to Transifex.net, so you can see that source files have en_US locale code. You could also take a look at .tx/config used in pushing and source files (they are located at framework-rc-migration branch in Git repo). So, what are you thinking about it? Should I continue migration as-is?