Hello there.
We need a change in this contact page: http://es.wordpress.org/contact/
“foros WordPress en español (no oficial)” needs to change to “fofos oficiales de WordPress en español” and link to es.forums.wordpress.org.
Thanks.
Hello there.
We need a change in this contact page: http://es.wordpress.org/contact/
“foros WordPress en español (no oficial)” needs to change to “fofos oficiales de WordPress en español” and link to es.forums.wordpress.org.
Thanks.
Hello there.
We have right now 1355 threads with 3337 messages in es_ES forums, but they are unsearchable. Right now, if you are in your locale forum and tries a search, you are redirected to wordpress.org/support/-only results.
Is it possible to set up the search to allow the users search in WP.org forums, locale forum, or both?
Not exactly “you are redirected to wordpress.org/support/-only results”, as they are pulled from *all* forums (try searching for a spanish-only term, like “pestaña”), but you have a point with limiting or prioritizing the search to locale forum first.
I didn’t realize about that because almost everything that you search (and I have tried) are common terms.
With this in mind and testing again, you can get a locale search using something like:
allowed memory size "es.forums.wordpress.org"
If you don’t use the quotes it doesn’t work.
Maybe we can add a checkbox to add %22LOCALE.forums.wordpress.org%22 to the search string if checked, and get something like
http://wordpress.org/search/%22es.forums.wordpress.org%22+Allowed+memory+size?forums=1
This ánd the fact that finding the Search option to begin with seems to be too difficult for most users.
I suppose bbPress 2.0 will solve most of these issues as well?
There’s also an issue with Cyrillic topics — none of them can be found via Google:
http://core.trac.wordpress.org/ticket/19011
Hello there.
I have created branches/3.3 in SVN and I’m using it to create the release.
I have used SVN files (I have uploaded all the .po/.mo files) and dist/ in translate.wordpress.org with the same result: wp-versions.php sais that we are in 3.3-aorctic-dissection, and the update doesn’t work.
Can you bring some light about what to do?
Thank you.
Can you post a screenshot of the settings you’re using to build?
I think I found the problem.
Revision 18439 was being used. Now using HEAD.
Newbie stuff at 3am >_<
Solved.
We have a missing string in http://translate.wordpress.org/projects/wp/dev
It says we have 1 string untranslated, but I cannot find it :$
Can you take a look at this?
Thanks
We are having a similar issue:
http://wppolyglots.wordpress.com/2011/06/17/re-count-fix-needed-for-wordpress-chinese-china/
If it’s no problem for the translation, then it’s OK!
Thanks
No problem.
Tip: you may want to export the .po file, then open it in programs like poEdit. You will then be able to figure out those untranslated, and you will be able to either translate them directly in poEdit then import your updated .po file, or search for the untranslated strings shown in poEdit to locate and translate them in GlotPress.
Thanks again
Hi there.
We have an issue in credits page (http://es.wordpress.org/wp-admin/credits.php). é appears as é, so there are two names wrong: José and Zé.
Can you take a look at the charset?
Thanks
duplicate. has-patch. wontfix ![]()
http://wppolyglots.wordpress.com/2011/06/08/ze-is-it-just-damst-me-who-has/
Thanks. Answering in the ticket.
Also, what is my name doing in your translation credits?
I suppose you have translated any string?
Be afraid
Hello there.
Is it possible to include Jetpack in translate.wordpress.org? In WP 3.1.2 and WP 3.2 we have Jetpack in English. In 3.1 installation it was in Spanish, and we want it in Spanish again
Not sure I follow. Jetpack is on GlotPress for .com as per http://wppolyglots.wordpress.com/2011/03/10/will-jetpacjk-be-added-to-wp-project-if/#comment-1550
Wakatta. Can you add me as a validator? username bioxid (with o, not zero) in .com. The inclusion of the translate in jetpack plugin is automatic, or we need to do something? It is almost completely translated and it appears completely in english in our installations.
Validator permissions added.
As to the inclusion of strings, it is up to the Jetpack developers to decide what to include in a release (it’s not automatically “deployed” to their svn repo), but they usually include all locales that are 100% translated.
This means that if es is at 100%, the next release will include it. For now, the solution is to download the .po/.mo and place those in your Jetpack languages folder.
Understood. Thanks for everything
And untill this happens, where do we find the .po/.mo files for the ES translation?
http://translate.wordpress.com/projects/jetpack/1.3/es/default/export-translations. Replace “1.3″ with the version you need, see http://translate.wordpress.com/projects/jetpack/ for available versions.
What’s “Wakatta”?!?
“Understood” in japanese. Language confussion, I was reading some japo things. ごめんえ
You need to get out more…
jajajaja I was there
Otto gave me a heads up that some download packages aren’t being packaged against the 3.1.1 tag, but rather the 3.1 branch. This is resulting in the es_ES download actually being version 3.1.2-alpha. I imagine this affects multiple locales.
This is not good. While our branches are always going to be quite stable, as we’re very cognizant of them being run in production, it’s a huge issue for users, as it causes confusion and perception problems.
Please test your builds. I’m not familiar enough with the deployment system to know where things went wrong (or if it was a systems error, rather than human error) or how to fix it, but I imagine Zé can provide some further direction.
This is when glotpress is used as the base for translations creating packages.
I had the same issue with the nl_NL where Rosetta at first didn’t pick up the proper tag, as discussed here but 30 minutes later it all worked perfectly.
Yes, I figured that was the issue. I imagined that Rosetta was similar to our own release deployment system, such that it allows you to specify trunk, branch, or tag, as well as a revision. We should probably just restrict packaging to tags and HEAD.
Yea, that sounds like a plan. Will that still allow us to build betas and RC’s?
Those are either in a tag or trunk (HEAD), so, yes.
You’d no longer be able to build development packages for point releases, but we typically don’t even announce those. I’ll add this to my list.
Point releases don’t usually bring new translatable strings so that fine.
Mostly, but I wouldn’t bet on this
True, but none to the extend that it would valid the need for RC testing imo.
There was no system error that I can pinpoint. I’d also alert to the fact that ‘create a new tag/branch in svn > bulid > release’ in one go can also lead to this kind of error, i.e. the newly created tag/branch won’t appear immediately in the locale site, which makes it too easy to choose the wrong one. Hence I’d recommend creating the tag ahead of time. I also agree with excluding branches (both core and locale) from build options.
Thanks a lot Zé. Is this the tag that’s created by us as part of our release process?
Are you able to force a new 3.1.1-es_ES build off the tag?
Yes. They’ll need to delete the current build and release and start over. Then warn users (on the es.wordpress.org blog, I suppose) that they’ll need to reinstall 3.1.1
Which reminds me that having a way to push messages to .org dashboards from the locale .org site would be a nice feature for the next iteration.
Use case? I don’t really see one here. We can’t even force messages yet, though we’re aiming to have that working soon.
Unlike core, strings can have updates/corrections within the same release. It’d be nice to be able to point them to the updated language files, for instance.
Hmm. Interesting. If all goes well, I’d love to see language pack versioning completely supersede the need for that.
Cool. To the es_ES maintainer(s), I’d personally prefer that any post simply emphasizes that the 3.1.2-alpha build is stable, so they can continue to simply use that, rather than do a pointless re-install. (Of course, let them know that they can do that if they wish.) It’d be good to acknowledge the mistake, but it didn’t cause an actual issue, just contributed to confusion and uncertainty. It’s trust and confusion that needs repairing, not actual sites.
Which is exactly what we did for pt_PT when 3.0.5 was released as 3.1-RC4, but we still rebuilt and rereleased.
Well I’ll be dammed. A few of us examined logs and the API code tried our hardest to figure out why the heck some people were getting upgraded to 3.1. Turns out that’s what they were being given!
Also, some people like to live dangerously…
Not typically by accident, though.
And what I did when I released the 3.1.2-alpha ..
Is this the tag that’s created by us as part of our release process?
It’s both, actually (core and locale)
I think the best would be to somehow inform everyone on new release, about the SVN revision they have to use when compiling the package. Me, for example can’t see the tags/branches since we do not use the SVN (except for dist/).
http://i.imgur.com/5H1qX.png
And yes, the best is to recompile the package with the correct revision.
They can also use my localize plugin to switch back to any version.
When I mentioned the tags/branches not showing up, I meant the dropdown used to build from rosetta, independently of the fact that you’d be building from svn or GP. The revision idea is good, though.
Link to the plugin?
If the revision idea is acceptable, than, first who sees the release and can blog here, can post the update. I can also do this in future.
The plugin was already posted once here, it can be used to switch to any language from GP.
http://wordpress.org/extend/plugins/localize/
Thanks for the link and also for volunteering to monitor the revision
Sorry about that. The version 3.1.2-alpha in translate was corrected to 3.1.1 April the 11th.
The person who release the version did it without creating SVN, so there was a problem with versions, translations and all this stuff.
We are now writing a how to release a localized WP version and will be in codex very soon. We think it’s neccessary, because the proccess is not clear.
So sorry for not answering before.
Hi Rafael,
“We are now writing a how to release a localized WP version and will be in codex very soon. We think it’s neccessary, because the proccess is not clear.”
Very soon now?
It’s in my to-do list!
I hope to have some free time next week to do this.
Hi!, when http://videopress.com in other languages?
Am I to understand that you are volunteering to translate to es?
jajaja I can help too
Count with my axe!
Hehehehe that’s it!
Hello there.
We have no official forums for WP.org in Spanish. It will be good to have one. As a forum support, it’s valid for the entire Spanish community, with all its localizations, so we think it’s very interesting.
Is it possible to get one?
Thanks in advance.
Well, at last
Done.
http://es.forums.wordpress.org , of course. Don’t forget http://codex.wordpress.org/International_WordPress_Forums
Working on it
thanks.
Almost done. Subforums created and finishing with .po files to upload.
I have a problem with recount. Is there any way to do a recount in the forum? Any URL not linked inside?
Thanks
All the archives are up and ready.
We are in your hands now
Translations, you mean?
Yes, he mean it
BTW all links (Showcase, Extend, …. Downloads) goest to 404 (they don’t exist).
Hi there,
could it be possible to make some changes in the spanish showcase’s theme? http://es.wordpress.org
Here’s the point. The theme only displays three random themes, and the only way to see them all is reloading the page. As they are random, your theme can appear in all, any or none of the reloads.
It would be very useful to have a showcase page like this:
http://wordpress.org/showcase/
Thanks!
patches welcome?
Great!, I would like to help improving it. Just let me know what is the next step
Hello there.
We have some problems with 3.1 compilation in es.wordpress.org. tags/3.1 doesn’t exist.
Can anyone look at it?
Thanks
tags/3.1 for WordPress does exist and is visible in the dropdown.
tags/3.1 for es_ES doesn’t exist and thus is not visible in the dropdown.
How can we compile 3.1 translation then? Any help?
Thanks.
Nevermind. Compilation is waiting. Thanks.
Rafael, you can use Subversion instead of translate.wordpress.org, but you’ll have to upload translated files to Automattic’s svn. We used that before Glotpress was created.
Thanks again. Working on it
.
HI there Zé,
Is there any WordPress / WordPress for Android validators?
I see waiting translations not being approved.
Regards
Hi there! I’m posting this here again as i don’t have response from the es_ES translation team
I have found a bug in setup-config.php for the official spansih version 3.0.1-es_ES
http://svn.automattic.com/wordpress-i18n/es_ES/trunk/dist/wp-admin/setup-config.php
setup-config.php and wp-config-sample.php doesn’t have the same connection strings so the install process fails to connect to database as resulting wp-config.php connection strings are not replaced.
I have the diff file ready to patch the SVN file
Thanks!
Please create a ticket in the core trac – http://core.trac.wordpress.org and attach your patch there and then provide a link to the ticket from here.
Ok, i have created the ticket on the TRAC, and attached the DIFF, this is the link
https://core.trac.wordpress.org/ticket/15429
Thanks!
Thank you!
Hi there! I have found a bug in setup-config.php for the official spansih version 3.0.1-es_ES, setup-config.php and wp-config-sample.php doesn’t have the same connection strings so the install process fails to connect to database as resulting wp-config.php connection strings are not replaced.
Sorry about the tags, i forgot the ,
Fixed
I have the corrected file, how can i send the patch so SVN?
Zé 11:08 am on June 29, 2012 Permalink |
As discussed over Skype, http://translate.wordpress.org/projects/rosetta/es/default looks mostly untranslated, which means that es.wordpress.org is using an old (manual) .po/.mo and that what’s on GP has never been deployed. You’ll need to either upload the old .po to GP or translate Rosetta again and request a deploy.
Rafael Poveda - RaveN 12:01 pm on June 29, 2012 Permalink |
Done and deploy requested.
Thanks
Zé 12:26 pm on June 29, 2012 Permalink |
Deployed
Rafael Poveda - RaveN 12:27 pm on June 29, 2012 Permalink |
Thanks