While waiting for today’s release, I wanted to remind you of two things:
Updates from Milan Dinić Toggle Comment Threads | Keyboard Shortcuts
If I didn’t make a mistake today and needed to do svn update, I probably wouldn’t notice (until after I make a release) that @vanillalounge made fatal mistakes related to Serbian dist files.
I reverted those changes for Serbian but wanted to note that Montenegrin is still missing me_ME.php since it wasn’t copied as wp-config-sample.php was in .
When you want to fork, you need to make a copy first, and then make changes to that copy, not to original.
Be careful in the future, @vanillalounge.
Fellow translators, note that there are two small changes in wp-admin/setup-config.php. Here is diff:
Tip for fellow translators: screenshot of WordPress dashboard on homepage of your locale site is probably outdated so you should update it to stay up to date
Question for those who translated “Freedoms” screen: do you get error instead of a string starting with “Every plugin and theme in WordPress.org’s directory…”.
I want to be sure that error is caused by core and not by my translation before opening a ticket.
My comment maybe wasn’t noticed so I’ll repeat it again.
After fixes were made to pot-bot, generation of POT for TwentyEleven stopped working so please look at it.
Also package builder need an update to include TwentyEleven translations too, not just TwentyTen.
Please add me, dimadin, as a validator for BuddyPress and bbPress projects for Serbian.
Thanks in advance.
POT files weren’t updated since May 5th, and it looks like GlotPress is affected too since there aren’t any new strings.
All projects are affected and it maybe has something with change for exclusion of TwentyEleven.
My comment maybe wasn’t noticed so I’ll repeat… « WP Polyglots, Milan Dinić, Xavier, and 1 other are discussing. Toggle Comments
There are strings in custom wp.org theme and/or plugin that aren’t in Rosetta POT file so they can’t be translated. I believe that reason for this is because they aren’t wrapped around gettext functions.
You can see them at following screenshots I made: links to topics’ view in header, on front page, and titles of those views; strings in topic’s sidebar; profile fields on registration and profile page; link for subscribing to new topics in tag.
Please fix this since we were patient for a long time.
Please deploy translations of WP.org bbPress theme and bbPress trunk on Serbian forums.
Thanks in advance.
Now that 3.1 is released, and that we are in 3.2 cycle, and over a month of #wptybee, where supposedly there were talks about it, it’s time to reopen topic on improvements to plugins/themes localization.
On my two and a half months old proposal, some core developers commented that we should instead use different approach, with some language packs, but we never got any detailed explanation how would those language packs work.
Core developers should now show to us their views on this, and I’m again opening it here instead of on chat or trac because I believe that since this involves WP core, GlotPress, and wp.org, we should first shape things before moving to codding.
If we again prolong this, it won’t be finished this year, if ever.
For those who still didn’t notice, 3.1 was released in the last hour, so head over to your locale site to release your version!
Serbian is already up for those wondering
There is a change in readme.html You can see difference here: https://core.trac.wordpress.org/changeset?reponame=&new=17302%40trunk/readme.html&old=16896%40trunk/readme.html
Thanks to Nikolay’s commit last night, we are now able to more easily see what strings have context or comment for translators.
To use this, go to GlotPress installation at https://translate.wordpress.org/, press “Filter” and then check “With comment”, “With context”, or both.
How is this useful? Translators who use Poedit can’t see contexts of strings. Contexts are used to distinguish two or more strings that are same but have different meaning, for example “spam” (comment, user, or site), “add new” (post, user, plugin,…), or “post” (verb or noun).
By filtering strings with this, you can see if you use proper grammar case or grammar gender for that strings, or other rule that should be applied.
Note that context are shown inline with strings, while comments are shown in “Meta” box when you expand string by pressing “Details”.