Salix OS

Hi,

How do others languages articles have to be wriiten and are managed ?
A dedicated Wecome main page ? A link from the english article to the translated one ? ... ?


++

You can append your locale after the wikipage you want to translate. For example if you wanted to translate this wiki page: to French, you can create this page: All users with a french locale will see the translated page after you create it.

Cool

Thanks.

++

A question just to be sure that this bug doesn't come from me

For example, I am on the page : Ctrl-Alt-Backspace doesn't work
I add /fr in the url, so new page, doens't exist, blabla..., create it.
I do that, write my translation, then, clic to save.
Unfortunately, the new page is saved with a truncated title like this one : Ctrl-Alt-Backspace doesn&
So, that don't do the trick for auto-translating the page.
I have to rename the page and then the magic can operate.

You can check :
http://www.salixos.org/wiki/index.php/S ... ions/Fredg

++

Uhmm, it seems to be "title dependent".
So, translators have just to take care about this, it may work as requested

++

Not saying that translations are bad, but how do you make sure that the translated version is up to date (in sync with english one)?

Mediawiki allow to monitor the changes from pages with email alerts.

++

Thank you a lot for this translations ! A good work !

You're welcome

++

There was recently a talk in the jabber room between me (as the initiator ) and JRD about this topic and looking for an easy and quick way to have a content management system without the need to replace the wiki.

Yes, there are Drupal, Zope and so on. But do you want to change the complete system only cause of some i18n problems? I think, answer is NO

For such problems, it is always good to have a differentiation between content and layout. Unfortunately, MediaWiki can not do this for us, content and layout definitions are mixed together to the wiki language.

I have the idea to use DocBook XSL and xml2po/po2xml (or po2txt) for internationalization of wiki pages. DocBook is already there in repositories (Slackware package linuxdoc-tools), xml2po and po2txt still needs to be implemented somehow. poedit is already in our Salix repository.

Generation of the localized wiki pages can then be done with usage of little helper scripts: manually, half-automated or completely automated. We only need some bots for monitoring wiki changes and extraction of the texts to be translated as file types po, txt or xml. For the wiki, there will then be some XSLT files to generate the localized static pages.

Advantage will be that the layout (mostly staying statically) is nearly fully independent from translation. Therefore, the translators could concentrate on their job of translation and will not have to hesitate with layout cause it is not included in their working files.

I am going to do some tests if you agree on this process.

References:
http://www.sagehill.net/docbookxsl/index.html
http://live.gnome.org/GnomeDocUtils (for xml2po)
http://translate.sourceforge.net/wiki/toolkit/txt2po

P.S. Here you can learn how the LXDE team solved i18n problems for their documentation:
http://www.slideshare.net/medicalwei/ho ... tionalized

The Zope trick:
http://wiki.zope.org/zope2/I18nInternat ... iki.org%3E

EDIT:
It seems that we need not to go the way over xml files. There is also html2po/po2html available in the "Translate Toolkit & Poodle". And there are a lot more of supported formats!
http://translate.sourceforge.net/wiki/toolkit/html2po
To get better localisation support, Salix team could create or join an (official) Poodle server.
http://translate.sourceforge.net/wiki/p ... ve_servers