1.5.1

You can find the installer package provided by our new contributor William Xu, attached to this post. If you read Chinese (possibly as a native language), please download, install it on your copy of Camino and test the quality of the translation, reporting errors here as comments.

For a very long time I've been the only one able o build the multilingual package of Camino. This is no longer true.
I recently posted a call on our mailing list asking for someone willing to learn the easy tasks required to build the package. Markus stepped up and we had a quick online meeting a few days ago. His work will begin effectively with Camino 1.0.6 and 1.5.1, because I will be on vacation for the first 3 weeks of August.

Thank you and welcome, Markus!

This summer, we'll have a couple of maintenance releases that will fix significant bugs both related or not to the l10n work we do here.

You can find the list of open bugs using the menu on the left or clicking here.

Here's a quick rundown of several bugs:

• Bug 382125 – [l10n] Corrections to localized Chrome strings in Camino DMG
  We are discussing corrections to the already available translations (French, Italian, German). I hope that we can get soon translations from the other requested languages: Spanish, Japanese, Korean, Simplified and Traditional Chinese (previous info)
• Bug 382331 – [l10n] Default browser dialogue's "set" button does not resize well
  This was manually fixed by us and the fix is ready to be included in 1.5.1ML
• Bug 383319 – [l10n] Text not translated in Keychain.nib, elsewhere, in German localisation
  Fixed. Ready to be included in 1.5.1ML
• Bug 382151 – [l10n] Some .strings file are UTF-16LE encoded, instead of UTF-16BE, causing troubles to l10n process on PPC Macs
  

A couple of bugs were fixed regarding the localizability of certain dates display.
Cookies Info sheet: https://bugzilla.mozilla.org/show_bug.cgi?id=335985
History view: https://bugzilla.mozilla.org/show_bug.cgi?id=335986

While we try to keep minor updates (like 1.5.1, 1.5.2...) string-freezed, I think this ones are likely (and better) land on next 1.5 updates rather than 1.6.
I don't know if they will require work, but we must keep an eye on them.