Ticket #7074 (closed enhancement: fixed)

Opened 5 months ago

Last modified 4 months ago

Proper i18n solution for "Files for direct translation"

Reported by: RanYanivHartstein Assigned to: nbachiyski
Priority: normal Milestone: 2.6
Component: i18n Version:
Severity: normal Keywords: has-patch
Cc:

Description

The Codex page Files for Direct Translation lists all the core files that translators have to edit directly for a complete localization.

These are mostly error messages in files that load before gettext is initialized. Some of them are loaded before wp_config.php and therefore can't tell yet what the proper locale is. One gets loaded when wp_config.php is *missing*, so there is no way of knowing what the proper locale is (this is discussed in ticket #6132).

A system needs to be put in place to allow localizing these strings without editing core files, or at least of editing just one core file in a specific location. This should be independent of the gettext system. For e.g., a single file place in the root folder that sets these strings as variables to be used in the various other files that need them.

Attachments

mark-not-gettexted-strings.diff (7.3 kB) - added by nbachiyski on 06/23/08 10:57:55.

Change History

06/04/08 11:32:24 changed by nbachiyski

  • owner changed from anonymous to nbachiyski.

06/21/08 20:27:56 changed by nbachiyski

  • keywords set to has-patch.
  • milestone changed from 2.7 to 2.6.

06/23/08 10:13:58 changed by nbachiyski

The patch above wraps strings, needing direct translation, in special comments.

Using the not-gettexted.php tool these strings can be extracted in POT files or replaced with translations from a MO file.

06/23/08 10:57:55 changed by nbachiyski

  • attachment mark-not-gettexted-strings.diff added.

06/23/08 15:40:43 changed by ryan

  • status changed from new to closed.
  • resolution set to fixed.

(In [8168]) Mark string that cannot be gettexted. Props nbachiyski. fixes #7074