Mambo & Aliro common roots

[newart]

good, I like to see more languages in Aliro just now

[newart]

I'm searching other uft-8 languages from the mambo world for using (with all adaptions needed as per your future instructions - maybe not all files or directories are necessary for Aliro) in Aliro. I inform you that it isn't easy to find them so I'd like to see if you have some links where to donwload other languages, maybe chinese, japanese or something else.

I'm a little surprised for this difficulty and sorry for this post but IMHO the translations are very important in a CMS.

[counterpoint]

OK, Alpha4 is now available and the main change is getting the language handling working. It took more work than I expected. There still seem to be bugs in the Mambo implementation of gettext, and it needed some tidying up.

I'm not too convinced about the concept used, and my feeling is that Aliro should next adopt a twin track approach. The issue is how to handle extensions. In Mambo, all base language strings found in the code are extracted into a selection of files, including components, modules, etc. This means that if someone translates their site to a local language, there will be support for the particular set of extensions that is installed there. This limits the usefulness of exporting and publishing the language file.

The immediate Aliro release provides for translation of just the Aliro core, that is the built in administrator side functions and the core services that can be used by both user and administrator side. I'd be glad of comments, but my feeling is that Aliro needs to pursue two initiatives:

1) Ideally, translations should be linked to extensions. I'm working on how to deal with this. My aim is to provide an online service where extensions can be uploaded and stored, and translation carried out, with the ability to download completed translations. That needs to be complemented by a mechanism for importing translations as part of the extension installation mechanism.

2) As it may take a while to get all that working, it seems sensible to extend the Aliro scanning process to include installed extensions so that at least the currently available extensions can be translated within Aliro.

Anyway, I'm hoping that people will try this out and give me feedback, comments, etc. I'll do my best to respond positively to whatever comes!

[newart]

Originally Posted by counterpoint

1) Ideally, translations should be linked to extensions. I'm working on how to deal with this. My aim is to provide an online service where extensions can be uploaded and stored, and translation carried out, with the ability to download completed translations. That needs to be complemented by a mechanism for importing translations as part of the extension installation mechanism.

I think IMHO that it is a good idea. I've seen an on-line system as described by you but I don't know where I saw that... if I realize where I'll post the link here.