Quote:
Originally Posted by ixtab
SimpleTextListFormatResources: This is a tricky case. The "_en" overrides some of the definitions in the base, but not all of them. (There is list.format.type_default.patterns in the base, which is not overridden in any of the existing locales. OTOH, all of the other existing locales "follow" the _en version in terms of content, plus the "default" one should be ok for all languages. So, in this particular case, the _en one should be the base for the translation, and the "base" one excluded from translation.
So the final question is about the naming of source files. I'm still not terribly happy with renaming "base" properties to "_en", because it will change the "semantics", and is not required for transifex. As said earlier, the source filename can be anything (it can even be completely different from the "translated file pattern"), the only thing required is to specify which locale the source file is in. My proposal is to use "blank" properties as sources, with exactly one exception as outlined above (SimpleTextListFormatResources). This one can be manually added to .tx/config.
What do you think?
About the conversion, it certainly makes sense to announce it a day or two before the change. The conversion itself should be pretty simple: - make full update (tx --pull --all)
- convert existing localizations to utf-8 (kt-l10n.jar iso2utf)
- remove all en_US files (to clean up previous source file state)
- extract all resources as UTF-8 (kt-l10n.jar extract)
- update .tx/config
- push sources
- push translations
Of course, it's best to do a test-drive this in temporary directories first, but that is roughly the way it should go. The entire process, when going live, would take at most half an hour (most of the time spent uploading to transifex).
Does that make sense?
|
Yes, your plan is absolutely suitable and makes sense (it's, obviously, THE right plan), but there are some small details you've not mentioned and while I've thought about them it is started to be hard to keep all of them in my head, so that's why I've came up to dumping of my thoughts to wiki. I've made initial draft
here. As you can see, it's the same as you've described. It's still not finished (migration date should be postponed to Sunday or Monday; I've missed removing of old en_US source files etc.), but outline is ready. It's late here, I'll polish plan tomorrow.
I'm also fully convinced to not add locale suffix to original source files. Strangely, I've thought that original files MUST have this suffix, that's why I've mentioned it. Wiki page has 'en' as required source locale code in crafting .tx/config snippet for new resources. It's my bad, tool will be fixed to not require locale code. I'll also add SimpleTextListFormatResources with suffix 'en' as hard-coded exception from common rule.
Also, I'm not so sure about time required for migration. Yes, half an hour is sufficient, but in case of appearing of any unexpected problems it's good to have a time reserve. Big reserve. If all will be ok, an announcement about successful completion could be made before deadline.
I'm certainly overcautious and too paranoid here, because I'm too scared of possibility of losing all translators' work.