SIGH 🙁 I see the development version was made and that’s good 🙂 But… 3.4 now are fully empty and during last weekes for italian people have submitted a lot of revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. that are gone forever if there is no backup 🙁
In Glotpress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., I see 40 untranslated strings A string is a translatable part of the software. A translation consists of a multitude of localized strings. for WP 3.4 nn_NO, but the list of untranslated nn_NO strings is empty. Any ideas?
3.4.1 has just been released. No string A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes. There is a 3.4.x project in GlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. for you. The revision is 21156 for either tags/3.4 or branches/3.4. This is a security update, so speed is important. Cheers!
Why till today on glotpress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. there is no 3.4 branch and 3.5 but we are still at 3.3.x and 3.4 with this last one that is a 3.5alpha? Is going to be realsed 3.4.1 and we have to struggle with version to generate packages with right tag. Since last week when i asked about it noone answered… why? Pls we need an answer
[ Edit: I no longer need an answer to this question. ] All translators — Did anyone have a locale.php file (like ru_RU.php) in 3.3 that they no longer included in 3.4? If so, what is your locale? Those files are going to sit there (and be included) after an upgrade, so we need to remove them manually: https://core.trac.wordpress.org/ticket/20974. Unfortunately it is not easy to ascertain which locales used to have them but no longer do.
Hi, when will be a 3.4 sub-project created on GlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.?
Because, if I build a package from development branch, it will end up with 3.5-alpha package, and the next branch is 3.3, which will end up a 3.3.2 package…
WordPress 3.4 will be released within the hour. Start your engines.
I’m seeing two unknown names in the 3.4 credits: along with the historical fr_FR translators (with their pictures), I’m seeing two other names — that are not even present in the fr.wp.org users. How come?
I think we are going to turn off the SVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. builder for 3.4.
You will still be able to use your SVN directory, and we will continue to pull files from /dist (like readme.html HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. and wp-config-sample.php). But, in order to create a build, you will need to import any po/mo files MO, or Machine Object is a binary data file that contains object data referenced by a program. It is typically used to translate program code, and may be loaded or imported into the GNU gettext program. This is the format used in a WordPress install. These files are normally located inside .../wp-content/languages/ you have into the wp/dev projects at translate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins..
GlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. is all about collaboration. So others may help, it is preferred that you periodically import your po/mo files there (if you work with a separate tool), rather than importing them at the end in order to do a release. This also isn’t just about collaboration. At some point, I’d like to make it so you can mark your locale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ as “ready” for a release. Then we will simply create the build for you when we release WordPress.
Request for feedback from East Asian languages for WordPress 3.4 core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. modifications.
In #8759, I’m looking for feedback for the editor word counts.
In #16079, I’m looking for feedback for the length of auto-generated excerpts.
If you could test the code and post in the relevant tickets, it would be much appreciated.
I’ve updated the list of 3.4 changes:
- New: Localizing commas, as a tag separator
- New: Fields that should always be LTR
- New: Spellchecker language is now translatable
- Changed: How precisely core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. detects that a language is RTL (it now uses a translated string A string is a translatable part of the software. A translation consists of a multitude of localized strings.)
3.4 update: Localizing quotes and apostrophes that go through wptexturize(). More
In 3.4, you no longer need any PHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. to customize the defaults for start of week, feed language, or default timezone. (You would have hooked into populate_options for these.)
start_of_week and timezone_string/gmt_offset are now translatable, and rss_language is gone (it uses the site’s locale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/, now).
I’ve created a page here that outlines all changes to 3.4 so far, including the details for how to set these defaults: Important Changes for WordPress 3.4. I will update it as more changes happen.
For 3.4, the default links are now translatable, both titles and URLs. https://core.trac.wordpress.org/changeset/19781
I left out the URLs for extend/plugins/, themes/, and ideas/ from being translated as there are not yet official localized resources for these, and I would not want to send them off-site. Since the forums are a better conduit for feedback anyway, I demoted Suggest Ideas down the list, moving the Support Forums up one.
In 3.4, you will no longer need to specify a $wp_default_secret_key, in $locale.php or in default-constants.php. For many of you, this means your $locale.php file will now be empty. Branch off 3.3 and remove $locale.php from /trunk/dist/ if that is the case. See ticket 19599 for more.