29 April

Coreblog localised or so-so

My own blog i18n experiment

I have advanced in my i18n / l10n attempts with Coreblog.
I have released my localised 'skin' as a series of zexp files.

This attempt needs Localizer, first of all, http://www.localizer.org
If you have Localizer installed, then you can proceed.

I have released my localised 'skin' as a series of zexp files. Importing
that folder... then, you change the skin and there it is. I have also
released some notes so others can localize it in other languages. As a
matter of fact, it's not more work than translating some 60 or so strings
in a .po file.
Look here to check .po files: http://www.tumatxa.com/intl/ZTMX/coreblog

Instalation how-to's an the zexp files, here:

A localised Coreblog looks like

https://manterola.org/familia/luistxo/coreblog/esblog in Spanish, or
https://manterola.org/familia/luistxo/coreblog/triblog with language
change in the interface

Of course, this is nothing more than a personal attempt. I hope Atsushi and
the people at Webcore will face one day the i18n of the original product.
Without that, sustainability of l10n efforts is difficult. I must also say
that I am no techie at all. I just have some user experience with Zope, and
also have some ideas about i18n and l10n.

At least I tried to follow the clear and standard way that Localizer
provides for l10n: a string repository following the Gettext methodology,
logic locale-issues stored in particular folders...

A disclaimer: I tried to provide the original default style_css styles
sheet with these skins of mine, but the graphic output didn't look the same
as in the original (I don't know why). So, the skins come with a slightly
modified skin, partly copied (fonts and other things) from Tom Lazar's
coreblog at http://www.tomster.org/blog>Tomster.org

Posted via: luistxo (07:50) | Permalink | Comments (0) | Trackbacks (0)

Ten Commandments for bilingual blogs

Blog i18n (4)

Is it possible, bilingual blogging?

Yes, and there are sites out there. But, the truly coherent, consistent, bilingual blog... I just haven't found it. My blog isn't either that kind of blog. I have written a list of features (Ten Commandments) with which true multilingual blogs should comply.

My own blog is, surprise! quite compliant. Well, this list reflects personal viewpoints, so no one should feel disappointed with this superiority of standards shown by The English Cemetery: it's a biased commandment list. However, I miserably fail with commandments 6 and 7, so far. Regarding 4, my blog could behave better also (and it can, using the power of Zope and Localizer, but I'm just too lazy right now).

So, the good, true and faithful bilingual blog should have:

  1. Language change. There should be a button, link, or pulldown menu to click or select, present in every page. That's the way to turn from reading content in one language to the other in a bilingual blog. Mixtures of languages in individual pages, no, that's not OK. Langauge change behaviour could vary: the distinction between symmetrical and asymmetrical blogs that I describe here is a key issue.
  2. Monolingual entry page. The main page appears to you in a given language, coherently English, or coherently Basque. Then, you may opt to change language. The first page to appear may be set by default, or perhaps, depend on browser settings. This commandement rules out the usual mixture of Lang1 / Lang2 messages in the first page, ordered by pure chronology, as well as the very curious double-horizontal layout of several sites.
  3. Interface as well as content bilingualism. You are reading a Basque post, so you can click on the Erantzunak link, if you know what it means. You are reading an English post, so you can click on the Comments link. Interface bilingualism should be bilingualism, not double-strings. No "Erantzunak / Comments" links. I don't like the redundancy at this en-fr or en-de sites. Messages should be in one or other language, depending on the content or language-category of the post you are reading, or in the action taken by the users when clicking the language change option.
  4. Interface string localisation capabilities. Not just single terms, by locale sensitive logic issues like date formats (and dates are important when blogging) should be localised in each language. In XML feeds, date formats should be standard.
  5. No double reading work. These people, for instance, they translate every post, so they explain things twice, once in A, another one in B. ( Transblawg , 0909 ) Such a blog could work with symmetrical model described in a previous post . One may fell the need to say the same things in several languages, of course, but, the reader? I can only understand that as an attempt of 2nd language or translation-teaching for your readers. Separate messages makes discussion or commenting consistent as well. Basque readers respond to Basque messages, Spanish readers to Spanish ones. Different threads may be constructed, of course. A bilingual messages can't have a consistent thread behind it: are we supposed to comment also in bilingual ?
  6. Open and coherent categorization. So far, my own blog is trilingual cause I have twisted Coreblog to make just 3 categories as locale-defining factors. The result is that I don't have categories, just language options. Other blogs also use categorization for multilingualism.
  7. Character sets conveniently adapted to non-ascii character sets. At the HTML interface level, as well as in XML feeds or pings (trackbacks) delivered.
  8. One separate XML feed per language. This is the most obvious feature to me. Look at the commandments listed here: the mixing of languages in postings, categories, interfaces and so on can be so complicated. The XML feed must always be clear. Those who use the feed with some aggregator or other need clear messages from our feed. Basque users need a clear XML feed in Basque from this site. Basque users who understand other languages and want the other content that I post here, then it's easy: they can subscribe to the other language feeds as well. The XML feed should include, if possible the lang variable marked following the Dublin Core standard or in any other feed specification that there might be.
  9. Same system (that is, ONE system) for the bilingual blog. If it's a moblog, the email posting procedure must be the same for the whole blog, with just one variable (a kewyord in the message or something) to direct the email to the Basque or English section of the blog. If you change the skin, the css-style, whatever, you change it once, it is applied conveniently to the whole blog, to its contents.
  10. Should be based in free software and its content protected by an open license, like creative commons or FDL. I needed the 10th commandement to reach the magic number, so I included this one :-)

Examples out there.

Posted via: luistxo (08:02) | Permalink | Comments (5) | Trackbacks (2)