Hi again!
Zé I don’t know why some strings in pt-BR forum http://br.forums.wordpress.org aren’t translated 
http://img843.imageshack.us/img843/905/forumeg.png
Strings are all ok e.g.:
Thanks for any clue
Tagged: pt_BR Toggle Comment Threads | Keyboard Shortcuts
-
Diana
-
Diana
Howdy,
Please deploy Support Forums for pt_BR, updated some links and strings thoug can’t find support status plugin strings :S…-
Ze Fontainhas
The support plugin isn’t being harvested at the time, sorry about that. Deploying forums in the meantime.
-
Diana
Obrigada Zé!
-
-
Anderson
Hey Zé,
Could you please add user “Dianakc” as an author at br.buddypress.org to create/edit posts?
Obrigado,
Anderson
wp-brasil.org-
duquebilly
Zé, its already done! Thankss
-
-
Diana
Hello there, Zé, could you please set me as validator in Polldaddy and Gravatar pt_BR (translate.wordpress.com), username: Dianakcury
-
Zé
All set
-
Diana K. Cury
Where do I access to create/edit posts?! tried br.buddypress.com/wp-login.php but no access granted.
-
-
-
Cátia Kitahara
Hi Zé, could you please give the user “viniciusmassuchetto” admin permissions at translate.wordpress.org? He’s going to lead the buddypress translation. thanks
-
Zé
Done, but could you take a look at the user list of br.wordpress.org? Feels a little crowded…
-
Cátia Kitahara
Thanks, Zé. i’ve just looked into it. There’re 4 editors, which are me, Anderson, Gabriel and Guilherme. I suppose editors can build packages and make releases, right? So I think it’s ok to keep these ones. And there are 3 validators: Diana, Gabriel and Seu Felipe. Does this validator permission relate to translate.wordpress.org? If so, we can also keep these ones. The rest are just subscribers, may I delete these ones as they can’t do anything at all? But how did they become users? I’ve never added them.
-
Zé
Feel free to remove subscribers, yes. They probably appeared as a result of the merge of permissions, a while back.
-
Cátia Kitahara
done, Zé, thanks a lot
-
-
-
-
-
Diana
Happy New Year Folks!
Two things for today: remove/check an user called “Malluco” from credits and set a new shot for br.wordpress.org, that is quite old. The new one can be found here: http://img32.imageshack.us/img32/3359/shotptbr.png.
Obrigada Zé.-
Gabriel Reguly
Hi Diana,
I have changed the role of ‘Malluco’ from ‘Validator’ to ‘Assinante’, so his name should not appear in the credits of the next version of WordPress.
Regards,
Gabriel-
Diana K. Cury
Oi Gabriel, obrigada.
-
Diana K. Cury
Ah e a imagem! Fiz para o br.wordpress.org: http://img32.imageshack.us/img32/3359/shotptbr.png.
-
Zé
You (or the admin of the site) can upload the screenshot here: http://br.wordpress.org/wp-admin/themes.php?page=custom-header
-
Gabriel Reguly
Thanks Zé for the URL.
Diana, the image is too small (300×200). Ideally the image should be 466 × 303 pixels.
Would you mind generating another one?
-
Diana K. Cury
Ah, here is again: http://img85.imageshack.us/img85/5618/intro2b.png
-
Diana K. Cury
Oops I will create a better one later, hold on please!
-
Diana K. Cury
Oi! Esta está mais legal:
http://img163.imageshack.us/img163/4189/telawp.png -
Gabriel Reguly
Valeu Diana! http://br.wordpress.org/
On a unrelated topic, have you seen this http://jobs.wordpress.net/2011/12/21/set-up-pet-adoption-plugin-and-website/
-
-
-
-
Gabriel Reguly
Malluco is gone, but I see some new users that I am not familiar with:
Augusto da Silva Costa, Caciano Gabriel, erickdeoliveiraleal, jra2, romuloctba, eUrsula (aka WP Gal).
And I welcome Carlos E. G. Barbosa to our Brazilian Comunity.
-
Diana K. Cury
I see. Don’t know who are these folks
-
-
-
-
Cátia Kitahara
Hi guys, as a linux user, I’ve noticed that after the font-family has been changed to sans-serif only, the main menu is breaking when the default language is Brazilian Portuguese. I’ve reopened this ticket. If anybodyelse has experienced this same problem… http://core.trac.wordpress.org/ticket/18020#comment:14
-
Gabriel Reguly
Hi Zé,
I wonder how you managed to release 3.2.1 for pt_PT?
Regards,
Gabriel-
Zé
Are you building from SVN? https://i18n.svn.wordpress.org/pt_BR/tags/3.2.1/messages looks empty.
-
Gabriel Reguly
Oh, sorry. I forgot to say that we build from GlotPress.
I can build the packcage, but the translation files are missing.
This is described here: https://wppolyglots.wordpress.com/2011/07/13/twenty-eleven-losses-translation-after-3-2-1-update/#comment-3597
Regards,
Gabriel-
Gabriel Reguly
Err, package
-
Gabriel Reguly
Que baita burro. Just re-read the instructions to make it from svn, I was so used to GlotPress that forgot the alternative.
Sorry to waste your time Zé,
Gabriel-
Zé
Caipirinhas are on you
-
-
-
-
-
-
Anderson
Please, how can I know which users are actually validators in pt_BR?
-
Zé
duquebilly, Dianakc, FabioFreitas, seufelipe, catiakitahara, webdf and anatman
-
-
Anderson
Hey guys. How can we make bbPress plugin avaiable for translation in pt_BR language at http://translate.wordpress.org/projects/bbpress ?
-
Stas Sușcov
Second the request for ro_RO too please.
-
Zé
Done
-
Stas Sușcov
Thank you.
-
-
-
Zé
Added and you as validator
-
duquebilly
Tks, Zé. =)
-
-
-
Felipe
the main menu in this new version is slightly thinner so the item “settings”, when translated to portuguese “configurações”, doesn’t fit. it feels clunky, you see –> http://d.pr/rYav. is there anything we can do? i mean, it’s an important issue (it’s not like the “save as draft”, which also doesn’t fit), millions of people using an ugly menu everyday :/
-
Cátia Kitahara
Yes, and after almost 3 years of consistent translation I don’t think finding another word is viable, since people are used to it.
-
Zé
We (pt_PT) use “Opções”, instead, but be it as it may, this should probably be submitted as a core ticket.
-
-
herzcthu
Yes, It is ugly. We have very long word translation in burmese for some short english word.
-
Zé
-
-
potbot
Hi, I am a Brazilian user of wordpress.com and would like to become a validator of translation into Brazilian Portuguese. I noticed that some time ago there is no update of translation in our language.
-
Zé
-
Gabriel Reguly
Olá Cristiano,
You are welcome to join http://groups.google.com/group/wordpress_br?hl=pt-BR.
-
-
Cátia Kitahara
Guys,
Something went wrong with the pt_BR version, it seems all of our 3.1.x’s strings aren’t aproved at translate.wordpress.org. Why is that if they were before when we released 3.1? could somebody help us please? Kind of urgent-
Cátia Kitahara
By the way, I reckon there are too many people with aproval privileges, people I don’t even know, I’d rather it would be only me and Diana.
-
Zé
There were no string changes. Can you upload 3.1 to 3.1.1 while we look at it?
-
Cátia Kitahara
I’m doing that, forgot I could, duh!
-
-
-
Gabriel Reguly
Hi,
I am making a build for 3.1, pt-BR
Could someone assure me that my actions are correct?
1. Create a new tag for 3.1 (/i18n/tags/3.1) with the same files from 3.0.5
2. Check on trac for changes from previous version, add/translate the changes and commit the files
3. Make the build with the following options
translations from: translate.wordpress.org
Locale Branch: tags/3.1
Project: Development(Trunk)
WordPress Revision: 17370 – that is where I am not sure <—————————————-
Version: 3.1-
Peter
You should use rev 17487
-
Gabriel Reguly
Thanks Peter.
-
-
-
Cátia Kitahara
me again,
A user reported a problem related to the $wp_default_secret_key at pt_BR.php. This person says that when he updates his sites he can’t access the admin panel and get a message: “You do not have sufficient permissions to access this page.”. Deleting this file fixes the problem. What’s wrong here? The variable value in brazilian portuguese is the same in the wp-config.php file. So I guess it shouldn’t be a problem. could somebody help us, please?-
Milan Dinić
Maybe problem is that he has default keys (as in core en_US version, ie. ‘put your unique phrase here’).
-
Sergey Biryukov
http://core.trac.wordpress.org/ticket/14024
Milan is right about the potential reason, but actually it shouldn’t happen even with the default keys. I guess $wp_default_secret_key should also be translated in wp-includes/default-constants.php.
-
Zé
That is correct. What we (pt) do is just leave it in English. It’s too easy to forget to translate.
-
Mattias Tengblad
So what you’re saying is that if we translate $wp_default_secret_key in wp-config-sample.php and setup-config.php we should also translate $wp_default_secret_key in default-constants.php? If so, where is this documented?
-
Sergey Biryukov
I’ve added a note on Files For Direct Translation.
To be clear, there’s no $wp_default_secret_key in setup-config.php.
When you translate it in default-constants.php, the string in wp-content/languages/<your-locale>.php is actually no longer necessary, however it’s still required to be there in order to build a localized package. So yes, currently it should be translated in all three places (wp-config-sample.php, <your-locale>.php, default-constants.php).
-
Da^MsT
Good to know, should have been pointed out earlier.
-
Cátia Kitahara
Wait, please. Just to clarify things. There are two possible solutions:
1. Don’t translate the variable at wp-config-sample.php and don’t add the locale.php file
2. Translate the variable at wp-config-sample.php and at default-constants.php and add the locale.php?
Both solutions are admissible, is that correct? -
Milan Dinić
If you don’t translate it in locale.php file and you did translate it before, this could affect existing installations.
-
Cátia Kitahara
so my best approach should be translate the default-constants.php from now on?
-
Sergey Biryukov
Yep, until a proper solution is found. Currently it’s more like a workaround.
-
Milan Dinić
I don’t like this. Instead of reducing direct translation and simplification of that, we are adding more files, and complicate already complicated situation.
This is a clear sign of how i18n is getting in worse and worse position, how it is ignored, how there isn’t care to truly fix existing issues and to make improvements.
-
Mattias Tengblad
+1
“Opened 8 months ago” (ticket mentioned above) kind of tells the story.
-
tsjogren
Hi Mattias
This is Torbjörn (Translating BP to Swedish).
I have the same problem reports from swedish users.
1. When does the problem occur? What WP versions?
2. What is the workaround? renaming sv_se.php did help.
3. Is this fixed in future versions (WP 3.1)
Please advice so i can give the users the correct answers.I did a WP 3.0.1 install, upgraded to 3.0.5 and installed BP with no problems…
-
Mattias Tengblad
1. From 3.0 and up
2. Yup renaming or deleting sv_se.php will work. Tell the users to update their secure keys in wp-config manually.
3. Yes, the workaround mentioned above is already applied in trunk (3.1).
-
-
-
-
-
duquebilly is discussing. 
Cátia Kitahara and 
Ze Fontainhas 10:17 pm on November 20, 2012 Permalink |
It looks like the .pot file isn’t current with the code. Investigating but needs @nacin‘s eyes. Hold tight.
Diana 12:07 am on November 25, 2012 Permalink |
Diana 2:35 pm on November 26, 2012 Permalink |
This is not solved yet.