Make WordPress Core

Opened 11 years ago

Closed 10 years ago

#16775 closed feature request (duplicate)

Auto-fetch translations from GlotPress

Reported by: AmirHelzer Owned by: nacin
Milestone: Priority: normal
Severity: normal Version: 3.1
Component: I18N Keywords:
Focuses: Cc:


Instead of having completely independent builds for WordPress per language, I think that WordPress should have a locale setting and then download the required translation files for core, themes and plugins from GlotPress.

A feature like this would help users get up-to-date translations for everything without having to look for .mo files and manually get them. Additionally, it will push plugin and theme authors to using GlotPress, so that their translations go live automatically.

We have the available resources for this task, and if it's accepted, we'll be happy to implement the required code on both WordPress core and on GlotPress.

Change History (8)

#1 @nerx
11 years ago

  • Keywords needs-patch added
  • Type changed from enhancement to feature request

This feature would actually be useful when Network Admin-ing a big network in multiple languages.

#2 @nacin
11 years ago

  • Owner set to nacin
  • Status changed from new to accepted

Yes, this is on docket.

#3 @AmirHelzer
11 years ago

I'm thinking about a new menu item Settings->Language.

There, you'll see a drop-down list of language to choose from. The default should be set by WP_LANG.

This page will report what localization (.mo) files are available for WP core, the current theme and plugins.

You should have a [ Download ] button to get those files and save where they need to go.

In order to include support for themes and plugins, GlotPress should include meta-data, per project, that matches the plugin/theme name and which directory, relative to the plugin/theme root, to save the translations in.

#4 @Bueltge
11 years ago

  • Cc frank@… added

This plugin http://wordpress.org/extend/plugins/wp-native-dashboard/ has inside an solution for this requirement, maybe its help for create faster a solution.

#5 @jottlieb
11 years ago

  • Cc jottlieb added

Please keep in mind that some languages (e.g. German) have different language files, because of different kinds of the same languages (formal language vs. informal language which is both used, depending on the kind of website or blog).
And there are still some core files that can't be translated by using gettext, so there's still the need for translating some files by hand.

#6 @dd32
11 years ago

And there are still some core files that can't be translated by using gettext, so there's still the need for translating some files by hand.

We're trying to reduce this count as far as possible, further, once a site is installed, the number of strings that will ever be encountered before translations are loaded are minimal.

The core group has had a chat about this (I think it may've been in person, so not logged anywhere) where it was thought that we might be able to load the translations much earlier in the loading process to prevent the requirement for some of the hard-coded strings, some other ideas were thrown around as well for this (with no set implementation release, etc)

#7 @AmirHelzer
11 years ago

Where can I find information about files that need to be patched in core to produced localized login?

Last edited 11 years ago by AmirHelzer (previous) (diff)

#8 @ocean90
10 years ago

  • Keywords needs-patch removed
  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.