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.
WP Polyglots 
Dreamcolor 1:05 pm on May 27th, 2011 Permalink |
It’s me. I did that. I had imported all those strings.
jiehanzheng 1:22 pm on May 27th, 2011 Permalink |
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.
Dreamcolor 1:53 pm on May 27th, 2011 Permalink |
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.
jiehanzheng 3:49 pm on May 27th, 2011 Permalink |
@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.
Zé 8:48 am on May 28th, 2011 Permalink |
It’s now revoked
Gregorovius 9:34 pm on May 28th, 2011 Permalink |
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.
herzcthu 2:28 am on May 29th, 2011 Permalink |
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.
jiehanzheng 3:48 am on May 29th, 2011 Permalink |
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.
Gregorovius 9:04 am on May 29th, 2011 Permalink |
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.