[Oscailt] translation

[Terence]

Hi,
Yes please send whatever code changes you have made and send them directly to me because the Oscailt email list will strip off any attachments.


For the next release (3.4), I have been doing some work with translation for the admin screens, but I have not done them all, although it will make the PHP code harder to read now. They will have their own xml files like edittypes.xml, editeditors.xml, editroles.xml etc etc.
 
I too realized that we need a general XML file to hold common strings because there are many in the main body of the PHP code. At the moment, I have created a hard-coded PHP file for these common strings. There is very little in it at the moment, but I will let it grow and see what happens and maybe migrate it to XML later. 

In the last release you will see a file called objects/languagedates.inc where I hard coded some date related strings.

I agree that the XML files for some of the modules has too much data and it would be better to separate out the configuration and translation. I will have to think about this.

Let me know what other problems that you have found and what other things you would like to see changed.

rgds
Terence
P.S. What version of Oscailt are you using?

--- On Fri, 20/11/09, Bertagaz <bertagaz at ptitcanardnoir.org> wrote:

> From: Bertagaz <bertagaz at ptitcanardnoir.org>
> Subject: [Oscailt] translation
> To: oscailt at lists.indymedia.org
> Date: Friday, 20 November, 2009, 11:51
> Hi,
> 
> I was willing to finish to translate oscailt, particulary
> some bits of
> text still left in the php code. I already did for some
> modules, mostly
> article and filterbox one and integrated this text in their
> xml and
> display files. I'll send a patch against latest cvs if you
> are interested.
> 
> But the more I'm working on it, the more I tell myself that
> splitting the
> translation part of modules from their configuration xml
> might be a better way
> to do. That would help having each modules configuration
> page a bit
> lighter, as they are for some of them already containing a
> lot of
> parameters. And even using the xml method would left some
> remaining text,
> like the "save preferences" link in displayobject.inc, that
> would require
> to have some more global method to translate oscailt.
> 
>  But that's kinda lot of work, so before trying to see the
> way
> to do that (using PO maybe, like in wordpress [1]), I
> wanted to see if you
> had yourself talked or thought about the way to do that
> clean in oscailt.
> 
> bert.
> 
> [1] http://svn.automattic.com/wordpress/trunk/wp-includes/pomo/
> _______________________________________________
> Oscailt mailing list
> Oscailt at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/oscailt
>