3
I found that Google translate will accept cut-n-paste code from the language files.
It works because the definition 'name' contains underscores so is is treated as one word and remains unaltered.
So if you paste:
Quote:
//Main menu links
define("_PROFILE_MI_EDITACCOUNT", "Edit Account");
define("_PROFILE_MI_CHANGEPASS", "Change Password");
define("_PROFILE_MI_CHANGEMAIL", "Change Email");
you get:
Quote:
/ / Main menú de enlaces
define ("_PROFILE_MI_EDITACCOUNT", "Editar cuenta");
define ("_PROFILE_MI_CHANGEPASS", "Cambiar Contraseña");
define ("_PROFILE_MI_CHANGEMAIL", "Cambio de correo electrónico");
Of course, this is a literal translation which is seldom as good as a human translation, but it's useful if you add some new definitions to a popular module which already has several language packs.
A module to manage this would be a good idea though.
![](https://xoops.org/uploads/smil3dbd4d6422f04.gif)
Or perhaps a module that automatically passes the developer's native language definitions through an online translator and feeds back everything in your own language? (one that was not browser dependent). That would remove the need for language packs completely.
A thread is for life. Not just for Christmas.