More Mozilla-like

The main goal was to make it simpler for KompoZer users to get a localized app. As a developer, I prefer to ship only one build per platform and one cross-platform language pack per supported locale; but obviously, most users prefer to download a localized build… like they do for Firefox, Thunderbird or SeaMonkey.

Cédric has spent more time than expected on these localized builds — partly because the lead dev forgot to mention a new localized string in the latest revision (ahem). After some work and a lot of tests, we’re now pretty confident that these localized builds work fine, so we’ve removed the “Localizations” page and included all langpacks in the main “Download” page.

The other main trouble when dealing with localized builds is that a lot of files have to be uploaded for each release. The old SourceForge File Release System was a complete blocker: we had to upload all files in a common directory on, then use their web interface to add each file one by one to the KompoZer project. Fortunately, the new SF File Release System is more straight-forward: each project now has its own “releases” directory, and it’s possible to rearrange files within this directory with simple shell commands, on SSH — errr, at least, when the “releases” directory is mounted, which isn’t always the case.

For the upcoming beta2 release, we should be able to release all localized builds at the same time. Hopefully.

Missing locales

KompoZer 0.7.10 is available in 21 languages; but so far, we have only 10 locales for KompoZer 0.8b1.

  • 2 locales are almost ready: Dutch and Simplified Chinese. These locales are still available for KompoZer 0.8a4 but haven’t been updated for 0.8b1. It should require only a few minutes to update them…
  • 5 locales could be easily updated from KompoZer 0.7.10: Hungarian, Japanese, Portuguese (Brazilian + European), Slovak. That should require about a day to update them.
  • 2 locales could be updated from KompoZer 0.7.10 but need a little more work: Bulgarian and Czech. I’m not sure these langpacks are fully translated (especially for the Bulgarian one), and there are some known problems with accesskeys and shortcuts with the Czech langpack.
  • 2 locales would need more work because they’re not supported by Gecko 1.8.1: Upper Sorbian and Esperanto. Both langpacks have been made by Michael Wolf. Michael, would you spend some time on these?

Besides, three new locales are almost ready: Finnish, Slovenian and Turkish (≥ 96%) still require a little work to be ready for KompoZer 0.8.

Translators, we need your help! Localizing KompoZer doesn’t require particular technical skills, and wouldn’t require much time for the locales listed above. You can have a look at the KompoZer l10n page to get more information, and of course, you can ping us on the #kompozer chan to get some help.

Default download policy

The new “Download” page now shows KompoZer 0.8b1 by default, but there’s a KompoZer 0.7.10 section at the top of the page — mostly for Windows users. We’ve kept the big, orange “Download” button for Windows users, and added a bold warning for Linux and Mac users: while KompoZer 0.7.10 works fine on Windows, there are known problems on recent Mac OS X and GNU/Linux systems.

The main “KompoZer 0.8” section now displays a locale/platform download table, as well as a big “Download” button that should point to the appropriate version — according to the user-agent. This button is visible for all supported platforms (Windows, Mac, Linux) and defaults to the English version when no localized version matches the user-agent locale.

On the home page, the main “Download” button points to:

  • KompoZer 0.7.10 (English) for Windows users
  • KompoZer 0.8b1 (localized) for Mac OS X and GNU/Linux users

I hope this will significantly reduce the number of mails and bug reports I get from Linux users complaining that KompoZer 0.7.10 crashes with their latest distro.

Still a lot to do

We intend to replace the “Download” buttons by localizable ones as soon as possible: at the very minimum, we’d like these buttons to state clearly which version (platform/locale) they refer to.

The next step will be to localize the whole website, at least for the most active communities. We’ve already begun to work on this, and this should be done before the final 0.8 release.

Of course, this will be an opportunity to revamp the website and re-organize the content. Note that the HTML structure will remain unchanged — we want this website to be usable as an example for beginning web authors and we’ll stick to this simple HTML structure:

   <div id="header"> … </div>
   <div id="menu1"> … </div>
   <div id="menu2"> … </div>
   <div id="content"> … </div>
   <div id="footer"> … </div>

So if you’d like to propose a new stylesheet for, feel free to submit your work: it will still work with the new, localized website.