Let's make Pligg more localization friendly

[formicin]

Pligg needs to be more "localization friendly". I installed beta9, localized everything in every php file taking days, then I updated to beta 9.1, everything is back in English except the ones in lang.conf . I localized them again, but it is a real problem. It is really hard to check every file for English words and localize them. Half English and half other language websites really look odd, so what are your opinions for making Pligg more localization friendly?

[savant]

localization in php pages, you shouldn't need to do that

what pages did you have to change.

[pligiro]

I can't localize Categories, Message Inbox and a couple of other words, which I don't remember now.

[kbeeveer46]

The point of modules are that they stay outside of the core Pligg code. For example, the private messaging module has its own language file inside of the module in /modules.

[pligiro]

Originally Posted by kbeeveer46

The point of modules are that they stay outside of the core Pligg code. For example, the private messaging module has its own language file inside of the module in /modules.

Yes, I catch that, but this word "Categories", "Message Inbox", "Check spelling" seems to be somewhere in .php files. "read more", for example, I found somewhere in .tpl file.

[formicin]

Tell this to a friend and some other ajax files also use some hard coded English words. I remember "Please wait, loading...." and "Sent!" in php files.

[pipin]

Originally Posted by formicin

Pligg needs to be more "localization friendly". I installed beta9, localized everything in every php file taking days, then I updated to beta 9.1, everything is back in English except the ones in lang.conf . I localized them again, but it is a real problem. It is really hard to check every file for English words and localize them. Half English and half other language websites really look odd, so what are your opinions for making Pligg more localization friendly?

i totally agree and therefore pligg should get rid of all phrases which are hardcoded in other files/modules too.

[formicin]

But the question is, how can we achieve that? I think the problem is .js files are not generated on the go, so they can't have PHP variables. The solution is the way TinyMCE uses. All the visible words are coded in curly brackets and there are language files like en.po or es.po, you just pick your language in a config file. Can Pligg adapt that method?

[formicin]

There are lots of core files that include english sentences. I think all of the core developers use english as their native language, so "all I wanna say is that, they don't really care about us".

[pipin]

Originally Posted by formicin

There are lots of core files that include english sentences. I think all of the core developers use english as their native language, so "all I wanna say is that, they don't really care about us".

look at the svn and you see that they are getting rid of most of the language coding in other files.