A number of users have complained about having trouble posting on our forum. Please investigate what happened–
http://zh-cn.forums.wordpress.org/
Nothing was posted since 5 months ago. I don’t seem to be able to access /bb-admin, either.
A number of users have complained about having trouble posting on our forum. Please investigate what happened–
http://zh-cn.forums.wordpress.org/
Nothing was posted since 5 months ago. I don’t seem to be able to access /bb-admin, either.
Any ideas why Twenty Ten and Twenty Eleven are not updating when using the automatic update for upgrading to 3.4? Users are reporting that after they update the themes separately, they lose the translation files for their themes…
Because wp-content isn’t touched on an update anymore.
Yes, themes are not updated together with WordPress, but there is also no support for updates of localized themes and plugins
We are waiting for Language packs – http://core.trac.wordpress.org/ticket/18200
Earlier today, our user reported that MD5 hashes for .tar.gz packages are not generating properly.
Please see this page: http://cn.wordpress.org/releases/
Links like:
are actually the download link to the .tar.gz packages.
It would be nice if this could be fixed.
Broken as a result of this. Working on it.
Thanks. This is awkward because all the ZIP ones are working…
Should be all fixed.
Tested. Thank you.
Hi there,
User “xslidian”, our invited translator and validator reported recently that in translate.wordpress.org GlotPress site, he is unable to approve any strings of WordPress for Android project, as he can approve strings for WordPress core project.
Screenshots he sent to me are attached below, which I think may be useful:
I noticed that in the WordPress core project, the language indicated is “Chinese (China)” but in WordPress for Android project, the language is “Chinese”, which might be the key to this issue.
Hope this can be fixed if possible.
Could you indicate the exact URL for both those cases?
they’re at `/projects/wp/dev/zh-cn/default` (core, normal) and `/projects/android/dev/zh/default` (wp4android, suggest-only)
Slug was wrong. Please use the new http://translate.wordpress.org/projects/android/dev/zh-cn/default as zh will be removed.
Please do a thorough recount for our zh_CN forum:
http://zh-cn.forums.wordpress.org/
If higher permission can be granted, that would be awesome.
In Beta 4, images under wp-admin/about.php contain English text and are not translatable because they are outputted directly with fixed img src attribute. Two suggestions:
wp-content/languages/ before outputting the path.I’d say option 2, but be it as it may, this sounds like a Trac ticket waiting to happen.
Same goes with the Color Scheme thumbnail in Twenty Eleven Theme Options.
Upon the suggestion, I’ve just re-written the three features (Chinese video embedding, Dashboard style modification, and Asian character count fix) in /wp-content/languages/zh_CN.php into three separate plugins. I want them to be enabled by default after installation. To make zh_CN.php more efficient, instead of checking plugin state each time zh_CN.php is required in wp-settings.php, I want to request for an action hook that will run after initial WordPress installation and each core update.
That way I can hook to the “install finished” action and enable the l10n plugins. The reason why I want an “core updated” hook is that I want to make new l10n plugins we publish in the future be enabled automatically, as well. In zh_CN.php, I will of course use add_option() and get_option() to check if the plugins were disabled by the user manually before so it won’t be re-enabled automatically again.
If there’s a better way or guideline for such situation, please let me know. Thank you.
I’m not sure that the i18n builds should be bundling lots of extra plugins.
The character count fix should be in the zn_CN.php file until it makes it into core (There is a trac ticket for it right?) as should the style modifications (I assume these are to pick a more appropriate font?)
What is the video embedding change you are including?
I agree with Peter. Ideally, the only files that are included in dist are po/mo, $locale.php, setup-config, and config-sample. Let’s work to keep them limited rather than adding more.
Okay. Sure it works for me. But I see some conflicts in the suggestions I received from other team members and l10n site maintainers. http://wppolyglots.wordpress.com/2011/10/15/regarding-the-word-count-problem/
To achieve the character count function, I need to include and register a new word-count.js file. Just to confirm: If the plugin solution is impossible, is it okay to put a zh_CN-word-count.js and zh_CN-word-count.dev.js under languages/?
Hi there.
The current JavaScript code for counting words in editor ignores Chinese characters, so I am working on a patch which I intend to ship with future cn.wordpress.org packages.
It seems that the easiest fix is to enqueue a modified wp-admin/js/word-count.js. Is it okay to put a modified version under the corresponding SVN dist/ directory, and get the original word-count.js replaced, OR I have to put it under wp-content/languages/ and play around with the hook to make it be queued to load?
Thank you.
Conceptually, I’d argue that the first option (replacing the original word-count.js) is changing core code, and hence recommend against it. That said, it also depends on what you mean by “play around with the hook to make it be queued to load”. Completely personal and subjective opinion, of course, would love to hear more from the others.
Okay then the first option is out. The real issue is that the built-in word counting function is not working for Chinese characters. By “play around with the hook to make it be queued to load” I mean I intend to include a zh_CN-word-count.js or something else and add a few lines of code in zh_CN.php to make it be loaded and deregister the original word-count.js so that the original core code remains intact and we can make the word counting work when WPLANG is defined as zh_CN in wp-config.php.
This sounds very good, on the other hand
Japanese package includes a fix for this as a plugin:
http://wordpress.org/extend/plugins/wp-multibyte-patch/
If you’re interested, I’d be happy to help the author translate the whole thing but here’s Google translated version of the description page:
http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http%3A%2F%2Feastcoder.com%2Fcode%2Fwp-multibyte-patch%2F
@jiehanzheng, I would recommend you do what the Japanese guys did. It’s working great.
Cool. Thank you for your advice. So for the plugin solution, am i supposed to include a copy of the plugin under SVN dist/wp-content/plugins/? Who should be the plugin author, and may I have a WordPress.org account with the name wordpresschina?
I will look into it, see how it works during the upcoming school long weekend and hopefully include the fix before our next release. I will post any updates here.
Thank you so much, Naoko. It’s a pretty nice idea because of the similarities of Japanese characters and Chinese characters. I will look into it.
The Google Translate version is… to some extend, readable. So thank you for your offer and I will do the research.
After the localized 3.2.1 update, I noticed that Twenty Eleven translation is dropped. Looking through the filesystem, no .po or .mo files could be found under wp-content/themes/twentyeleven/languages/. However, corresponding .po and .mo files can be found in localized packages.
Do any of you have this issue, too?
I you update to Twenty Eleven 1.2 via theme updater, translations are lost.
yeah… something fishy is going on…
Yeah. Many of our users reported that. Besides manually moving .po and .mo files in, is there any better solution to offer to them?
I also tried re-installing the localized core, but Twenty Eleven remained in English
Right now, no. In the future, language packs.
Just an explanation of whats happening here:
The Theme updates from .org do not include localised files, as such, updating to the theme from .org installs a copy of the theme which does not include them.
3.2 no longer updates the theme during a core update (as happened in the past) and core is the only place (At present) which includes the language files.
The same thing would’ve happened with TwentyTen, except updates of core would happen at the same time (which caused the translation files to be copied into place), masking the problem.
Language packs are really the ideal solution to this problem, but not a short term solution for 3.2.x
So we know its happening (now), and we know the cause of it, The only question is how it’s to be fixed. Stay tuned and we’ll sort it out somehow.
Could you please grant the WordPress.org user franklsf validator permission on Chinese (China) WordPress for iOS project? Thank you.
Granted
Hello. I am encountering a problem that the “Untranslated” count on the language list for WordPress project doesn’t match the “Untranslated” filter on the translating screen.
The situation is: there are untranslated strings, but I am unable to filter them out by using the filter; however, they are visible when I go through the “All” list manually. Hope this could be fixed by doing a re-count or so for us to help the translating process to be more efficient. Thank you!
It’s a GlotPress bug (caching), for now just wait it out, please. Thanks for the patience.
Well, this is big. I have rejected some strings in Twenty Eleven translation and they are not in Untranslated (I can find them navigating through All, so it’s no problem, but just FYI).
Woops. Duplicated, sorry. I came here from another ticket and didn’t read the whole text. :$
This post concerns a serious problem with the iOS app to Chinese users.
Our users report that after their upgrading to version 2.8.1, they are no longer able to type Chinese on the composer screen. I tried and now I can prove this problem really exists.
Most Simplified Chinese users depend on the iOS build-in Pinyin IME to type Chinese on the Qwerty keyboard; and a combination of several letters denote several possible Chinese character / word matches, and users choose from several candidates offered by the IME. (See this screenshot to see how it is expected to work, as in most apps.)
But in the WordPress for iOS app, the candidates cannot be shown. Therefore users became unable to type.
I hope this problem could be investigated and solved as soon as possible. And I really appreciate your hard work. I don’t know if this problem affects other languages.
Hello,
There was a bug in the 2.8.1 release that caused the post editor to work strangely. 2.8.2 was just approved by apple today and it fixes the issue. I assume it will fix the issue you were having with Chinese characters, but let us know if it’s still a problem.
Okay. I will keep checking for available updates on my iPhone and collect reports from Chinese users. I will let you know if this persists.
Thank you!
This post concerns the Chinese Credits page. Hope @nacin and @vanillalounge or anyone else this may concern could take a look.
First I am happy to see that the Chinese separator (“、”) is in place on the contributor’s list, but there’s an imperfection that in Chinese we use “。” rather than “.” to indicate the ending of a sentence. So I have one suggestion: to substitue “.” with “。”, or you can just remove the ending period.
I just discovered that this is managed by the po translation files. So no need to fix on the API side. Sorry for this. Please see my next issue:
Another thing I want to report is that the current translator list is inaccurate for Chinese. I don’t know how about other languages, but for Chinese it is not. None of the current 4 “validators” indicated on the Credits page is a currently active validator. It should have jiehanzheng (me) for WordPress, and musiclog for bbPress Plugin. kingler and Paveo also worked on WordPress, but they no longer do. Please help remove those who are inactive if possible.
Thank you.
kingler and Paveo (and jtam) were removed.
Hi. Could you please list all validators of the zh_CN WordPress core project in GlotPress? I found that there are many strange strings who don’t have a “Translated by” field and were not translated by me. It seems that they were imported, but as far as I know, other validators (Paveo and kingler) are no longer working at WordPress.
Although I am going through all the thousands of translations but I am eager to figure out where did stings like this come from in order to prevent such conflict and overriding in the future.
It’s me. I did that. I had imported all those strings.
I wonder when and how you became a validator of the core project. Please don’t simply import your translation again, since that will override all the existing strings, and your expression for some words is kind of different from those existing. I think translate or modify them one-by-one is more acceptable. Thank you.
Another example is that I replaced most of the links to English Codex articles by links to Chinese Codex articles, and your import just wiped them off and I have to revert to my previous translations one-by-one.
Sorry about that. I just found that so many strings did not being translated. So I did that. OK, I won’t do that again. And I do.t know when and how I became a validator. If you feel not good. You can ask administrator to remove my permission. I just wanna to help. If you didnt need that. I stop. Sorry again.
BTW, should I become a validator of bbPress? I already 100% finish the translation of it.
@vanillalounge: as he stated, I hope his validator status at WordPress core could be revoked if possible.
My suggestion for GlotPress is not to directly overwrite any existing strings when importing, instead, mark them as waiting when there are conflicts, to prevent such incident from happening again. Reviewing all translations is really a heavy work that can take days.
@Dreamcolor: I really appreciate your help. I am open to any suggestions from the community and, as many can see, I always reply and process every email, forum post and comments on cn.wordpress.org regarding translation mistakes carefully and correct them as soon as possible, but to some extent I can not stand such suggestions that overrode all of my existing work that will cost much of my extra time to fix.
However, please believe that I will be reviewing all the strings, and I will keep those who are better than existing ones.
It’s now revoked
My suggestion for GlotPress is not to directly overwrite any existing strings when importing, instead, mark them as waiting when there are conflicts
I agree with ‘jiehanzheng’ in this suggestion, since we are three validators for Galician in WordPress.com. And I wouldn’t like to see my work of two years deleted with a single upload.
It would be great if only one person has full rights to review all others’ works. New role like “language coordinator” or “project leader” may resolve this.
Just to be accurate, they won’t be deleted but marked as “Old.” Then we will have to double-click on all the translations, then “All translations of this original,” double-click on your translation again, and “Approve” our translations. This process will need tens of thousands of mouse clicks.
When translation is made on line and approved in GlotPress, it saves previous strings as Old. But seems that when a PO file is uploaded, this action deletes the entire history.
Either way, from now I will save a PO file each time I add a new string, in order to facilitate the restore if there is a similar situation.
Hi. I am making a list page for our volunteers to contribute to translating WordPress, its sub-projects and the Codex. Could you please add Simplified Chinese into these pages:
… and set me as validator for all the Simplified Chinese projects?
Thank you!
All set
Thanks!
Hey, I’m preparing a new release and I was going to add the new Chinese translations.
However, iPhone supports “zh-Hans” and “zh-Hant”. Which of those I should use for this translation?
You should use “zh-Hans” for Chinese Simplified, which equals to “Chinese (China)” in GlotPress. Thank you. Have a nice day!
Samuel Wood (Otto) 12:29 am on December 8, 2012 Permalink |
I see no problems with that forum. I logged in and posted without any trouble.
http://zh-cn.forums.wordpress.org/topic/test-1?replies=1
Samuel Wood (Otto) 12:33 am on December 8, 2012 Permalink |
When you seem to be able to log in, but not to access the admin, then clear your wordpress.org cookies, then log in again using the form specifically on the support forums. You can also just log-off explicitly and back in again, if you don’t want to clear cookies. This usually works too.
This happens when the cookies become unsynced, so you can have auth cookies, but not admin-auth cookies. Thus the site knows who you are, but won’t let you access admin because of the different sets of cookies. Clearing those and re-logging-in will fix that. This can happen on any of the forums, not just specific language ones.
Jiehan Zheng 6:22 pm on December 8, 2012 Permalink |
Thank you! It worked.
And thank you @vanillalounge for replying to that test thread!