Tag Archives: core

Andrew Nacin 5:02 pm on April 4, 2012
Tags: , core   

I think we are going to turn off…

I think we are going to turn off the SVNSVN 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.htmlHTML 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 filesMO 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.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins..

GlotPressGlotPress 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 localeLocale 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.

#announcement, #core

Andrew Nacin 9:12 pm on March 2, 2012
Tags: core, , , ,   

Request for feedback from East Asian languages for…

Request for feedback from East Asian languages for WordPress 3.4 coreCore 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.

#core, #ja, #my_mm, #zh_cn, #zh_tw

Andrew Nacin 9:52 pm on February 7, 2012
Tags: core,   

I’ve updated the list of 3.4 changes *…

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 coreCore 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 stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings.)

#core, #rtl

Andrew Nacin 2:50 pm on January 31, 2012
Tags: core,   

3.4 update Localizing quotes and apostrophes that go…

3.4 update: Localizing quotes and apostrophes that go through wptexturize(). More

#core, #he_il

Andrew Nacin 9:27 pm on January 29, 2012
Tags: core   

In 3.4 you no longer need any PHP…

In 3.4, you no longer need any PHPPHP 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 localeLocale 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.

#core

Andrew Nacin 5:19 am on January 29, 2012
Tags: core   

For 3.4 the default links are now translatable…

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.

#core

Andrew Nacin 6:55 pm on January 27, 2012
Tags: core   

In 3.4 you will no longer need to…

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.

#core

Ryan Boren 12:00 am on January 27, 2012
Tags: core   

For 3.4 WP is going to use frontend…

For 3.4, WP is going to use frontend, admin, and network admin pot files rather than the current wordpress and ms pot files. For background, see ticket 19852. We’re currently shuffling around the “Development (future 3.4)” project to accommodate this new pot split.

#core

Andrew Nacin 8:38 pm on January 26, 2012
Tags: core   

All locales In 3.4 you will no longer…

All localesLocale 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/: In 3.4, you will no longer need to override wp-admin/setup-config.php. The stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in this file will now be included in the POT, and the config file will be generated properly regardless of the wp-config-sample.php placeholders such as “your_username_here”. See [19760] and #18180.

#core

Andrew Nacin 10:46 pm on January 25, 2012
Tags: , , core, , , , , ,   

RTL locales In 3.4 you will no longer…

RTL localesLocale 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/: In 3.4, you will no longer need to specify $text_direction = 'rtl'; in your $locale.php file. Please remove it from $locale.php, and if this makes your $locale.php empty, then remove the file. (Please branch /trunk/ off into /3.3/ first, in case there is a 3.3.2.)

The following locales have been included: ar, ckb, fa_IR, he_IL, ug_CN, dv, fa_AF, ha, ps, uz_UZ, yi. If you are missing (or are incorrectly included), let me know.

#ar, #ckb, #core, #fa_af, #fa_ir, #he_il, #rtl, #ug_cn, #uz_uz

Andrew Nacin 9:10 pm on January 3, 2012
Tags: core,   

The release of 3.3.1 is imminent It is…

The release of 3.3.1 is imminent. It is a security and maintenance release. There are no new stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings.. Please deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. promptly. Thanks!

#core, #release

Andrew Nacin 10:49 pm on December 18, 2011
Tags: , core   

Moving Locale-Specific Modifications to Core

Moving LocaleLocale 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/-Specific Modifications into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

The core team is intending to propose for 3.4 that all locale-specific modifications get moved to core. Ideally, this will reduce all (or nearly all) packages to mo filesMO 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/, po filesPO files PO files are human readable files which contain translations we use. These files are not used by WordPress itself. Each language will have its own PO file, for example, for French there would be a fr_FR.po file, for german there would be a de_DE.po, for British English there might be en_GB.po., and readme.htmlHTML 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..

What does that mean? All plugins, locale.php files, JS, CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site., etc., will all end up getting a complete review and become part of core. Any future changes will then take place with new versions of WordPress, and will be tracked on core TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. Translation teams will still advise on, and ideally drive, any needed changes.

I think it’s pretty clear as to why we’d like to go in this direction. This will happen in parallel with language packs. To get there, we will need to simplify the contents of localized packages. The end goal is to make things simpler for the user, but it also can set the stage for future features, and there are added benefits. One, the core developers will be investing time into problems that translation teams face. Two, translation teams will be prevented from solving complex problems on their own.

We know that in some cases, core tickets for certain problems have rotted for some time, forcing hacks, filters, and plugins. We will not only addressing these, but by tackling these issues, we are making a commitment that extends beyond WordPress 3.4 that localized builds are a major player in the ecosystem.

This is a major undertaking, and we will need your help.

I would like to keep discussion here and pure implementation on Trac. However, to demonstrate how serious we are, and how large the scope of this project will be, here is an incomplete list of Trac tickets assigned to the project:

  • #8759 — “Word count” should could by characters in some localesLocale 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/.
  • #6425 — Support RTL in feeds.
  • #19597 — Allow translation of the bundled plugins’ descriptions.
  • #19598 — Text inputs for codes or URLs should be LTR.
  • #19599 — Localizations should not need to worry about the default secret key.
  • #19600 — Core should know which languages are RTL.
  • #19601 — Support localized defaults for options, links, dashboard widgets, etc.
  • #19602 — Curly quotes from wptexturize() should not be forced on all locale.
  • #19603 — Support locale-specific modifications in core (the catch-all ticket).

I am going to need to have discussions with the fa_IR, ug_CN, ru_RU, zh_CN, ja, and eo locales, as you have complex bundled plugins and locale.php files. Some other locales may have particular concerns as well. We should schedule some public chats in #wordpress-polyglots for this, and to I intend to do a town hall style discussion on #wordpress-polyglots in a few weeks.

Dion Hulse (dd32) is the other core developer on this project, and one of our rockstar contributing developers (and Russian maintainer) Sergey Biryukov will be heavily involved as well.

So, any questions or comments? 🙂

#announcement, #core

گناهکار 4:09 pm on December 15, 2011
Tags: core   

I found a problem in no wp config…

I found a problem in no-wp-config screen, no-config screen dosen’t use language files at all. there are some stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. of no-config-screen in POT filePOT file POT files are the template files for PO files. They will have all the translation strings left empty. A POT file is essentially an empty PO file without the translations, with just the original strings. but they never been used/translated in the screen!
I think it’s happening because WP reads the language code from wp-config.php and WP use original strings when wp-config dosen’t exists.
in my view it’s better to look for wp-config-sample.php and read language code from it, or read the wp-content/languages for language files and use them.
what’s your idea?

#core

Andrew Nacin 10:46 pm on December 12, 2011
Tags: , core,   

3.3 is about to be released

3.3 is about to be released.

#announcement, #core, #release

Andrew Nacin 6:21 am on December 12, 2011
Tags: , core,   

Expect a final release of WordPress 3.3 in…

Expect a final release of WordPress 3.3 in the next 10-36 hours.

#announcement, #core, #release