We should add the missing languages that are not in Drupal core but supported on localize.drupal.org. This is how the localized Drupal install profile looks now with the .po files in place for all l.d.o languages:

Not pretty. We should have an explicit listing for the missing languages. Here are Drupal 6 and 7 patches.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Gábor Hojtsy’s picture

FileSize
251.51 KB

A full size version of that screenshot also linked above.

Gábor Hojtsy’s picture

Here at the actual patches now that I managed to upload the images :)

Gábor Hojtsy’s picture

Issue tags: +localized install
plach’s picture

Status: Active » Needs review

Makes sense, just a note: I don't get if the formatting differences between the cases below are intended.

+++ includes/iso.inc	15 Sep 2010 12:10:19 -0000
@@ -327,6 +328,7 @@ function _locale_get_predefined_list() {
+    'en-gb' => array('English (British)'),
+++ includes/iso.inc	15 Sep 2010 12:10:19 -0000
@@ -413,6 +418,7 @@ function _locale_get_predefined_list() {
+    'pt' => array('Portuguese International'),
     'pt-pt' => array('Portuguese, Portugal', 'Português'),
     'pt-br' => array('Portuguese, Brazil', 'Português'),

Btw, I noticed one of the missing languages is Filipino: in #385296: Standardize the language selector for the Philippine language. we agreed to replace Tagalog with it. Tagalog is not even present on l.d.o. so it seems this is the right choice.

Powered by Dreditor.

Gábor Hojtsy’s picture

@plach: I merely used the language names as they are on localize.drupal.org. We can use "English, British" and "Portuguese, International". There is also Swiss German, which might or might not be correctly written as "German, Swiss".

plach’s picture

Status: Needs review » Reviewed & tested by the community

Well, if we go this way the two other portugues languages should perhaps changed in "Portuguese, Portuguese" and "Portuguese, Brazilian". Anyway I don't want to stress on formatting, the patch is RTBC besides it, and I ain't even sure it is a real issue.

Dries’s picture

+++ includes/iso.inc	15 Sep 2010 12:10:19 -0000
@@ -327,6 +328,7 @@ function _locale_get_predefined_list() {
     'en' => array('English'),
+    'en-gb' => array('English (British)'),

This format is inconsistent with others. Elsewhere we'd write 'English, British'.

+++ includes/iso.inc	15 Sep 2010 12:10:19 -0000
@@ -413,6 +418,7 @@ function _locale_get_predefined_list() {
+    'pt' => array('Portuguese International'),
     'pt-pt' => array('Portuguese, Portugal', 'Português'),
     'pt-br' => array('Portuguese, Brazil', 'Português'),

For consistency, this should be: "Portuguese, International" IMO. Can we work with the localize team to get that cleaned up?

+++ includes/iso.inc	15 Sep 2010 12:10:19 -0000
@@ -462,6 +469,7 @@ function _locale_get_predefined_list() {
+    'xx-lolspeak' => array('Lolspeak'),

Really? :)

I'd like to figure out how we can improve consistency of the formatting. In the mean time, let's use something consistent in core.

Dries’s picture

Status: Reviewed & tested by the community » Needs work
Gábor Hojtsy’s picture

Status: Needs work » Needs review
FileSize
2.99 KB

Ok, fixed en-gb and pt as requested. Looks like nobody disputes that Swiss German is a separate language and not "German, Swiss". We can debate the listing of lolspeak there. Currently l.d.o has a "test" language for testing and this lolspeak language for fun. I'd not say lolspeak was picked up but people were campaining for other languages like Pirate talk, to be added. Because Drupal uses information from this array to show user friendly names to users, we need to keep it in sync with l.d.o or risk language codes showing up in the language list which would confuse users even more.

plach’s picture

I don't want to be annoying but since Dries cares about formatting I have a couple of additional questions:

+++ includes/iso.inc	15 Sep 2010 12:10:19 -0000
@@ -413,6 +418,7 @@ function _locale_get_predefined_list() {
+    'pt' => array('Portuguese, International'),
     'pt-pt' => array('Portuguese, Portugal', 'Português'),
     'pt-br' => array('Portuguese, Brazil', 'Português'),

For consistency with "English, British" shouldn't we have these renamed to "Portuguese, Portuguese" and "Portuguese, Brazilian" (or viceversa have "English, Great Britain")?

Moreover I don't get why some languages have the native name and some others don't.

Powered by Dreditor.

Gábor Hojtsy’s picture

You are welcome to add native names to languages, the missing items are not there for historic reasons. That has no relation to this issue however.

For the specific languages, "English, Great Britain" I've never seen, "English, British" or British English are the common form. We can also rename pt-br and pt-pt if that is desired for consistency. Feedback please.

plach’s picture

Status: Needs review » Reviewed & tested by the community

@Gábor Hojtsy:

the missing items are not there for historic reasons

Thanks for the info.

webchick’s picture

Version: 7.x-dev » 6.x-dev
Status: Reviewed & tested by the community » Patch (to be ported)

I can't believe that I'm actually committing a patch to core that includes the string "Lolspeak", but there you go.

Committed to HEAD. ;)

But this does raise an interesting point. I assume that localize.drupal.org will continue to evolve and gain more languages, which means more patches like this are inevitable in 7.1, 7.2... are these considered acceptable string freeze breakages? I assume so, since the freaking Drupal 6 maintainer uploaded a D6 patch up above. But we might want to document this somewhere.

Moving to D6.

mikl’s picture

Version: 6.x-dev » 7.x-dev
Status: Patch (to be ported) » Needs work

“English, British” just looks plain wrong. It should be either “English (Great Britain)” or British English. As for Lolspeak, should it not be “LOLspeak” or even “LOLspeek”?

And for consistency, I think we should use parentheses for German (Switzerland) and Portuguese (Internatioal) (and the rest of them) as well.

Gábor Hojtsy’s picture

@webchick: Yes, there is no other way to display the language names properly for those languages but to add them to Drupal core. So this will continue as new languages are added. If a new language is added but not yet in Drupal core, it will only show up as its language code in the installer, and people will need to add it manually on the locale UI (which is much more painful compared to the automated UI, where you just pick a language and it fills in orientation, language code, etc). Basically usability for the languages not added to core but on localize.drupal.org is very bad. So I'm glad we got these in.

Gábor Hojtsy’s picture

@mikl: I can only comment on Swiss German, which is quite a different language from German and not a dialect (that I know). So calling it German (Switzerland) would not be correct. Feel free to correct me.

Also, for Lolspeak, that is the "official" name of that language: http://speaklolspeak.com/page/LOLspeak+101

For the others, standardization of their name in either form would ideally involve the leads of the teams since they know traditions best. Unfortunately some traditions contradict, so I'm not sure we can achieve 100% consistency here. (But it can always be an endless bikeshed :)

webchick’s picture

I would just like to go on record stating that Professor Elfinugget has entirely too much time on his or her hands.

plach’s picture

Status: Needs work » Postponed (maintainer needs more info)
mikl’s picture

Status: Postponed (maintainer needs more info) » Needs work

#16: I stand corrected on the Swiss German part. I just remembered that it is called “Schweizerdeutsch” in German, indicating that it is indeed rather different. Wikipedia sums it up very well: “The dialects of Swiss German must not be confused with Swiss Standard German, the variety of Standard German used in Switzerland.”

As for LOLspeak, while that site has a mix of capitalisations, LOLspeak seems to be the most prevalent.

In any case, I still think “English, British” is horrible.

Xano’s picture

As a developer and an enthusiastic member of the Drupal community I like the idea of Lolspeak in core, but from a marketing perspective I think this is a no go. Drupal has become too popular to make the product itself funny. Languages on l.d.o are user-contributed, so it's fine to add Lolspeak and Klingon there, but in Drupal core we should stick to official (modern) languages.

plach’s picture

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

  • webchick committed b20e037 on 8.3.x
    #912218 by Gábor Hojtsy: Add missing languages present on localize....

  • webchick committed b20e037 on 8.3.x
    #912218 by Gábor Hojtsy: Add missing languages present on localize....

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

  • webchick committed b20e037 on 8.4.x
    #912218 by Gábor Hojtsy: Add missing languages present on localize....

  • webchick committed b20e037 on 8.4.x
    #912218 by Gábor Hojtsy: Add missing languages present on localize....

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

  • webchick committed b20e037 on 9.1.x
    #912218 by Gábor Hojtsy: Add missing languages present on localize....

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

tim.plunkett’s picture

Issue summary: View changes

Fixed HTML format

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

Version: 9.3.x-dev » 9.2.x-dev
Status: Needs work » Closed (outdated)
Issue tags: -localized install, -Needs backport to D7

This issue was committed to Drupal 6.x along time ago. It was reopened to discuss the Drupal 7 version. Looking at the current version of the file in Drupal 7, the changes are there.

I am closing this as outdated.