I noticed today that upgrading TwentyTen and TwentyEleven to their 1.3 version make said themes loose their translations if they previously had some. Any idea who to talk to about this and / or where. Perhaps you know @nacin ?
Tagged: TwentyEleven Toggle Comment Threads | Keyboard Shortcuts
-
Remkus de Vries
-
Kenan Dervišević
Hello,
Translation for Twenty Eleven isn’t included in the localized build for 3.3 Beta 1. I tried with both methods (svn and directly from GlotPress). Could you please take a look?-
Zé
Build system is misbehaving (having troubles with pt_PT myself). Digging.
-
Nikolay Bachiyski
@kenan3008, this should be fixed. And it shouldn’t be a problem in future versions.
-
Kenan Dervišević
Everything is working and all translations are in the correct place. Thanks 🙂
-
-
-
jiehanzheng
After the localized 3.2.1 update, I noticed that Twenty Eleven translation is dropped. Looking through the filesystem, no .po or .mo files could be found under
wp-content/themes/twentyeleven/languages/
. However, corresponding .po and .mo files can be found in localized packages.Do any of you have this issue, too?
-
Milan Dinić
I you update to Twenty Eleven 1.2 via theme updater, translations are lost.
-
Peter Holme
yeah… something fishy is going on…
-
jiehanzheng
Yeah. Many of our users reported that. Besides manually moving .po and .mo files in, is there any better solution to offer to them?
I also tried re-installing the localized core, but Twenty Eleven remained in English 😦
-
Milan Dinić
Right now, no. In the future, language packs.
-
-
-
Dion Hulse (dd32)
Just an explanation of whats happening here:
The Theme updates from .org do not include localised files, as such, updating to the theme from .org installs a copy of the theme which does not include them.
3.2 no longer updates the theme during a core update (as happened in the past) and core is the only place (At present) which includes the language files.
The same thing would’ve happened with TwentyTen, except updates of core would happen at the same time (which caused the translation files to be copied into place), masking the problem.
Language packs are really the ideal solution to this problem, but not a short term solution for 3.2.x
So we know its happening (now), and we know the cause of it, The only question is how it’s to be fixed. Stay tuned and we’ll sort it out somehow.
-
Nikolay Bachiyski
A couple of Twenty Eleven strings were changed: http://core.trac.wordpress.org/changeset/18348
xavier
About Twenty-Ten: Wondering whether “, ” was a list separator or a numeric separator (y’know, 1, 000.55 and all that), I went into the theme’s code, and sure enough, there was a “translators:” indication… but somehow potbot doesn’t integrate it into the POT. Could that be resolved, so as to help us get a quicker grasp of the context for a string?
Thanks guys!
-
Zé
Can I assume that this discussion continues in http://core.trac.wordpress.org/ticket/17777 ?
-
xavier
Well, now that I’ve included a tidbit about that issue in the ticket’s comments, I’d say yes 🙂
-
-
Nikolay Bachiyski
@xavier, @vanillalounge I am working on fixing the comment omission:
http://i18n.trac.wordpress.org/changeset/17091
I don’t want to declare victory before all the cron jobs are passed and I am sure all the POTs were re-generated OK.
-
xavier
Thanks Nikolay!
-
Nikolay Bachiyski
It all looks good, GlotPress has been updated with the translator comments.
-
Zé
\o/
-
xavier
*\o/* Confirmed in POT! *\o/*
(and I learn about http://i18n.trac.wordpress.org/! Marvelous day!)
-
-
Nikolay Bachiyski
TwentyEleven translation is now included in the translation packages. Please, give it a go to test if it’s working right.
-
herzcthu
OK with my_MM. I’ve tested it.
-
Zé
and pt_PT
-
Rafael Poveda - RaveN
es_ES too.
herzcthu
I see some strings for theme descriptions in twentyte pot and twentyeleven pot. I translated these strings but they don’t appear on my wp 3.2 beta testing sites. How can I make it appears ?
-
sofyand
Got the same problem, I’m interested in the answer as well. Anyone?
-
Stas Sușcov
If the strings were approved, you can use a tool like localize to update the
.mo
files on your blog. If not, you will have to wait until someone validates the strings, and again use Localize or download manually the files.-
herzcthu
I’m validator of my_MM project. I mean not on glotpress. I mean I’m testing my translation package for 3.2 on localhost .
When I go to Appearence menu, descriptions of twentyten and twentyeleven are only in english although I translated the strings for descriptions of those themes in my_MM.po file and my_MM.mo.-
Stas Sușcov
Hmm, might be a bug in 3.2 or twentyeleven, try to update to latest nightly. If it persists, report on wp-testers or trac/irc.
-
-
-
Milan Dinić
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.
Thanks.
-
Zé
Right you are, and this also affects bbPress. Working on a fix and thanks for the reminder.
-
Zé
Twenty Eleven should now be updated properly.
-
xavier
There are quite a few TwentyEleven strings in the WordPress POT. Since we already have access to the TwentyEleven POT, could those strings be moved out now, so as to not translate strings which are going to be removed eventually?
Thanks a lot.
-
Nikolay Bachiyski
TwentyEleven strings are now omitted from the WP POT, the TwentyEleven will be committed regularly and automatically, and its contents are synced with the GlotPress project.
-
xavier
Thanks a lot for the speedy answer, Nikolay!
-
Mark Thomas Gazel
How about the strings that were translated before the move. Are they lost? Should they be retranslated?
I see some familiar strings in Twenty Eleven, but also miss some strings. There were some colours, that were quite a challenge to translate, that is not there now.
-
Mark Thomas Gazel 11:09 am on December 14th, 2011 Permalink |
Yeah, it’s a flaw I’ve experienced too. Also with earlier upgrades of the default themes.
Andrew Nacin 2:55 pm on December 18th, 2011 Permalink |
Yeah, we hosed you on this one. In 3.4 this will absolutely be handled.
Remkus de Vries 2:56 pm on December 18th, 2011 Permalink |
Is it an option to add the current available locales to a 1.3.1 version?