Comments on: Mac Developer Network Launches http://www.red-sweater.com/blog/436/mac-developer-network-launches Mac & Technology Writings by Daniel Jalkut Wed, 17 Mar 2010 22:33:24 +0000 http://wordpress.org/?v=2.9 hourly 1 By: ganyard http://www.red-sweater.com/blog/436/mac-developer-network-launches/comment-page-1#comment-134790 ganyard Thu, 22 Nov 2007 20:19:20 +0000 http://www.red-sweater.com/blog/436/mac-developer-network-launches#comment-134790 Localization Suite from Blue Technologies Group has made things really easy for us in the past. http://www.blue-tec.com/locsuite/ Localization Suite from Blue Technologies Group has made things really easy for us in the past.

http://www.blue-tec.com/locsuite/

]]> By: Martin Wennerberg http://www.red-sweater.com/blog/436/mac-developer-network-launches/comment-page-1#comment-134785 Martin Wennerberg Thu, 22 Nov 2007 08:01:46 +0000 http://www.red-sweater.com/blog/436/mac-developer-network-launches#comment-134785 I find it easiest to simply translate all the strings in code. I wrote some simple categories to the GUI classes that recursively goes down a window, view or menu and translates all the titles etc. using a .strings file. This way you only need to maintain the .strings file and never localize the nib files. If this should ever prove insufficient for some localization you can still have a localized nib for that language. I wish for a good editor for the .strings files though. I find it easiest to simply translate all the strings in code. I wrote some simple categories to the GUI classes that recursively goes down a window, view or menu and translates all the titles etc. using a .strings file.

This way you only need to maintain the .strings file and never localize the nib files. If this should ever prove insufficient for some localization you can still have a localized nib for that language.

I wish for a good editor for the .strings files though.

]]> By: Chris Liscio http://www.red-sweater.com/blog/436/mac-developer-network-launches/comment-page-1#comment-134781 Chris Liscio Thu, 22 Nov 2007 01:26:33 +0000 http://www.red-sweater.com/blog/436/mac-developer-network-launches#comment-134781 I just went through localization with FuzzMeasure 3. I had a French translation done during the course of my beta program, and the UI kept changing like crazy. I even went through converting all my .nib files to .xib files. Anyway, I digress... One thing I found to be easier with ibtool was re-applying existing localization to .xib files that changed as I added new menu items and stuff. I made a script called 'relocalize.sh' which contains the following: #!/bin/bash # # Re-localizes a .nib or .xib file using an existing translation. # # Usage: relocalize.sh localized.xib base.xib # LOCALIZED=$1 BASE=$2 ibtool --generate-stringsfile $LOCALIZED.strings $LOCALIZED rm $LOCALIZED ibtool --strings-file $LOCALIZED.strings --write $LOCALIZED $BASE rm $LOCALIZED.strings -- No matter what, I find that my localized version will inevitably lag behind the English version. However, with tools like this, it will bring us a step closer to being able to offer something wiki-like for community-maintained translations. At least I hope we can pull that off... Another nice feature of using the strings file is that we can avoid having to hand nib/xib files to localizers. Unfortunately, this method of using strings files totally falls apart if we ever hope to supprt Arabic or Hebrew translations. :( I just went through localization with FuzzMeasure 3. I had a French translation done during the course of my beta program, and the UI kept changing like crazy. I even went through converting all my .nib files to .xib files. Anyway, I digress…

One thing I found to be easier with ibtool was re-applying existing localization to .xib files that changed as I added new menu items and stuff. I made a script called ‘relocalize.sh’ which contains the following:

#!/bin/bash
#
# Re-localizes a .nib or .xib file using an existing translation.
#
# Usage: relocalize.sh localized.xib base.xib
#

LOCALIZED=$1
BASE=$2

ibtool –generate-stringsfile $LOCALIZED.strings $LOCALIZED
rm $LOCALIZED
ibtool –strings-file $LOCALIZED.strings –write $LOCALIZED $BASE
rm $LOCALIZED.strings

–

No matter what, I find that my localized version will inevitably lag behind the English version. However, with tools like this, it will bring us a step closer to being able to offer something wiki-like for community-maintained translations. At least I hope we can pull that off…

Another nice feature of using the strings file is that we can avoid having to hand nib/xib files to localizers. Unfortunately, this method of using strings files totally falls apart if we ever hope to supprt Arabic or Hebrew translations. :(

]]>