Anonymous
Any news on that ?? – š
Anonymous
To Jason, Matt:
Is there a date on the wp_translate thing. It’s been an month since the annoucement of the wp-translate function. And there are now 10’s of localized files based on Otsukare’s version. Doesn’t it just take a couple days if Matt work with Otsukare on the issue.
No update 5 weeks after Otsukare effort ?
Devs, are u still working on this highly important feature ?
at least may we have a simple roadmap with dates and milestones ?
and FYI, I would be glad to help on the french translation š
Anonymous
Hello all, I’m also waiting for some decision about the translations, or at least updates of the progress.
I’m thinking about transalate my blog to swedish since the rest of my current site is swedish, but I want to follow the recomendations.
//Robert
Upgrading to WP v1.0.2 Multilingual Edition
Go to http://sourceforge.jp/projects/wordpress/files/ and download wp102-multi.zip.
Then overwrite *all* existing files (except wp-layout.css) with what you’ve just downloaded; most of the files are modified since the last version (v1.0.1-miles).
After that, proceed as follows:
* If you are using the newest release from wordpress.org (wordpress-1.0.2-blakey):
–> go to /wp-admin/change.php
* If you are using the last release from wordpress.org (wordpress-1.0.1-miles):
–> go to /wp-admin/change.php
* If you are using v1.01 Japanese Edition provided by wordpress.xwd.jp:
–> go to /wp-admin/change.php
* If you are using v1.0 Multilingual Edition provided by wordpress.xwd.jp:
–> go to /wp-admin/upgrade.php
At last, delete these files you won’t need anymore:
change.php、upgrade.php、upgrade-functions.php、upgrade-functions.php
I’ve ended distribution of Japanese Edition (not “Multilingual” Edition) as of March 12.
Please use Multilingual Edition instead so we can stay compatible with wordpress.org’s original version.
Ok, nice to see that the project went forward!
However, i would like to point out that the language file covers only the administration files. The index.php file in the multilingual edition still has hard-coded text in it (e.g. “Filed under:”). I think that if we want WP to be really multi-lingual, we have to focus not only on the authors, but on the readers too…
For example, after 4 or 5 months using WP, today i published a post closed to comments, only to discover that the comments_popup_link() function, which is deep inside wp-includes/template-funciotns.php, uses a $none variable that throws a “Comments off” english text on the page.
Now, it looks bad to a reader if i have all the page in portuguese (say), but there is a single phrase in english.
I don’t mean to just criticize – ithink this project is very important. But i think that someone who is authoring with WP is expected to know some english, the same doesn’t go for readers.
Cheers,
Eduardo
This is great news!
What about the file format ? Does it stay the same, or is it about to change, as Jason hinted ?
Can we resume translating in the current fileformat ?
Anonymous
You guys should look at Java’s mechanisms for Internationalization and Localization – they’ve already worked all this out, and it works really nicely.
And a nice idea if you haven’t considered it is just to use the user’s locale (which they set in their browser – you can get it from the request) to determine what language to display messages in.
Anonymous
Sorry, I didn’t get it:( What should I do to translate my blog in to diffirent language (in my case its russian)?
> What should I do to translate my blog in to diffirent language?
Translation is being done at http://wiki.wordpress.org. Go to:
http://wiki.wordpress.org/index.php/WordPressLocalization
and create your language’s page.
post translation of the phrases on this page (e.g. ‘Edit timestamp’ etc.):
http://wiki.wordpress.org/index.php/lang_en
Here’s “How to Use Wiki”
http://wiki.wordpress.org/index.php/HowToUseWiki
Hope this helps!
My, people are not listenning!
Look: translation as it is being done now will not translate the blog. It will only translate the admin pages. The page that readers actually read has hard-coded english that must be changed in the index.php page and inside some functions (template-funcions.php).
Somebody (Otsurake?) more involved in the coding would take a look at this, please?
Anonymous
Thank you for helping me!
I have translated WP to russian. How can I apply the language to the blog now?
anatman, it translates not only the admin pages, but also registration, login etc. index.php and other stuff can be easily translated manually.
This is my interpretation of the events unfolding before our eyes. This is my guess:
WP core developers are still looking into the translation issue. When they are ready they will publish the official -or right- format for language files. It is a complicated choice. There are several issues to consider.
In the meanwhile we will have to do with the language file format (and method of translation) provided by the WP Multilingual Edition. This file format you find currently on WP Wiki Localization pages. – This language format is an ‘easy’ or ‘common’ format. Nothing wrong in that. It is very good.
To use this ‘easy’ or current lang file format you have to use WP Multilingual Edition. The lang files work only with it. If I am not mistaken the Multilingual Edition is maintained by Otsukare. If there are functional changes to WP the same changes will be made to Multilingual Edition as well. Find your updates there.
I believe what we have here is a parallel version of WP. It simply fullfills the needs of multilingual users in the short term. It is not a fork. Something was bound to fulfill the void: after almost 2 months there is still no official lang file format available.
If you translate the strings and use the current lang file format your work will no be in vain. Whatever the right file format will be the same strings will have to be translated. But it might involve a lot of ‘cutting and pasting’ when converting.
As for whether a particular translation is complete or not – I have not installed the Multilingual Edition. But having done some translating in the past there are always odd sentences deep down that are left in English. Even in programs that have claimed to be fully multilingual for several years. To hunt down those we need community effort. – So, a lot of work ahead.
I hope I did not offend anyone…
