View Single Post
Old 01-09-2012, 03:31 AM   #92
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
Some thoughts on Java resources extracting results.

(Looks like forum adds spaces into long file names. They are shouldn't be there, but I don't know how to fix it. Hope, you'll find out where spaces are unnecessary)

It would be good to have tool's option to add locale code suffix at filenames without it. Like 'kt-l10n.jar ... --default-locale-suffix en' and then instead of DeveloperCerificateInstallerResources.properties I will get DeveloperCerificateInstallerResources_en.propertie s (but DeveloperCerificateInstallerResources_de.propertie s will stay with it's name as-is). It is required for importing into Transifex, where source file must have locale code suffix.

There is could be conflict, if, say, we are extracting Rc.properties into Rc_en.properties, but there is already Rc_en.properties extracted (as-is) a bit earlier. Or, we are extracting Rc_en.properties into Rc_en.properties (as-is), but there is already Rc_en.properties, extracted from Rc.properties a bit earlier. I think following rules should apply:
  • extracting Rc.properties into Rc_en.properties, but Rc_en.properties already exists - don't overwrite, issue a warning
  • extracting Rc_en.properties into Rc_en.properties (as-is), but Rc_en.properties already exists - overwrite, issue a warning
That said, I've found some files with suffixes '_en_US' and '_en' in current extraction results, while, mostly, the same resources, but named without locale code, are extracted also:
  • com\amazon\ebook\booklet\reader\resources\DefaultD ictionaries_en_US.properties
  • com\amazon\ebook\util\dict\resources\SimpleDictLoo kupFormatResources_en.properties (but there is no SimpleDictLookupFormatResources.properties)
  • com\amazon\ebook\util\resources\SimpleTextListForm atResources_en.properties

I've looked into their's contents...

I think DefaultDictionaries.properties and all it's localized versions (that with locale code suffix) should be blacklisted from extraction. Not localized version of SimpleTextListFormatResources.properties (that without locale code suffix) should be blacklisted, but it's localized versions should be
extracted. SimpleDictLookupFormatResources_en.properties could stay out of blacklist, but I'm not sure and will be OK if it will be blacklisted too.

But there is no urgent matter as it doesn't prevents me from importing process. I've added '_en' locale suffix (as default) by hand and will delete some resources from tool output manually:
  • com\amazon\ebook\booklet\reader\resources\DefaultD ictionaries_*.properties
  • com\amazon\ebook\util\resources\SimpleTextListForm atResources.properties
  • com\amazon\ebook\util\resources\CliticUtilResource s_*.properties

Last edited by eureka; 01-09-2012 at 03:48 AM. Reason: add list of resources excluded from importing
eureka is offline   Reply With Quote