![]() Now we are ready to really create the project. (Some nibs do not contain any localizable strings so we placed them outside localizable project folders.) Just ignore them and click Next again. When you click Next, another dialog informs you about some non-localizable or read-only files. Set everything as shown in the snapshot below to your needs. Start iLocalize and select File > New Project. Create your iDEV folder in your desired place. I myself use a development folder iDEV and created a new folder iCalamus2_GUI there. Now choose a location on your hard drive where to place the localization project. Uncompress it on your desktop in order to get a functional iCalamus.app there. You need to install iLocalize 4.x which can be obtained for free from the Mac App Store.ĭownload the current version of iCalamus 2 from the official download path given by invers Software. You need to install Xcode 6.x which can be obtained for free from the Mac App Store. Or guess that a localization of iCalamus 2 exists already, but you take over the localization support for this language or are the maintainer but have to set up things new on a new Mac. Imagine that you are the one who adds a new language localization to iCalamus 2. Create a new iCalamus 2 translation project in iLocalize You can leave a response, or trackback from your own site.How to Create an iLocalize Project This page describes how you should create an iLocalize project to be able and localize iCalamus 2 afterwards. You can follow any responses to this entry through the RSS 2.0 feed. On Sunday, July 8th, 2007 at 10:09 pm and is filed under Apple, Français, Internet, School. Oh, and did I forget to mention… It’s Free! Here’s an easy way to test your different localizations without the hassle. It displays only the localizations avaiable for your app. That’s where LangSwitch comes in… It gives you a simple GUI way to switch the localization for only the app you’re testing. I personally don’t really like to use a computer in Chinese… This is especially time-consuming as you have to change the language settings in System Preferences every time you want to change the localization.Īlso, another downside of this is that it changes your whole computer (well, just your session, but whatever…). The only boring and time-consuming solution is to thoroughly test the new UI in every localization before releasing. What then happens is you ship with a faulty localizations, you get lots of weird complain email in Japanese, and… you’re screwed! The thing is: there is a high probability you will make a mistake without noticing (it happened to me once). The thing is, not only do you need to modify your english nib(s), but you also need to make the same changes to every other language’s nibs!!! Alright, since you’ve got no choice, you do it. ![]() With all the feedback you’ve got you’ve decided to make a few big UI changes. With all this fame you get wonderful feedback and even get it localized in 15 different languages. It’s the “next big thing” and you become rich (or not). Now’s the time to localize it… right, you do the job (it’s never pleasant to localize nibs). You develop it in english until you get to a Release Candidate. But, you see, the problem is that sometimes it creates more problem than it solves.Let me explain: say you’re creating an amazing Cocoa app. I mean, compared to REALBasic, or Java, or even Qt… at least it has one. The first time you look at it, it looks really great. One of the things I hate about Cocoa is its localization system. LangSwitch, or how to test your app’s localization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |