Some new features have been added to WPAndroid, and new strings have arrived with them. Any help translating them is much appreciated:
Recent Updates Toggle Comment Threads | Keyboard Shortcuts
-
Dan
-
Ze Fontainhas
All pending rosetta deploys have been processed. Thank you for your patience.
-
Torsten Landsiedel
I will translate http://de.forums.wordpress.org/ in the next days. Meanwhile, could you have a look at this page, too. There are -518 topics which seems to be a bbpress-problem. Maybe you can start a re-calculation of the topics? And all of the hot topics are spam, I have “destroyed” the tags, but there are still showing up on the front page. Could this be updated, too?
Maybe we could do this with an admin account? Robert could do this for Germany (see: http://wceupolyglots.wordpress.com/2013/10/07/note-to-self-all-whats-up-with-the/comment-page-1/#comment-42)
Thanks in Advance! And it was really great to meet you in Leiden!
-
Remkus de Vries
The recounts currently don’t work. I’ve been looking at that with @otto42 and created a ticket for it.
-
Samuel Wood (Otto)
They actually do work, sometimes. Just not always. I was able to run the recount on that forum to correct the thread count. I’ll look into the specific other problems.
-
Torsten Landsiedel
Thank you @otto42 and @defries! Count is fine now.
-
-
-
-
Ze Fontainhas
Heads-up for those not attending WordCamp Europe: as a part of the Contributor Day, the polyglots that did attend are sitting together and working on a few things. If you want to follow along or even participate, please visit http://wceupolyglots.wordpress.com/. If you need access to comment, request that here. indicating your WordPress.COM (not .org) user name.
-
Ruben Woudsma
My remark on the page is awaiting moderation, but I am not actively contributing in Leiden.
-
Birgit Olzem
Hello Ze, please look at this http://wceupolyglots.wordpress.com/2013/10/07/note-to-self-all-whats-up-with-the/comment-page-1/#comment-45 to accept my request to comment
-
-
-
Charles Frees-Melvin
It would be great if we could edit the readme.html from within rosetta possibly with a short code that auto inserts the version and the wp-config-sample.php from strings in GlotPress and have the compiler script automatically pull them and make those files. It would allow more rapid push out of new releases/updates without the need for tagging the new version in SVN. In theory, if the version number gets auto filled in the readme.html with this method, it would also allow the core admins to push all the translations too for a security release if there are no changed strings.
-
Andrew Nacin
Definitely something we’ve talked about before. There are a number of potential issues. A lot of installs have their own readme.html file, with the actual filename translated as well. Thus it would ship next to the American English readme.html. We could encourage this for all languages, but then we’d have a conflict for non-American English translations. Or we could discourage this, thus readme.html would always reflect the local language. But when you start dealing with updates, versus just a standard download package, things get a bit messy.
When using an American English install, WordPress currently downloads only changed files when updating to a minor release. Since we know which files changed and we know that no strings changed, it’s entirely fine to do so. We’re nearing the point of “language packs” that would update po and mo files separately. Unfortunately, this readme.html file remains a thorn, especially with the version number. It’s not a big deal if the translated readme says “3.5″ but the actual install is 3.5.1. But, if a translator is simply replacing readme.html, then we’re going to stomp on their changes. Now, I don’t necessarily mind this as users aren’t relying on their readme once they are installed (or at all — it’s a bit of an anachronism). It’s also no different from when a user opts to update to WordPress in English before a zip is ready.
Oh, and some include a translation of the license file, too.
I think we’re at the point where, at the very least, Rosetta can replace a placeholder for you inside readme.html. Then you could just always take the trunk or branch dist files which will have nothing more than a readme.html and wp-config-sample.php. Over time I’m very happy to see newer tools here.
-
-
Andrew Nacin
Strings for WordPress 3.7
Hello, all. I want to explain what was going on with 3.7. After we rearranged our code repositories for WordPress core, our tools that generate and import strings needed to be adjusted. At the time I also knew that a 3.6.1 security release was being prepared, so we moved the “Development” project to “3.6.x” to make sure all 3.6 and 3.6.1 releases went smoothly.
GlotPress is not yet good at “branching,” so after I move “3.6.x” back to “Development” and create an empty “3.6.x”, I have a script that handles exporting and importing all translations. Once that happens, I can then update the original strings in the “Development” branch to reflect 3.7. If I were to just create an empty “3.6.x” and let you do the export from “Development” and import into “3.6.x”, your exports will be incomplete because the originals changed, and that’s no fun, and it makes it much harder for you to release security releases.
(Note: This isn’t a complaint about GlotPress. I’ve had conversations with @markoheijnen about how a few adjustments can make GlotPress better for us, and I’m excited.)
I cited 3.7 repository changes as the catalyst, but we’ve actually done this shuffling previously. No one noticed until now because this release cycle is so short. But, I’ll argue that this “shuffle” is actually a good thing. Otherwise, what happens is a few strings change per week during early “alpha” development, and translators jump all over those. But in reality, those strings are still in flux, which means you’re just doing extra work because GlotPress presented you with a string that we might change in a few days. That’s no fun for anyone, and it makes me feel really bad, because your time is valuable. Waiting a few weeks before we start to populate strings into “Development” is actually ideal.
Okay, what about string freeze?
You may have also noticed that 3.7 was a very “low-level” release. It primarily focused on bug fixes, code improvements, and updates. There were no major user-facing features or UI changes, which also meant there were very few strings. there are only around 76 strings new in 3.7. I imported the new strings less than two hours ago, and then I went through each of them to confirm there were no typos or changes to make. The crazy thing is in two hours, two translators are already almost done! (Props @damst and @SteveAgl.) That just goes to show how easy and quick it will be to update your translations for WordPress 3.7.
It also showed how quickly new strings are translated. As I said, I want to make sure you feel your time is valued. So: let’s consider this point to be a “string freeze” with a qualifier. The 76 strings have been double-checked and are ready to go, and you should start translating them today. The qualifier: There will be some new strings that get added over the next week. First, we’re still polishing a few things. Second, there is also the about page, which I promise you’ll have a week to translate. We’re planning to launch 3.7 the week of October 14, so expect to hear more next week.
What about language packs?
The general concept of “language packs” are new in 3.7. But, a lot of the processes for how WordPress.org will be handling those is still not settled (more to come here). However, If you’re looking for something to do, may I suggest you make sure your translations for the WordPress importer plugins are up to date? Upon 3.7′s launch, any 100% translations for these plugins will be delivered to WordPress sites during updates. The same goes for bbPress, BuddyPress, and default themes, too.
While after reading this you may come to your own conclusion, I promise there was no conspiracy, negligence, or incompetence to keep you all from translating 3.7.
Finally: If you’re at WordCamp Europe this weekend, please come find me to chat! I want to hear your thoughts and ideas.
Happy translating!
-
Xavier Borderie
Always the thorough post, Andrew. Thanks a lot!
-
fernandot
No problem Andrew, we’re going on it asap
-
Mattias Tengblad
Thank you for the much needed information!
-
Stefano Aglietti
Thanks for the explanation, and yes cause the future short release cycle the translation systems should be triggered to allow us to have new version available at beta (during alpha and development i can understand that strings chamnge etc) where we can stand some strings changes, if you dev will be able to string freeze on RC1 this would be nice. As italian translator and validator since 2005 i always tried to keep the it_IT version uptodate. Unfortunatly cause we are “italians” the collaboration form others people often lack but i hope to have for plugins etc some validators or at least some not occasionally contributors to help us to deliver translation up to date to coming versions for all the project active.
-
Nashwan Doaqan
Thank you
-
fernandot
All new strings done for es_ES
-
egalego
All new strings done for Galician, gl_ES
-
Kazama
how to report the wrong string?
References: wp-admin/options-permalink.php:179
number of tags are available-
Marko Heijnen
http://core.trac.wordpress.org. Curious what is wrong with the string.
-
Kazama
this string is about how to setup permalink but the anchor text for the link is “number of tags are available”. It should be “Documentation on Permalinks”
-
-
-
Mushviq Abdulla
Dear Andrew Nacin! I have plenty of faults found me a pre-Azerbaijan language translations. He made errors. However, interpretation of these errors remains. How do I get an Error delete He barge quotations?
-
Marko Heijnen
I don’t know what kind of errors you exactly mean. I’m happy to help if you still having them.
-
-
Birgit Olzem
@nacin I didn´t found a german -> formal tree for the importer plugins
-
Birgit Olzem
All new strings done for 3.7 in german and german->formal
-
-
Mattias Tengblad
Heads up all. Trunk is upp to date again.
-
Nashwan Doaqan
“Happy translating!” — Andrew Nacin
-
-
Wacław Jacek
Could you please remove the form field autofocus from the contact pages? I’d like for people to read the entire page before they submit the contact form, and having it focus the field, Chrome automatically scrolls down to it.
-
Isaac Keyet
Validation request! There are a few languages in the WP for iOS and Android projects that are waiting for a validator to take a look.
iOS
Finnish, Tamil, Slovak, Irish, Arabic, Persian, and Greek all also have pending strings but are at a low overall translation level. Help needed!
Android
- Italian (55)
- Chinese (China) (5)
- Chinese (Taiwan) (34)
- Japanese (24)
- Hungarian (45)
- Russian (179)
- French (103)
- Polish (106)
Georgian, Slovenian, Slovak, Finnish, Norwegian (Bokmål), Bulgarian, Czech, Arabic, Persian, Burmese, Uzbek, Azerbaijani, and Mongolian too have pending strings (some have lots!) but are far from a 100% overall. More translation help needed.
-
Naoko Takano
Moderated Android in Japanese & added some more translations. Thanks!
-
Naoko Takano
@isaackeyet I’m almost done but need a bit more clarifications. Could you elaborate on these?
http://translate.wordpress.org/projects/android/dev/ja/default?filtersstatus=untranslated&sortby=priority&sorthow=desc-
Isaac Keyet
Only the untranslated ones? I struggled with those too. I’ll ping some people, then report here, then update the string descriptions in the project.
-
Naoko Takano
Thanks, yeah I meant to send this URL: http://translate.wordpress.org/projects/android/dev/ja/default?filtersstatus=untranslated&sortby=priority&sorthow=desc
if you guys could provide clearer descriptions for the untranslated strings that would be great!-
Isaac Keyet
Okay so we’re trying to add comments for the future, but here’s the explanation:
includes %sPublicizeThis is from the Stats section and refers to “follower” stats, an example would be “10 followers (includes Publicize)”. The variable in the string is used to add a link so the word Publicize is actually tappable.
Custom DateThis is from the media library browser and is one of the filtering options, the other being “All”, “Images”, “Unattached”, “Custom Date” — so it really just means “filter by date” if that helps.
Kudos to @mbiais for the above!
-
-
-
-
-
vestimir
I’ll try to help with the Bulgarian translation. Can you add Bulgarian translation for the iOS project?
-
Isaac Keyet
That’d be great! We’re just trying to get the translations as close to core WP as possible and only make exceptions where it’s absolutely needed due to width constraints.
I’ll see if we can add Bulgarian to iOS shortly, we just want to make sure we keep as many languages at 100% at all times otherwise it’s (of course) not a very good experience.
-
Kenan Dervisevic
@isaackeyet Is it possible to publish a localization in a language that isn’t supported by iPhone and Apple? If so, I would gladly help in making WP for iOS available in my language (Bosnian) too.
-
Isaac Keyet
Unfortunately not, and it looks like neither Bulgarian nor Bosnian are currently supported by Apple unfortunately
Sorry guys! If you keep translating at least we’ll be ready once they enable it, but since there’s a lot of upkeep maybe best to simply hold off.-
Kenan Dervisevic
According to this http://stackoverflow.com/a/13360348 there is a language identifier in the code for both languages, but Apple decided not to support them. Maybe they will offer support in some future version.
-
-
-
vestimir
Hey, I am ready to submit translations. I downloaded a PO-file from the translation site. How do I import it back? Do I have to clone a repo or something?
-
vestimir
@isaackeyet can you direct me to the validator for the Bulgarian translation, so I can send him a PO file with the translations I made?
-
Petya Raykovska
I’m gonna talk to Mario and Nikolay and take care of projects for WordPress for iOS and Android to be set up shortly, Vesti. And I will take care of the Android project translation.
-
vestimir
10x Petya. I spoke with Ze and he pointed me to make a validator request, so I posted one yesterday here.
-
-
-
-
-
Nashwan Doaqan
Arabic on progress…
-
shooh
Hello @isaackeyet
We need help with “RTL issue” in Uzbek translation, please: http://android.trac.wordpress.org/ticket/516-
Isaac Keyet
To respond to your comment on that trac ticket a validator would be the one approving suggested strings. You should seek out the Uzbek translation community to see if you can get help with that (not a bad idea to stay in sync with them anyway).
-
-
SeriousOwl
I can help with Indonesian
-
Isaac Keyet
That’s great! The iOS and Android projects are already 100%, but with each update of course additional help is needed for new/updated strings. You can also look into the Windows Phone and BlackBerry projects (also in GlotPress).
-
-
Isaac Keyet
@vanillalounge, can we get Maxime Biais added to Polyglots? His username is “mbiais” and he’ll be helping us on the French side moving forward.
-
Ze Fontainhas
Invite sent.
-
Isaac Keyet
Thank you.
-
-
-
Ze Fontainhas
@nacin, a heads-up: I’ve created http://translate.wordpress.org/projects/wp/dev by hand and imported originals from trunk. Could you (or someone) make the potbot aware of this, as http://i18n.svn.wordpress.org/pot/trunk/ isn’t current at all.
I apologize if this is stepping on anything else, but we can’t really have a 3.7b out without a /dev or an explanation for why it’s not there.
Thanks
-
Ze Fontainhas
Same goes for bbPress 2.4.x
-
Marko Heijnen
Awesome. Thanks for doing this.
-
Nashwan Doaqan
You are the man! Thanks
-
Nashwan Doaqan
But Ze .. The translations of the new branches are wiped! We need to Export/Import the translations and this will clear all the translators names and other meta data!
Is there a way to Export/Import with ability to save the translators names?! see
http://translate.wordpress.org/projects/wp/dev
http://translate.wordpress.org/projects/bbpress/2.4.x-
Ze Fontainhas
Please mind your wording: how can they be “wiped” if they were never there to begin with? The procedure is still the same as it always was: export the strings (as a .po for instance) from the version immediately before and import them to the new project. (the WordPress project itself might not need that).
-
Nashwan Doaqan
Sorry, I was thinking that the admin procedure is:
1- Rename the ‘Development’ branch to the version number.
2- Create a new ‘Development’ branch with the strings in the trunk.So the validators will not need to Export/Import the translations every time a new version is published.. anyway thank you for your clarifications
-
-
-
Andrew Nacin
After talking with Zé, I’m undoing this — will be recreating it in a few hours with the right strings and copied translations. Thanks for your patience!
-
Stefano Aglietti
after 2 days the 3.7 is not up yet, we are close to the programmed release (October 14th) and we do not know ho much work should be done and how language packs will works. I can’t understand why immediatly after the starts of development for 3.7 the project wan’t created. I hope the 3.7 branch will be available soon and i think my thoughs are the same of lot of we translators.
-
Mattias Tengblad
I agree. Moreover, it seems that the previously agreed on string freeze period is ignored.
-
Xavier Borderie
I think the initial schedule is not to be taken as-is anymore.
The initial release date was Oct 14 with a beta 1 on Sept 16 and RC 1 on Sept 30.
In reality, beta 1 was released on Sept 28th. Andrew wanted beta 2 to happen early this week (it’s not there yet), and the RC 1 this Friday (we’ll see).
WordCamp Europe happens this weekend, and Andrew is planning on using the contributor day to boost the release day, so we might get back on track with the schedule. In any case, I’m pretty sure we’ll get our wishes granted at WC Europe
Besides, I think the string freeze usually happens on RC1, so…
-
Mattias Tengblad
Correct, RC1 = String freeze. Supposed to be 14 days. Planning as of nacins post, string freeze would have been less than 1 week (at an already shortened time frame, where we have not been able to translate a single string yet).
The primary headache here is the lack communication.
-
-
-
pavelevap
Dev is now active, but there are 1771 (should be 1746) strings and it is copy of 3.6. There are no new strings for 3.7.
-
Mattias Tengblad
The latest POT seems to be form “2013-08-01 15:13:03+00:00″
-
-
-
Gabriel Reguly
Thanks Zé for taking action and thanks Nacin for making it right.
And a happy WordCamp Europe for both!
-
-
Mattias Tengblad
3.7 beta 1 released…project? pots?
-
Ze Fontainhas
-
Mattias Tengblad
Thank you Ze!
-
-
-
Nashwan Doaqan
bbPress 2.4 has been released! please update the page:
-
dyrer
Congratulations.
There is no Greek language to translate-
dyrer
Thanks for Greek (polytonic) but today in Greece (Hellas) we are not writing polytonic anymore except when we use ancient or byzantine.
Please add simple Greek -
Nashwan Doaqan
@dyrer What you are talking about ?!!
-
dyrer
I saw Greek (polytonic) in strings.
please add Greek in bbPress dev
-
-
-
Nashwan Doaqan
@Ze Fontainhas I miss you
-
Kazama
I think automattic should hire someone to take care us.
-
-
Ze Fontainhas
-
-
Dan
WordPress for Android has a big update coming and a lot of strings have been added. We’d appreciate any help getting as many translations updated as possible!
-
Kazama
Thai is ready
-
Isaac Keyet
Swedish is pretty much there.
-
Mushviq Abdulla
Dear Dan! Please add azerbaijani language. I’ll translate it.
-
Dan
Sure, here you go: http://translate.wordpress.org/projects/android/dev/az/default
-
-
-
drssay
Please, Open translation project wordcamp base theme for ko_KR ( http://translate.wordpress.org/projects/wordcamp-theme/ko/default )
-
cubells
And Catalan, please.
-
egalego
and Galician, please
-
Kazama
I’ve translated all strings for Thai since last year, but I have no idea how to use it.
-
Ze Fontainhas
All added. When the WPF sets up the theme for your WordCamp, they should be able to choose to set it to one of the languages available.
-
-
Andrew Nacin
WordPress 3.6.1 has been released. This is a security release and there are no string changes. Please push new releases ASAP, thanks.
Edit: Assuming you are building from translate.wordpress.org, please use revision 25318 and the “3.6 and 3.6.x” project. This is the version for core.svn.wordpress.org (not the revision you find on Trac, which is develop.svn.wordpress.org). I’ll try to make this much better in the near future, as yes, it is confusing.
-
Sergey Biryukov
ru_RU is done.
-
Milan Dinić
Just noticed that pots aren’t updated since change in SVN directory structure. See https://i18n.trac.wordpress.org/browser/pot
-
fernandot
Done for es_ES
-
egalego
Galician , gl_ES is done
-
DjZoNe
hu_HU is out
-
Kazama
What is the DB version of 3.6.1?
-
Kazama
I used 24448. If it correct, then th is out.
-
Sergey Biryukov
DB version is not the same as the revision number.
It looks like you used revision 24448 to build the package, and that resulted in 3.6-beta3-24432.
You should use revision 25361 instead: core.trac.wordpress.org/changeset/25361.
-
Sergey Biryukov
Disregard, see Nacin’s comment below.
-
Kazama
Thanks for your help, Sergey.
-
-
-
-
-
Andrew Nacin
Assuming you are building from translate.wordpress.org, please use revision 25318 and the “3.6 and 3.6.x” project.
-
Kazama
Thank you Nacin.
-
-
drssay
ko_KR is done!
-
Remkus de Vries
nl_NL is done too
-
Birgit Olzem
de_DE is done!
-
Xavier Borderie
fr_FR is up!
-
WordPress Türkiye
tr_TR is done
-
Kenan Dervisevic
bs_BA is up!
-
Kirin Lin
zh_TW is released!
-
Rami Yushuvaev
he_IL is up!
-
Stefano Aglietti
it_IT was realesed
-
-
Isaac Keyet
We could use your help translating a few new strings in the upcoming WordPress for iOS release. For the major languages there are currently only 14 new pending strings so it shouldn’t be too much work. Here’s the link: http://translate.wordpress.org/projects/ios/dev
We’re specifically looking for help translating the remaining bits of the app into Korean, Thai, Chinese, Russian, Norwegian, and Indonesian.
-
Kazama
Thai is ready
-
bhkyung
korean is ready, too
-
Isaac Keyet
Great, those strings need approving though.
-
drssay
All string is approved!!
-
-
-
Isaac Keyet
Nice!
-
-
Birgit Olzem
German ready
-
Isaac Keyet
That’s great!
-
Pascale
There are some typos in the German translation: (enthält ein ungültigen Ausdrück – should be: enthält einen ungültigen Ausdruck etc.)
I’ll suggest some new translations there.
-
-
Remkus de Vries
nl_NL is ready too.
-
Isaac Keyet
Dank u wel!
-
-
kukac7
Hungarian done.
-
Isaac Keyet
Awesome!
-
-
Xavier Borderie
fr_FR is up to date!
-
Isaac Keyet
That’s great news!
-
-
LuigivdB, 
mbootsman 6:16 am on October 9, 2013 Permalink | Log in to Reply
Oh, nice! I finished translating the Android app on #wceu Contributor Day, but hey, no worries
Maxime 8:47 am on October 9, 2013 Permalink | Log in to Reply
I’ve finished translating for French with the new strings. I had to read the code source for some string to get context. If anyone needs help for this, ping me.
Validation needed
LuigivdB 4:48 pm on October 9, 2013 Permalink | Log in to Reply
Just finished some translating for the dutch one!