Home ›

10.5.x

Current release: Camino 2.1.1

Submitted by Marcello on Fri, 02/10/2012 - 00:26
in
The most recent Camino release is version 2.1.1 (Universal Binary, for Intel, PowerPC, needs Mac OS X 10.4 or higher). Camino 2.1.1 multilingual contains: Chinese (Simplified), Dutch, English (US), French, Italian, Japanese, Norwegian, Spanish, Swedish. Camino 2.1 users should receive notice of the new version by way of the internal software update engine. If you have not set up Camino to check automatically for new versions, use the "Check for updates..." item in the Application menu.

iLocalize introduction

in

iLocalize is a localization tool (http://www.ilocalize.com/ilocalize/). Like AppleGlot, it's basically an interface for nibtool/ibtool, but it has several advantages, compared to AppleGlot, not requiring an external strings editor and having a nice UI for trivial tasks like importing a localized package or updating the source package.
If you localize open-source software (like Camino), you can use it without paying, by acquiring a free license: http://www.ilocalize.com/ilocalize/download.html
iLocalize requires Mac OS X 10.4 and, of course, XCode installed.

In this page, we look at the initial set-up and at the basics to get started. Detailed instructions provided by Igor Pryadkin.

1. Create a new project:

- Use the latest Camino MultiLanguage distribution as the package to be imported
- Check "Create non-existing localized file(s) from base language" option
- Check "Leopard and previous version" compatibility option
- In the following screen, select "English" ("en") and your language (setting "English" ("en") as base language)
- If you find ISO ("ru" in my case) and legacy ("Russian" in my case) designation for your language, select both.
The problem is that the last iLocalize version doesn't make difference between ISO and Legacy names and creates by default a Legacy ("Russian" in my case) .lproj folder when exporting even if you set an ISO ("ru" in my case) designation for your language in project.

2. Preferences

In "General" pane:
- Check all the items in "Automatic actions", and "Display", if not checked
In "Localization" pane:
- Check "Validate string on user input" and "Flag updated files after update operation", if not checked

AppleGlot Blues #2: Camino 1.6b2

Submitted by Marcello on Sun, 01/20/2008 - 11:07
in

The new Sparkle update system worked as expected and notified me (using Camino 1.6a1) that betas were available.
In the meantime, Smokey provided us with a possible fix for troubles affecting the old CaminoFramework+Palette package (it worked OK for me with Leopard on Intel, we're waiting some positive results on PPC before releasing the new package on this site).

I then went to my AppleGlot Camino environment and updated the Italian l10n to 1.6b2. First, thanks to the new Universal Binary framework, AppleGlot stopped complaining and run quietly all its passes. Here are the casualties that I found after the AppleGlot treatment. This list is meant as an help for other localizers, anyway, until better AppleGlot days, its better to plan a thorough package inspection everytime a l10n is updated: results may vary among different languages.

Quick checklist of AppleGlot's leftover working with Leopard and Camino 1.6a1

Submitted by Marcello on Wed, 01/02/2008 - 15:38
in

Starting with a possibly complete l10n of 1.5.4, here's a quick checklist of things to look after inside the package, after you ran an AppleGlot complete routine. AppleGlot will complain about nibtool errors but it mostly gets the job done, as long as you have installed XCode 2.5 and have created a symlink for nibtool:
ln -s /XCode\ 2.5/usr/bin/nibtool /usr/bin/nibtool

  • Check wether the Localizable.strings file inside the Talkback package is OK, otherwise pick one from previous versions (1 file)
  • Check the .strings files inside MacOS/plugins packages and fix version mismatches (3 files)
  • Check all the .nib files for the preference panes, looking for layout tweaks and a string to translate in the Navigation/General prefpane; don't forget to use the validate layout function (8 files)
  • Check the MainMenu.nib file and see if the View menu is localized (1 file)
  • Check the main Localizable.strings file and look for empty translated strings - there should be only 2 about "Script" (1 file)

All in all, it's just 14 files to check and fix in very limited parts. Of course, we're eagerly waiting on the AppleGlot update that should fix all this.

FINAL NOTE FOR THOSE STARTING A L10N FROM SCRATCH

It's strongly suggested to use a PPC/10.4 box. Period.

Syndicate content