WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 2 days ago

#21642 closed enhancement (wontfix)

language_attributes() print WP lang instead content lang.

Reported by: shadowhck Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.1
Component: I18N Keywords:
Focuses: Cc:

Description

If you have WordPress in a language does not mean that the content has to be in that language. It would be good if there was an option to select it.

Another detail is for example: If we have the translation "Spanish - Spain", "es-ES", WordPress print "es-es" instead of "es" simply.
This would be good because it is the only translation into Spanish.

Change History (5)

comment:1 @shadowhck3 years ago

  • Keywords needs-patch added

comment:2 @shadowhck3 years ago

  • Keywords needs-refresh removed

comment:3 @nacin3 years ago

WordPress language values are designed to be only as specific as is necessary. Specificity is fine if there is a reason to distinguish among regions and subtags. es_ES is the code for Spanish spoken in Spain because Spanish is spoken in many other countries. WordPress, for example, also has Peruvian, Venezuelan, and Chilean translations, and I would not be surprised if Central America is represented in the future.

If you have WordPress in a language does not mean that the content has to be in that language. It would be good if there was an option to select it.

I agree, but we're not there yet. For now, this is best left to a plugin — for example, http://wordpress.org/extend/plugins/admin-in-english/.

comment:4 @iseulde2 years ago

  • Component changed from General to I18N

comment:5 @chriscct72 days ago

  • Keywords 2nd-opinion needs-patch removed
  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

As there are multiple Spanish translations now, this specificity actually solves a problem in which Spanish translation to use.

Note: See TracTickets for help on using tickets.