I make my websites in french. The original strings in my theme are in french, but the original strings in my plugins are in english.

If only I could specify a language for each context, but unfortunately, I’m left with only one choice,

One other thing, ever thought that I might need to correct a typo in the original version of the string, without having to rescan my theme and copy-paste the old translation back into the new original string?

These are little things I’ve been dealing with for years and unfortunately are still not fixed in September 2011, AFTER you’ve gone commercial and I paid my share.

So, why not insert the default language strings in “wp_icl_strings_translations” table too, so they could be changed too, without change of the “wp_icl_strings” table ?

Is this new version 179TC2 including Buddypress Multilingual Plugin. I read somewhere both will be merged. If not, is there a link to new BP Multilingual Plugin version ?

Regards,

I think I understand your point by discussing your following question: “Why do not allow to change all the three languages directly, even the default one, and search for a traduction on the front website even for the default language ?”

The reason why you are not allowed to change only the default one, since the others two language will have to refer to the default strings you are currently using.

As we know, WPML will scan your original strings that located in your theme and plugin files based on (mostly) the _e() and __() function. This original theme and plugin strings will have to be similar with the original ones that being save in WPML table (I will explain it below). WPML will keep those strings in exact-match condition.

Here is the example based on my experiences.

I usually use “Translate theme by WPML” option in order to scan and get the original string from the theme and or plugin files I use. This will make WPML keep/save the original strings (default one) into wp_icl_strings table, whereas the translation strings will be saved separately in wp_icl_strings_translations table.

Since the original strings being saved in the different table, then we can only change the strings that located in wp_icl_strings_translation table from the “Strings Translation” sub menu of WPML.

If you want to change or modify the default strings that being saved in wp_icl_strings table, then you have to change them first directly from the themes and plugin files, afterwards, let WPML re-scan your theme and plugin files in order to update the newest value in your wp_icl_strings table. Then, you will be able to re-adjust the other two new translations with the newest update strings you have just already done.

The conclusion: each time you modify your default strings by modifying them directly in your theme and plugin files, then you have to re-scan them via ”
Theme and plugins localization” menu of WPML, and then re-translate the newest string that recommended by WPML from “String translation” menu.

Another advantages why you should modify the original/default strings directly to your theme and plugin files, since when you want to use the “Using a .mo file in the theme directory.” option in “Theme and plugins localization” menu, then you can easily create the .mo file based on the newest changes you made in the files.

At least, I took this conclusion based on my experience until now.

People, let me know whether you find something new that I don’t know. Also, correct me if I’m wrong, and let me know your additional comment to explain further more about this. Thanks.

I am not sure we understand each other.

I think the default reference is the texts which are in the theme files, in the _e() and __() functions. Not the data in WPML database, which has, I think, an ID primary key to refer to.

What I suggest is to consider the default language as a translation. For example, if there is _e(“Test”, ‘theme_name’) in the theme file, and we are in the default language, it displays “Test” if nothing has been changed or configured in the WPML administration, but displays “Whatever” if changed in admin.

Cyrille