[wp-polyglots] Why the language files are placed in wp-content/languages directory by WordPress 2.2?

[Mohd Tarmizi]

I've also noticed about this.

In WordPress version 2.1, the right place to put the translation file would be in "wp-includes/languages". But if the script doesn't find anything in that directory, it will fall down to "wp-contents/languages". So, if you put the translation file into "wp-contents/languages" instead, the translation will also work.

Don't know how things work out in 2.2 though.


----- Original Message ----

From: Hasan Karaboga <hasan at teknoseyir.com>

To: wp-polyglots at lists.automattic.com

Sent: Thursday, May 17, 2007 7:37:56 AM

Subject: [wp-polyglots] Why the language files are placed in wp-content/languages directory by WordPress 2.2?



Hi,



In WordPress 2.2 I've observed from the config-sample.php file that the language file's directory has been changed.

It is now wp-content/languages, instead of wp-includes/languages.

And also, if we place the .mo file into wp-includes/languages, it still works. 

What is the reason for that change?



And, in that document in codex (http://codex.wordpress.org/Files_For_Direct_Translation)

it is said that "wp-includes/js/quicktags.js - this is entirely JavaScript, not PHP, so it does not use gettext. All text for buttons, menus, etc. needs to be translated." 

But in WP 2.2, this file is gettexted by wp-includes/scrip-tloader.php file and we don't have to translate quicktags.js by WP 2.2. Am I right?



Regards,

Hasan.

 _______________________________________________

wp-polyglots mailing list

wp-polyglots at lists.automattic.com

http://lists.automattic.com/mailman/listinfo/wp-polyglots













       
____________________________________________________________________________________Pinpoint customers who are looking for what you sell. 
http://searchmarketing.yahoo.com/