Showing 1-8 of 8 unresolved posts
8
GlotPress Trac Core i18n Tickets
We added four final strings to WordPress 3.7. All of them are used to communicate update failures to users. So while they should never be used, when they are needed, it’s super important for them to be accurate.
Thanks for your understanding! At this point, we’re done with 3.7. Expect a release in the next 18-36 hours.
Hi @Ze and @nacin,
I can´t create a RC Build in Rosetta for de_DE to test it.
My workflow:
1. add all dependent files into svn at /tags/3.7/dist (liesmich.html & wp-config.php)
2. commit changes to svn
3. go to rosetta
Build a new packet:
I get following error message:
Fehler beim Kopieren von /tmp/rosettaVtIemt/de_DE/dist/liesmich.html zu /tmp/rosetta4vXl9F/wordpress!
What can I do to fix this problem?
Best regards,
Birgit
@tenpura just help me few days ago about this problem
for Locale branch:
you must use the folder “trunk” not “tags/3.7″
for Revision:
Please check here http://core.svn.wordress.org/
right now it is “25775″
hope you can solve this problem
@kazama you made my day! Thanks to @tenpura too 
Memo to me: check always the revision number on http://core.svn.wordpress.org before building a package 
I think if it is the normal build (not from trunk at svn) we should check here http://core.trac.wordpress.org/browser/tags but I’m not sure about it.
Testing the Japanese version on my local machine and the automatic update from Beta2 to RC1 works fine except:
1. $wp_local_package in wp-includes/version.php is removed after the update.
2. Translations is not updated.
Step to reproduce:
1. Install WordPress 3.7 beta 2 Japanese version on your local machine.
2. After a while it is automatically updated to RC1.
3. Look into wp-includes/version.php, you will find wp_local_package is gone.
4. Look into wp-content/languages/ja.po and you will find “PO-Revision-Date: 2013-10-11 19:25:37+0000\n”, though the ja.po file of RC1 says “PO-Revision-Date: 2013-10-18 13:03:34+0000\n”
Does it happen because the all files are still in trunk?
Is anyone else with localized install having this issue?
I’m on RC2 and seeing “Translations / Your translations are all up to date.” (in English) on wp-admin/update-core.php, but apparently the translations haven’t been updated.
Hello everyone! Following up on my 3.7 strings post — we are now in a 100% string freeze for WordPress 3.7. I’ve just pushed the final 55 strings for the release. The bulk of these are for A) the about page and B) email notifications for background updates.
I don’t expect for there to be any more string changes. Of course, if you catch a typo, let us know.
We’ll be releasing 3.7 RC1 in a few hours, and if all goes to plan, we’ll be releasing WordPress 3.7 before the middle of next week.
Sweet!
You ripper, just waiting for my ‘en_AU’ post here to be approved/published and ‘all the things’ setup for us Aussies
Oh, so RC1 is actually a string freeze release, cool! Great! Sorry to have doubted you on the Core blog!
And http://i18n.svn.wordpress.org/pot/trunk/ is up to date, yay! Rush hour!
Well done! We waiting for final 3.7
I want to ask, about word deregister string. Why deregister and not unregister?
isRegistered() – false if the object is ‘unregistered’ – i.e. ‘not registered’ false == isRegistered().
registerSomething() – It has now moved from ‘not registered’ to ‘registered’.
deregisterSomething() – It has now moved from ‘registered’ to ‘not registered’. i.e. ‘unregistered’.
Great!! The it_IT is now 100% translated too! First?
Thanks Time to translate!
@nacin Could you please tag /trunk in the rosetta so that we can make packages easier?
Hi, I’m not sure if I don’t have the right permissions or just don’t know how to do it.
Can I get @sendhilp added to http://translate.wordpress.org/projects/ios with permissions to upload originals?
Can I get permissions to do it myself, or should I post here when needed?
Thanks
That will only work if they give you admin rights. You guys should not need those permissions unless those projects don’t get auto updated
They don’t, although that’d be nice to have
Do you need xcode installed to have a bash script for it? Can’t remember how to generate the translation file.
There’s a python script calling genstrings, which I guess comes with Xcode.
Another option would be to generate strings manually and have something sync the strings file from git to glotpress
Hi Zé,
could you please deploy the translations for Rosetta and Rosetta Forums for German. Thank you very much! There is a little bit of activity there after the WCEU …
And could you add German as a language for the WordCamp base theme (http://translate.wordpress.org/projects/wordcamp-theme), and make me a validator, that would be great. Maybe it could be used in the next year …
Hey hey Polyglotters!
I have a question from the docs team. Should all code examples in the codex and other official WP documentation be internationalized? There’s a strong case for it as many people just cut and paste code examples and then we end up with untranslatable strings.
Anyhow, please let me know if you have any comments here, or please come to our chat on Thursday October 17th at 16:00 UTC in #wordpress-sfd
Thanks!
They should but the problem is that most developers don’t understand what those functions really do.
This also reminds me that I still need to revert a change on http://codex.wordpress.org/Function_Reference/register_post_type.
Agree
Out of curiosity, which change are you reverting and why?
The two primary issues with internationalizing code examples is:
As much as I would like to disagree I do agree with your valid points. However, when displaying generic code it would be nice to have a default link to the Codex entry about internationalization.
I have to support the plugin Multilingual Press, and one common request is the translation of Custom Post Type/Taxonomy properties. But this is the responsibility of the authors, not of our plugin. Unfortunately, most (new) developers just copy and paste Codex examples.
All I can say to these authors right now is: Please ignore the Codex, the examples are wrong for distributed code. This is not good.
It wouldn’t raise the barrier too much to create correct examples. We could use the string insert_your_textdomain as text domain and add a link to the example. But the code should be translatable from the start.
No, because of what Andrew said.
That being said, every code sample with strings should have a line at the bottom saying, more or less, “Code is simplified for readability reasons. Product code should have all the strings internationalized“.
Ahem, “Production code”.
Agree with that that one. It just should be obvious enough to not miss it.
This sounds like a good compromise.
No, the scope of code in codex page is to acts as a tutorial, for italian pages i’m usually translate comments and sometimes variable names if the meanings of them need to be render in italian. Adding I18N is as Andrew says mor bad than good and fragment of code need to be tedomained too ecc. Like the Xavier’s idea to add a note at the end of code fragments
If the scope of codex is to act as a tutorial. Shouldn’t it do I18N then too. Otherwise the tutorial isn’t complete. Codex is to learn things what you need and I18N is a must to do things good.
Although there are pages of the Codex that function as tutorials, overall it is a reference – i.e. it’s for looking for specific things that you need to know. The handbooks will be more of a tutorial and i18n are being built into it.
The reasons why the strings should be internationalized.
Developers need to understand php before they can use functions so they need to understand internationalize before they use strings.
I know this should be discussed somewhere else but this also raises the question about the escape and sanitization functions in code examples.
I vote for “No”, I agree with @Andrew Nacin and @Xavier Borderie comments.
I don’t see 3.7.x (or trunk) project option in our rosetta translation page. We can’t make 3.7 local betas without it, can we?
You can build 3.7 beta using svn, but you first have to export all translations from GlotPress, and then upload them to /ja/trunk/messages on the svn server.
I’d rather have official POT files to work with, really.
I agree, but I guess that trunk on GlotPress and on svn’s /pot/trunk are synchronized.
We could build with the old school way like Kenan said, but if someone is just forgetting to update the dropdown, please add the current project to it.
I can’t build 3.7 from trunk. the error is can’t create directory /tmp/rosettaTENIaI/wordpress/wp-admin!. Anyone get the same error as me?
You need to rename translation files like this. If you would like to build 3.7-beta2, use revision 25672 which is the version for core.svn.wordpress.org.
thank you I can build beta2 now but we still can’t for RC1?
Finally we can build RC1 without uploading translations to svn. Select trunk at translate.wordpress.org as a source and use revision 25762 for WP core.
Thanks Tenpura. I did create RC1 with revision 25764 last night.
Some new features have been added to WPAndroid, and new strings have arrived with them. Any help translating them is much appreciated:
Oh, nice! I finished translating the Android app on #wceu Contributor Day, but hey, no worries
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
Just finished some translating for the dutch one! 
Swedish is done, but there are tons and tons of strings in there that are the exact same ones as in the iOS project. Some sort of automated migration would go a long way to help the other languages.
That’d be neat. Can GlotPress do that? If not, let’s make a ticket
Are strings mainly the same for both iOS and Android? If you compare OS X and Windows, they use different basic translations.
It’s on the roadmap. I don’t think that there is a ticket for it. But when translating the Windows phone app I did notice that a lot of strings aren’t the same.
Sorry
Hello, please tell me where I need to register to be able to translate for Polish and translated accept that there is no Polish administrator who would accept and improving Polish translation.
Regards
I think some text are missing from this string (You agree to the fascinating by pressing the ‘Next’ button). Should it be “You agree to the fascinating terms of services by pressing the ‘Next’ button”?
Yes, you’re right! Some wildcard characters didn’t get imported properly. It has been corrected now.
th is completed 
All pending rosetta deploys have been processed. Thank you for your patience.
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!
The recounts currently don’t work. I’ve been looking at that with @otto42 and created a ticket for it.
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.
Thank you @otto42 and @defries! Count is fine now.
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.
My remark on the page is awaiting moderation, but I am not actively contributing in Leiden.
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
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.
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.
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.
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.
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!
Always the thorough post, Andrew. Thanks a lot!
No problem Andrew, we’re going on it asap
Thank you for the much needed information!
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.
Thank you
All new strings done for es_ES
All new strings done for Galician, gl_ES
how to report the wrong string?
References: wp-admin/options-permalink.php:179
number of tags are available
http://core.trac.wordpress.org. Curious what is wrong with the string.
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”
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?
I don’t know what kind of errors you exactly mean. I’m happy to help if you still having them.
@nacin I didn´t found a german -> formal tree for the importer plugins
All new strings done for 3.7 in german and german->formal
Heads up all. Trunk is upp to date again.
“Happy translating!” — Andrew Nacin
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.
fernandot 11:50 pm on October 22, 2013 Permalink | Log in to Reply
Done for es_ES
Birgit Olzem 12:29 am on October 23, 2013 Permalink | Log in to Reply
de_DE default and formal done
Kazama 3:25 am on October 23, 2013 Permalink | Log in to Reply
th is done
Stefano Aglietti 7:37 am on October 23, 2013 Permalink | Log in to Reply
Done for it_IT
Xavier Borderie 7:54 am on October 23, 2013 Permalink | Log in to Reply
fr_FR is ready… but it seems to me that readme.html still bears the 3.6 version number
Xavier Borderie 8:05 am on October 23, 2013 Permalink | Log in to Reply
And somehow /wp-admin/credits.php mentions the many contributors under “Core Contributors to WordPress 3.8″. Any has this?
Xavier Borderie 8:13 am on October 23, 2013 Permalink | Log in to Reply
That last issue does not happen with the RC2 as downloaded from wp.org today, only with my automatically-updated trunk install.