I really like the new installation language page in coming WordPress 4.0, but I am not sure what is the main point of it? I am writing article for our users and I am not sure about it. There will be special localized installation packages as in the past (automatically generated), so when user downloads localized version, he usually wants to install this version. So, for 99,9 % users is this new page only some more bothering clicks? Or is there any other purpose? I know that I can download original English version and install WordPress in localized version, but it is edge case. Any ideas?
Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts
I noticed that English (Canada) is not appearing in http://api.wordpress.org/translations/core/1.0/?version=4.0 even though everything in GlotPress is translated for days. Could it be because English (Canada) does not have a “Continents & Cities” that the Rosetta builder was corrected for a few versions back.
Let me share some issues about 4.0 language switching functionality.
- Current implementation for 4.0, adding new languages is not automatic. To get a new language to show up in the language switcher in the admin area, users have to manually copy language files to wp-content/languages directory. For example, if an initial installation is made as English (United States) and later the user wants to switch to other locales (his/her native locale, etc), the user have to obtain the language files from somewhere, upload them to the right directory, and finally change it through the language switcher.
- WPLANG constant is semi-deprecated and doesn’t work like before. It is used as a fallback when English (United States) or empty language option is selected. For example, if an initial installation is English but your wp-config.php has WPLANG with non English locale, WPLANG’s language files are automatically installed during the installation process.
Releasing local packages as usual might be a good idea since it contains local language files in the first place. That always guarantees users to have a choice to switch back to his/her local language without complicated manual steps.
I’m a bit behind with the da_DK 3.9.2 package. When I build from trunk/revision 29189 i get this suggestion:
I made a testinstall and it immediately updated to WordPress 4.0-beta4. I’m not sure that is supposed to happen.
When I build from 3.9 and 3.9.x I get this suggestion.
Looks more right and I would of course change the versionnumber in the filename to 3.9.2 before building. Is that the right approach?
As for 3.8.4 and 3.7.4 should they be build from tags 3.8 and 3.8.x/3.7 and 3.7.x? From these builds?
29190 for 3.8.4
29191 for 3.7.4
Or from trunk?
In a few hours I’ll be building new language packs for RC1 for any locale at 100% for the wp/dev project and all sub-projects (this includes the network admin). Each day as translations are completed, packs will be created or updated. We’ll work out some kinks over the next few days and hopefully have everything in order come September. Expect to hear more from me in the coming days and weeks as we begin a new journey.
@helen is targeting September 3 for release. The about page is done, help tabs are updated, and strings are frozen. You have one week to get everything in order, so good luck and happy translating!
On GlotPress there is now a ticket for cleaning up the locales file. A part of this is renaming the English or native name. If you have time, then please check if there is a change for your locale and leave feedback behind. Like for Chinese the idea is to rename the English names to “Chinese (Simplified)” and “Chinese (Traditional)” for zh_CN and zh_TW.
We are getting ready to submit version 4.3 of WordPress for iOS and need your help with translations. I’ll be adding release notes soon, too!
Thanks in advance!
Side note: does anyone know why it says all of the strings need translated? Some of the strings were in prior versions.
galician development version is translated 100%
there is no untranslated
but in glotpress says 99%
We’re going to release WordPress Android 3.1, can you help us translate the release notes here?
I would like to have i18n SVN access for the Arabic(ar) repository.
Please tell me how can I add a new validators to Latvian translation group?
The Permalinks tab in Admin has a translation bug in Hungarian. It says:
“Ha szeretnénk, megadhatunk saját struktúrát a kategóriák és címkék URLcíméhez. Például használhatjuk a temak kifejezést kategória előtagként, és a kategória hivatkozások így fognak kinézni http://example.org/topics/nincs-kategorizalva/”
The problem is that “temak” and “topics” shall be the same literal string.
There are no strings for default themes in 3.9 branch?
I wanted to release localized version (sorry for delay) and it will not work…
Just saw http://translate.wordpress.org/languages. I really love it, this is what I really want.
I would like to have access to the SVN i18n for help @gabriel-reguly in the new versions pt-BR