Site stats (Jetpack) were deactivated from localization websites? Or access removed?
Updates from pavelevap Toggle Comment Threads | Keyboard Shortcuts
Can we also have glossary feature? Please
What does Ectoplasm really mean? I found several different meanings, but I am not sure which is the right.
Hi, I would like to know answers to following scenarios:
1) Users will update to WordPress 3.7 (English) and several days later our localized version will be available. There will be notice, that localized version is available and they can update nce again? So, the behaviour will be the same as in WordPress 3.6?
2) There will be WordPress 3.7.1, all users will be automatically updated to what?
a) English version
b) Current localized version
c) Right localized version which will be available several days later (with some small changes and bugfixes from community)
It is not possible to upgrade original English version to selected localized version. You can install English version of 3.4.2 and add define(‘WPLANG’, ‘cs_CZ’); into wp-config.php. After uploading localized files into wp-content/languages is WordPress install localized.
But it is not possible to update to Czech version of WordPress 3.5. There is only English version available. It is regression, because it was possible several months ago. Now there is no chance to update to localized version and several Czech users had troubles with this behaviour. So, when you start working in English and want to switch to localized version, automatic updates will not work. Never. Too bad… Could you please look at it?
Automatic notice of new localized version missing. There was standard behaviour, that users could upgrade quickly to the latest WordPress version and when localized version was ready and released, notice about new localized version appeared in administration. Do you remember this behaviour? But some users found that it was changed (in 3.5 or maybe 3.4) and when they upgrade to English version, they are not noticed about new Czech version in the future which is annoying. I tried it on some websites and it is true. I am not sure, if it is wanted change (but does not make sense for me) or bug (regression)?
WordPress 3.5 is distributed without Twenty Ten, but localized versions have Twenty Ten. Is it intended? The whole package together with all themes and localized files is a really big one archive…
There are no strings for Continents and Cities project in 3.5 branch. Could you please look at it?
GlotPress shows 1729 strings, Poedit shows only 1704 strings. When you list through GlotPress, there are 115 pages * 15 strings + 4 strings on the last page (= 1729). So, what about 25 strings? Duplicities? How can we check them and see if there are no different translations? Which strings will be in localized package?
There are no strings for Continents and Cities in 3.4 branch?
I am using Poedit for testing localization and there are 1664 strings in my .po file (updated from wordpress.pot), but in GlotPress there are 1689 strings. In admin and network admin files is everything OK. Strange…
WordPress › Any news on the string count issue from… « Translate WordPress, Sergey Biryukov, pavelevap, and 4 others are discussing. Toggle Comments
3.4 will be wonderfull for localized versions, but could I ask once again for stats? It was requested several times by translators: http://wppolyglots.wordpress.com/tag/stats/ We make localized versions, but we do not know how many people use them. These information are available, but translators are banned Please, what should I do to make it happen? Should I create ticket in Trac?
Continents and Cities were added to GlotPress, but when I tried to build package, related .po and .mo files were not added to package. Everything else is OK. Any idea?
There are no strings in GlotPress? No project, no language…
Hi, could you please set up cs_CZ (Czech) for Jetpack? Validators will be the same as for WordPress.com, pavelevap and neoen. Thank you!