WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 7 years ago

#3327 closed enhancement (wontfix)

Reorganizing language files and functions

Reported by: pandem Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.1
Component: General Keywords: i18n
Focuses: Cc:

Description

Just to take advantage of the changes proposed in #3315, it could be a good idea to centralize all language files in one folder. I'd do the same with TinyMCE js files if possible as this would be a great improvement for us translators, but it'd probably be a hassle for coders.

I know i18n of themes is not encouraged but, as the use of WordPress as CMS increases, also does the i18nalizing needs, therefore my proposal.

Attachments (1)

l10n.php.diff (1.1 KB) - added by pandem 8 years ago.
change in plugins and themes l10n functions

Download all attachments as: .zip

Change History (6)

@pandem8 years ago

change in plugins and themes l10n functions

comment:1 @matt8 years ago

  • Milestone changed from 2.1 to 2.2

comment:2 @foolswisdom8 years ago

  • Milestone changed from 2.2 to 2.3

comment:3 @markjaquith8 years ago

  • Milestone changed from 2.3 to 2.4

It's already within wp-content. What is the benefit of having them in a single folder?

comment:4 @darkdragon7 years ago

  • Keywords hunt-irrelevant added

This would not be a good patch. I think the reason for having themes have their own .mo files is because themes have different translated areas and not all .mo files will reference the locations in every theme.

At least from my understanding of how .mo files work, your patch won't actually fix anything and might break themes.

comment:5 @darkdragon7 years ago

  • Keywords has-patch hunt-irrelevant removed
  • Milestone 2.5 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

I will say that, themes and plugins should contain their .mo files in their folders or whereever they want in respect to their base plugin file path. the .mo files are already in wp-content, in /plugins/ and /themes/ therefore having all .mo files will hinder the user instead of helping.

The user will have to move the files from the plugin or theme directory to this folder you propose and then remember to delete the files when they uninstall the plugin or theme. I think it is much better to remove the plugin .mo files when I delete the plugin or theme instead. I also know that the .mo files contained within the plugin and theme go with that plugin and theme.

The current behavior is by far the best with ease to both the user and plugin/theme community.

Note: See TracTickets for help on using tickets.