View Single Post
Old 01-08-2012, 04:57 AM   #76
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
Quote:
Originally Posted by ixtab View Post
I have not taken the final step of updating the source .properties on transifex. eureka, Could you please verify that the output of "extract" makes sense before we go anywhere else? (BTW, this would also be a possibility to check for differences between 5.0.0 and 5.0.1. I tried the md5sum thing, but it's pretty useless because md5sums of almost all files have changed. I'm attaching the output of "extract" for 5.0.1.) Then the only thing left to do is to actually update the source files for transifex... Could you please do that? (I don't know how you managed to automatically update the .tx/config and have the files appear on transifex with the correct name etc.)
I've ran this tool on 5.0.0 resources: tool's output is attached. No resources were changed between v5.0.0 and v5.0.1, as far as I can see. You could recheck, if you wish.

Tool's output, however, brings some difficulties to checking differencies with 'diff -r'.

Firstly, line endings in my output are '\r\n', while in yours they are '\n'. I'm on Windows, as you can guess. I think it'll be useful, if line endings will be uniform: '\n'. Could you implement it?

Secondly, timestamp in header comment. Could you remove it from output?

Also, could you output in UTF-8 without \uXXXX escape sequences?

Overall, looks like I'm far behind you in progress of my JS tool. I'll try to speed up the work. I'm now refactoring it to fit parsed JS into nice internal data structures and planning to use XLIFF format for output. XLIFF is a XML, so I can attach metadata (like, 'it should be wrapped into MessageFormat constructor call') to translatable strings.

About uploading to transifex. I've made it with some throw-away scripts. One for scanning of src/5.0.0/framework for .properties and crafting .tx/config. Then I've manually changed all slugs of resources in this config (slug's length shouldn't exceed limit of 50 characters, and I wanted to put sensible abbreviation of 'com.amazon.kindle.<...>' into these 50 characters). Then 'tx push'. For displaying nice names of resources in Transifex WebUI, I've made another script which changed resources's names with using of Transifex API.

I've deleted these scripts, but surely I can make them again. I'll wait for your response about line endings in tool's output before importing this output into repository and Transifex.
Attached Files
File Type: zip extract_500.zip (119.0 KB, 219 views)
eureka is offline   Reply With Quote