Previous version (October 2004): no modified product

Besides the current version (April 2005) for Coreblog 1.1, we realeased a previous version (October 2004) for Coreblog 1.0, which does not require a different product installation, but, instead, works with the standard Coreblog downloadable from Coreblog.org

See the running demos for that previous version:

To run these localised versions of Coreblog, and to localize your own version in another language, you need:

Coreblog (tested with version 1.0).
Localizer (tested with version 1.1.0a4). This product needs also iHotfix and iTools to be installed.

Downloadable localised skin files (.zexp files):

Follow the How-to instructions below to install.

This localisation work only comprises the public web interfaces of Coreblog. Management interfaces based in the ZMI have not been touched.

These Coreblog skins not only are localised, but their layout is adapted to pure CSS, following the CSS-compatible template of Movable Type 2.x. That work was programmed by Jeffrey Hicks.

The default skin goes with a MovableType Rusty CSS style, which has been distributed by MovableStyle.com with a Creative Commons license.

Bugs: problems have been reported by users of non-latin character sets.

How-To Instructions: Install a localised version of Coreblog

We have prepared two localised versions of Coreblog, in Spanish and in Basque. To run them, you need:

Get those products installed on a Zope instance. Then, you can proceed.

1. Download the es-i18n-v1.zexp file (we'll install the Spanish version in this example).

2. Create a given Coreblog object on your Zope server. Add some categories and trial messages.

3. Go to the Contents tab of your Coreblog, and delete or rename the Modules folder.

4. In the Contents tab, click the skins folder, and inside that, import the es-i18n-v1.zexp file.

5. Go to the skins tab of your Coreblog and change skin, choose es-i18n-css

6. That's it. It will look like this trial

Additional notes

if you have already a previosly working coreblog, if you install this skin your modules organization and the css style sheet will be substituted.

After installing this CSS version, the design changes that you may do will be better made touching the style_css document on folder contents.
GPL'ed software. No warranty.

Localize and install Coreblog in other languages (simple method)

1. Install, for instance, the Basque skin eu-i18n-v1.zexp following the steps explained above.

2. Go to the Contents tab of your Coreblog, and you'll see three particular objects, all linked to Localizer the product: Localizer, lf and gettext. The interface messages are inside 'gettext': get there, and substitute the Basque translations of strings with your own language. You may also upload/import a .po file with the messages. Consult the .po files here

3. Then there's the lf object, which is a LocalFolder and is used to store logic. There are few locale-sensitive l elements of logic at Coreblog. Just 4 formats for time/date rendering, and the factor defining when a week begins on the calendar, be it Sunday or Monday. The Basque logic date/time formats are like this:

"03:30", defined as localdate1, which is the same as in the original Coreblog and appears with each entry
"04.07 04:35" month and day numbers, and then the time, defined as localdate2 and which appears at some recent modules
The complete date, "2004.04.14 04:35" with numeral year-month-day and time (this Basque form happens to be also the ISO standard) defined here as localdate3 and which appears with comment and trackback bodies.
The week-beginning factor is Monday for Basque.

If you are happy enough with this formats and settings, then you can skip steps #4 and #5

However, you should look at the localdate4 methods, which renders the complete day, including weekday and month names...

4. To adapt the date formats mentioned in the previous point, enter into the lf object, and in the Contents tab of it, click on the folder_eu object. You'll find the three localdate methods there. Adapt them as you like.

5. To change the week-beginning factor from Monday to Sunday, enter into the lf object, and in the Contents tab of it, click on the folder_eu object: go to the Properties tab of that folder and set the weekbegins integer property as 6 (for Sunday). For Monday, it's 0.

6. It's done. As for the Localizer object and product, this is as if your Coreblog works in Basque. But as you have translated the messages in step #2, and if date/time formats are OK, nobody will notice it. There will be no signs of a Basque locale, neither at the HTML code of the blog.

Localize and install Coreblog in other languages (thorough method), and get, if you wish, a multilingual interface

1. Install the trilingual i18n-v1.zexp following the steps explained above. You will get a Coreblog instance looking like this one, with language change option between English, Basque and Spanish locales.

2. Go to the Contents tab of your Coreblog, and you'll see three particular objects, all linked to Localizer the product: Localizer, lf and gettext. Suppose you want to add a Faeroese version. Then, you must enter into those 3 objects, and in each one, at the languages tab, add your language, Faeroese.

3. Now, the interface messages. They are inside 'gettext': get there, and add translations of strings corresponding to Faeroese. You may also upload/import a .po file with the messages. Consult the .po files here

3. Then there's the lf object, which is a LocalFolder and is used to store logic. There are few locale-sensitive elements of logic at Coreblog. Just 3 formats for time/date rendering, and the factor defining when a week begins on the calendar, be it Sunday or Monday. You'll see, inside the Contents tab of lf three folders named folder_es, folder_en and folder_eu. Now you have to add another folder for Faeroese, ant it MUST be named folder_fo for fo is the ISO code for this language. In orther to do this smoothly, copy one of the previous folders, for instance folder_eu, then paste it, and rename it as folder_fo.

4. Inside the newly created folder_fo you'll find the logic. For instance, the Basque logic date/time formats are like this:

"03:30", defined as localdate1, which is the same as in the original Coreblog and appears with each entry
"04.07 04:35" month and day numbers, and then the time, defined as localdate2 and which appears at some recent modules
The complete date, "2004.04.14 04:35" with numeral year-month-day and time (this Basque form happens to be also the ISO standard) defined here as localdate3 and which appears with comment and trackback bodies.
The week-beginning factor is Monday for Basque.

If you copied folder_fo from the Basque folder folder_eu, that's the way those logic variables appear now in Faeroese. If you are happy enough with these formats and settings, then you can skip steps #5 and #6

5. To adapt the date formats mentioned in the previous point, enter into the lf object, and in the Contents tab of it, click on the folder_fo object. You'll find the three localdate methods there. Adapt them as you like.

6. To change the week-beginning factor from Monday to Sunday, enter into the lf object, and in the Contents tab of it, click on the folder_fo object: go to the Properties tab of that folder and set the weekbegins integer property as 6 (for Sunday). For Monday, it's 0.

7. If you have followed these steps until this point, now your blog has a 4-language interface, like this one but with Faeroese added to Basque, Spanish and English. If you want to reduce the number of languages, go to Contents tab of your Coreblo, and then enter into these three objects: Localizer, lf and gettext. In each one of them, at the languages tab, delete the languages you don't want, and, if you wish, leave just Faeroese for a monolingual blog.

Additional notes

When the Localizer object present at the Contents tab of yout coreblog has more than one language, the languageChange method will show the changing option at two points: inside the blog_banner and at the Credits module. If there is only one language at that object, the changing option just disappears.