tag:blogger.com,1999:blog-3206415812059189210.post1124444087422002102..comments2023-07-12T02:43:20.576-07:00Comments on Cocoa Musings: Localizing Cocoa SoftwareRyanhttp://www.blogger.com/profile/11265111661371250363noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-3206415812059189210.post-21876924122149491902008-10-20T15:53:00.000-07:002008-10-20T15:53:00.000-07:00Regarding the comparison with other platforms - I ...Regarding the comparison with other platforms - I played with Trolltech's Qt some time ago, and I must say I'm shocked that the localization in Cocoa takes so much effort. The difference is that in Qt, you never position widgets/controls manually, you just put them in vertical or horizontal containers and set their alignment, scaling behaviour etc. If you want to do localization, you extract strings, translate them, put them in separate language bundles, but there's no such thing as separate UIs for each language! Strings are just replaced automatically, and the widgets are repositioned/rescaled according to the rules you set, depending on specific phrase lengths.<BR/><BR/>The mere thought of having 10 separate UI designs (NIBs) differing only in the language used for the labels, which all need to be updated separately after each change in the application, is making me shiver. It's as non-DRY as possible. If you have 10 methods that do almost the same thing, do you keep them separate and copy-paste each change to all of them, or do you refactor this so that there's only one, configured by parameters?...<BR/><BR/>I still can't believe they couldn't come up with something more sensible...Kuba Suderhttps://www.blogger.com/profile/10820083350428666188noreply@blogger.com