search

fastsupply / growl

Automatically exported from code.google.com/p/growl
0 stars 0 forks source link

Localization process changes #109

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The whole localization process sucks, for developers and as a result, 
localizers. Improve this drastically. Make localizing easy. Make receiving 
updates simple.

Original issue reported on code.google.com by chrisf.g...@gmail.com on 9 Feb 2010 at 11:21

GoogleCodeExporter commented 9 years ago

Original comment by chrisf.g...@gmail.com on 29 Jul 2010 at 4:42

GoogleCodeExporter commented 9 years ago

Original comment by ch...@growl.info on 8 Sep 2011 at 4:07

GoogleCodeExporter commented 9 years ago 
How do we feel about the current process? Transifex + strings translation (and 
auto layout) seems for the most part to work out much better.

Original comment by dan...@growl.info on 22 Mar 2012 at 2:45

GoogleCodeExporter commented 9 years ago 
I'm really happy with it, but there are 3 points left that cause problems for 
the dev side, and one sticking point for localizers.

For localizers:

- They have to dig into the export from ilocalize if they are using iLocalize 
to translate Growl.

On the plus side, we have people doing the translations right on the transifex 
website, and can do it in about 3 hours. To me that's a big win.

For us, there are other problems:

- Adding to the Xcode project is not automatic. Not a huge deal, but the 
resources are in different locations so it's not a single drag+drop. I'm sure 
there's some way to add a resource to a project, but right now it's a manual 
process.

- RTF's cannot be handled through Transifex currently. We could make a new 
parser for them to handle it, but trying to parse an rtf is kind of counter to 
the point of what we're doing. If we removed the need for rtf files, we could 
get rid of this point as well.

- Currently the script isn't very dynamic. It quite literally has variables for 
every language, twice, and then a copy command for every single resource. I'm 
not sure if there's a better way or not, but it's just a thought.

Anyhow, so overall the process is very much improved. Once the script and the 
Xcode project are all handled, then updates are pretty much guaranteed for 
known resources. It's a really nice setup.

Original comment by ch...@growl.info on 22 Mar 2012 at 9:53

GoogleCodeExporter commented 9 years ago 
This is as good as it's going to get for this ticket. Make tickets for specific 
tasks now. Closing.

Original comment by ch...@growl.info on 21 May 2012 at 11:36