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.
Time to ask for Christmas presents 😉
In WordPress.org you can have the latest version using http://wordpress.org/download/latest.zip. It’s great for automatization in servers, plugins, linking and other stuff. Can we have the same for localized versions? ex. http://es.wordpress.org/download/latest.zip
Thank you!
Didn’t know about the existence of this 🙂
Not sure if this helps, but it’s safer to use Localize if the only reason you need localized builds is to test or update the translation:
http://wordpress.org/extend/plugins/localize/
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.
Hello there.
Zé gave me the idea and I have been thinking in have a localized P2 to the translation community in Spanish. I have tried to create it with the most logical name, but i had this message:
The address es_es.wordpress.com is reserved and cannot be registered.
Do you think it will be a good idea to ask for this locale references to work with translation communities? I mean:
That message is wrong, actually. It should be “Only lowercase letters and numbers allowed”, as on first signup (I’ll relay it to the devs). I’m no apologist of standardizing such blog names on .com for the obvious reasons that the names might already exist and .com doesn’t allow recycling/reassigning them.
I’m also not sure if it’s necessary to have the blog live on .com. Our own (pt_PT) is a network site of the main site, self-installed. That said, everyone is free to do it, of course. Just choose your own name. Whichever solution is centrally implemented (if it is at all) in the future is safe, with the export/import tools, anyway.
What we could debate with @nacin is the possibility of having the option to have a p2 dependent on the main xx.wordpress.org install. Maybe.
Other opinions?
I agree with that the possibility to have a p2 in the main xx.wordpress.org will be good. For newer localizations without much experience or resources, or for communities with translators without tech skill, it can be very useful.
I don’t have a problem adding a network of P2s for translation teams.
Tied in some way to the xx.wordpress.org sites? (trying to preempt management headaches here 🙂 )
This would be a very good idea.
Also, the concept of en_US made me smile 🙂
😛
I like the idea. I am working on something P2 driven on the danish site which I would simply call a teamblog. Wouldn’t team-locale e.g. team-da_DK.wordpress.org or team-pt_BR.wordpress.org work?
But I’m still a little hesitant towards using P2 for the team. As have been noticed in this P2-blog here, there are some disadvantages. Threads get lost or forgotten quickly and don’t get brought up to front when they get new comments.
So I’m also thinking about bbPress and making a Team Forum instead. Especially when bbPress as a plugin merges better with the websites theme. It will get mixed up in the rest of the (support)forums and won’t be a small closed group (or feel like it), but as Zé has pointed out you will be able to mark threads as [Resolved] and you can revive old threads and such.
There is pro and cons for both scenarios. P2 is great for quick, shortlived, in the moment communication while bbPress is better for longer in debt discussions and have some tools for working with threads and topics.
team-da_DK.wordpress.org seems awfully convoluted… maybe da_DK.wordpress.org/team?
If I’m reading your comment correctly, you’d advocate both a P2 *and* a forum? As in a forum separate from the main locale forum? Not sure I like the idea.
As to
you will be able to mark threads as [Resolved]
don’t underestimate @nacin‘s skills of beating a P2 into submission. Enough said 😉
No, I meant that both P2 and a forum had advantages, but I wouldn’t use both at the same time. Just that it’s hard to decide which would work best.
Actually you only need the da-prefix as in da.wordpress.org 🙂
I’m sure @nacin is very focused at making P2 suit our needs.
Zé was hinting at a plugin already written. Stay tuned 🙂
I think sticky posts can easily resolve this problem 🙂
You got a point there.
Disagree. Not optimal at all.
my e-mail comments notifications are now in… any other language I don’t know?
Du kan se alle kommentarer til dette indlæg her:
You’re holding it wrong
Isn’t this making things even more complicated then it needs to be? Why not just create one install with bbPress as suggested earlier (https://wppolyglots.wordpress.com/2011/05/30/is-it-just-me-or-is-this-solution/ and https://wppolyglots.wordpress.com/2011/03/24/i-am-getting-a-bit-concerned-about-how/)? In other words create a bbPress install on .org for polyglots and in this install create team specific sub-forums.
The discussion is not about all polyglots per se, but rather about the discussion within each language.
I get that, still doesn’t see the point. We already got the ability to create local forums, why create yet an other platform? If the point is to organize the individual teams then I stand by my earlier words. To split things up even more is just a bad idea.
Ok, reread and noticed the sub-forums point. Forum vs P2 is the whole point of this discussion, yes.
Here goes my opinion. My problem with sub-forums is that they don’t have a good notifications system (e-mail, jabber…), a very useful thing. With P2 we have a real-time-like system.
Maybe real-time is not neccessary, but it’s very useful when more than 2 people are working in a release.
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 :$
http://translate.wordpress.org/projects/wp/dev/es/default?filters%5Btranslated%5D=no&sort%5Bby%5D=priority&sort%5Bhow%5D=desc&filters%5Bstatus%5D=either
Can you take a look at this?
Thanks 🙂
We are having a similar issue:
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 🙂
Hello there.
In es_ES forums someone has reported that some parts of Jetpack are impossible to translate.
I took a look and, in fact, module descriptions are untranslatable. I have reported it in http://plugins.trac.wordpress.org/ticket/1333
It’s a known issue. Thanks for the ticket.
NP 🙂
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 😀
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 https://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 😛
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).
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 :).
Hello there. There are two spammers in Gravatar→ Spanish (Spain). ¿Can you delete them?
Thanks.
Users ampocac & reagrupamentpaisvalencia
Zé 11:08 am on June 29th, 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 29th, 2012 Permalink |
Done and deploy requested.
Thanks 🙂
Zé 12:26 pm on June 29th, 2012 Permalink |
Deployed
Rafael Poveda - RaveN 12:27 pm on June 29th, 2012 Permalink |
Thanks 😀