Showing 1-6 of 6 unresolved posts
6
GlotPress Trac Core i18n Tickets
Please add Russian to bbPress → International Forums, Theme and Support Plugin.
The forums theme .pot will eventually be uploaded there, right? I still can’t find some strings in the latest wporg.pot from http://codex.wordpress.org/International_WordPress_Forums.
Header codepage is currently broken on http://ru.forums.wordpress.org/
Used to be: http://oi39.tinypic.com/118qe5x.jpg
Now: http://oi41.tinypic.com/10wp27p.jpg
Seems back to normal again. Thanks to whoever fixed it 
@matt with a hat-tip from @otto42. Thanks for the report.
On WP 3.3 ru_RU Credits page, aside from validators, there are some translators who don’t seem to have any approved strings in the final 3.3 release: agvares, cstrife and ivankovalenko. Is that some kind of a caching issue, or is there a valid reason for them to be there?
I am working on the Sanskrit translation, but my name appered on the pt_BR translation credits board. I am a brazilian citizen, and I do speak Brazilian Portuguese, but I do not work with pt_BR team, so it is probably due to an automation problem on the process of crediting translators.
I help the pt_BR translation team and indeed Carlos Eduardo G. Barbosa is not listed as a Validator or Editor under br.wordpress.org, so it must be from some other source.
I would like the opportunity to invite you, Carlos, to work with the Brazilian Team.
Any time, Gabriel.
Just drop me a message at with the team’s basic rules.
My pleasure.
editor at yogaforum dot org – it was bracketed and disapeared from the message above
Hi Carlos, happy 2012.
The Brazilian translators gather at http://groups.google.com/group/wordpress_br?hl=pt-BR and we have some translation directions here: http://wp-brasil.org/traducoes
Sorry about taking so long to comunicate back and welcome aboard.
If I can help you with Sanskrit, not the translation, but building the packages, please let me know.
Thank you for being so nice, Gabriel. You can count on me.
Carlos,
You are listed as a translator, not a validator. This means you have submitted at least one string to pt_BR and that string was approved.
I can find a total of 9 strings you have submitted to pt_BR for WordPress core. One was submitted at 2011-10-25 12:12:28, this one is still current. The other eight were submitted on 2011-12-24; these were approved but later made “old” once the strings were moved from the main wordpress.pot to the wordpress-admin.pot.
Nice to know that Nacin. Thank you for making things clear for me!
For Tamil (Sri Lanka) we have Andrew Nacin on Translators credit. Is that suppose to be that way?
He was on the users list. Removed.
I’ve occasionally added myself as a validator for testing reasons. If you ever see me, you can remove me. Note though I am now automatically excluded from translator and validator lists.
The credits script considers strings “old” or “current” added since the previous release, to be valid strings. So, anyone who added a string after June 5, 2011, and was at some point approved, is considered a translator for 3.3.
This is the same as how core works. Someone may get props for code that ends up getting removed. They still keep their props.
Note that a “waiting” string is not included — the string had to at some point be current/approved in order to be made old.
It looks like all of these strings translated by these three users were made old at the same time on December 13.
Makes sense, thanks for the clarification.
In Rosetta deploy queue for ru_RU, there are many entries I didn’t request. Where could they come from?
I did, however, request the one from 12.07.2011 21:22, due to updated screenshot. Is it possible to deploy it?
12/07 is now deployed. There are two admins on ru.wordpress.org, you and Atrax
Thanks! However the old screenshot is still displayed (the new one is here), even after clearing cache and switching browsers.
There were no commits to Rosetta for a long time, so I doubt Atrax would request deploys several times a week almost every month. Perhaps the requests are made automatically under some circumstances?
Requests cannot be system-generated, no. And the screenshot is now updated.
Thanks, Zé!
The same is true for ro_RO. Btw, we also filled a request.
Can that be deployed? Thanks.
ro_RO was deployed a few days ago and as of right now, there are no changes to deploy
I also see a lot of requests I didn’t made. It’s only me on mk.wordpress.org.
btw I just filled a request for mk_MK. Thanks.
Now deployed and marked as such
There’s a big number of deployment requests that I didn’t make, too. I think they are automated, or event-triggered.
Yep, that’s what I see: http://i52.tinypic.com/14mvp0p.jpg
Of all those requests, only two are mine. It’s not a big deal, but I’m curious if I should cancel the old requests and if that will affect something.
Please remove teleman and a1ex from ru_RU validators for WordPress.
Removed
Thanks!
For Firefox Add-on, it seems that the Russian community has not had a validator. Could I please have the validator right on http://translate.wordpress.com/projects/atd/atd-firefox/ru/default? Also, on the same topic, what are the primary download locations for this add-on and its localized versions, and are translations deployed automatically (I assume they are but wanted to make sure)?
When I try to upload an image on http://ru.wordpress.org/, I get this error:
Unable to create directory /home/rosetta/public_html/wp-content/blogs.dir/15/files/2011/04. Is its parent directory writable by the server?
Is uploading not allowed?
Not at the moment, no. Sorry about that. You can safely link to externally hosted images, however.
OK, thanks.
Do theme names usually remain untranslated? I spot-checked a few other languages, and it seems as though they are not. Also, theme descriptions don’t seem to be translated either, and I am guessing they are lower down on the priority list. So – treat theme names as “product names” and leave them in English, right?
(I am translating WordPress.com into ru_RU at the moment, however thought this question would be relevant to all of the WordPress community, for all themes and all languages.)
Theme names aren’t normally translated, no
Thanks!
I don’t translate names but I do translate other theme and plugins meta information (description, author). Exceptions are my own plugins where I translate everything.
Makes sense, that’s what I’ve been doing as well.
Is it possible to enable Akismet on http://ru.forums.wordpress.org/?
I’m not sure if it’s on or off since I seem to be able to mark posts as spam (and recover them) by hacking post_status manually. However there are no visible links neither for that nor for viewing the spam queue.
The API key for Akismet was wrong. Try now?
I see the links now. Thanks, Zé!
Is it possible to become an admin on ru.wordpress.org? Currently both Atrax and me are editors.
Sure, I’ve made you admin. Is Atrax an admin, too?
Thanks! Yeah, he should be an admin too.
All set
Great, thanks.
Hi, what is the difference between admin and editor? I am not sure what am I on cs.wordpress.org, I did not find it anywhere. Maybe it is the problem I can not set some things on this page?
The same as on a normal WordPress install. The profile should be admin for the coordinators of a locale, not editor. I’ve changed yours.
Great, thank you! Now I can see thing like Pages, Menus, etc. I thougth about changing these parts of web but I did not know where
Don’t go overboard…
Per discussion in #15920, I’ve figured out that in Russian we need 4 plural forms instead of 3 to distinguish a single item from 21, 31, etc. items in certain cases.
I’ve changed the Plural-Forms header in .po files to include the rule for a single item:
"Plural-Forms: nplurals=4; plural=(n==1) ? 0 : (n%10==1 && n%100!=11) ? 1 : ((n%10>=2 && n%10<=4 && (n%100=20)) ? 2 : 3);n"
and it works fine with Poedit. However when I import the translations into GlotPress, there are still only 3 forms. I guess the header is stored elsewhere.
Is it possible to update it in GlotPress both on translate.wordpress.org and translate.wordpress.com?
Should be fixed in http://trac.glotpress.org/changeset/592
Something wrong is going on there.
1. The new header is totally broken. The old one was OK, except that in certain cases we need an additional form for a single item. I’ve provided longer description in comments to #15920:
In Russian a single form is used for every number ending in 1 (except for 11): 1, 21, 31, etc. Standalone single form (as in “Theme enabled”) only makes sense for 1 item. In other cases (21, 31, …) the number should be included in the string (as in “%s theme enabled”), but it’s still single form.
The header I’ve proposed does just that.
2. The GlotPress page for ru locale is not fully loaded, breaking right after .
Perhaps as a long-term solution it’s a good idea to use the header from .po file. If there’s none, then fall back to the default.
…breaking at <p class="plural-numbers">, I meant.
Checking
Reverted the changeset for now. We took the expression from here: http://translate.sourceforge.net/wiki/l10n/pluralforms. Is it not correct?
It’s basically correct, but not sufficient for WordPress. I’ve provided the correct header in my post.
@Sergey, there was an error in the expression, n%100=20 should be n%100==20.
@Zé, in that commit, you didn’t copy/paste the expression properly, and also the nplurals changed to 4. Not that any of that mattered, because of the syntax error in the expression itself
@Sergey, changing the plural forms entails some amount of work. We will need to re-index all translations. Now, index 0 is n%10==1 && n%100!=11, index 1 is n%10>=2 && n%10<=4 && (n%100=20) and 2 is the rest. If we change it, index 0 has to be only 1 and the rest need to shift one index position left. We can automate this and I guess you would like index 0 to be auto-populated with the current value of index 0, right? Can you take care of the conversion yourself? If yes, I can change the plural forms anytime.
Another thing. A change like this will affect all Russian translations on translate.wordpress.org and any other GlotPress installs. Some people may be used to the old plural forms. How badly do you need this change? Are the rest of the Russian translators generally OK with the change?
You’re right, that’s what you get from post-xmas commits. A question for Sergey: wouldn’t the change also have to be applied to Ukrainian, which shares the same plural form?
We’d like to update the navigation links on http://ru.forums.wordpress.org:
Done.
Great, thanks!
Please deploy the translations of WP.org bbPress theme and bbPress trunk on Russian forums.
Done.
Thanks! There are still some things I’d like to figure out:
1. %d days, %d weeks, %d months, etc. are not translated (they are translated in bbPress trunk).
2. Some strings are missing in the latest wporg.pot: All Topics | No Replies | No Tags | Not Resolved. Where can I find them now?
1. looks like a bug,
2. Tose strings should be in rosetta/wporg-bbpress-theme.po, in your locale’s folder
1. Some other strings from bbPress trunk which are not translated:
First name
Last name
Display name as
Trunk is supposed to be at http://svn.automattic.com/bbpress-i18n/ru_RU/trunk/, right?
2. Those strings were gone when I synchronized wporg-bbpress-theme.po with the latest wporg.pot from http://codex.wordpress.org/International_WordPress_Forums.
Some other strings I couldn’t find:
Version
Select the version of WordPress you are using
WordPress version:
Subscribe to Topic
Notify me of followup posts via e-mail
How can I fix this?
To be precise, almost strings on profile edit page aren’t in POT files (see at http://ru.forums.wordpress.org/profile/username/edit where username is you wp.org username).
Any news?
Carlos Eduardo G. Barbosa, 
pavelevap, and 
Andrew Nacin 3:36 am on April 5, 2012 Permalink |
I deleted those three sub-projects, as they were the wrong ones, actually.
Note we are planning to move the i18n forums to the bbPress plugin in the next few months, which is why we are largely in maintenance mode here. That’s just a disclaimer, though. Let’s solve your problem.
The international forums are governed by three different POTs:
There are some strings missing in the wporg.pot which I will get add tomorrow, including the strings you couldn’t find way back in September 2010. Previously there were some technical restrictions, but I just rewrote things so that is no longer a problem — you can have any strings you’d like. (If there are missing strings, report them here as a bug. From tomorrow on out, it’s just a matter of fixing the code to add the right textdomain, etc.)
Also note you will need to request a deploy through Rosetta for these strings, and specify that you want the forums deployed.
Andrew Nacin 3:24 pm on April 5, 2012 Permalink |
The rosetta/forums project is now updated with the latest strings. Please let me know what is still missing.