Standardize the language selector for the Philippine language.

if i'm reading it correctly, the local and international version should both be written as Filipino.

Reading several publicly available resources, I don't believe there is a case of removing Tagalog when adding Filipino. The relationshop between the two remains unclear at this time, and both have legal ISO639 codes.

Your patch is not created from the root Drupal directory, so the test bot cannot apply it. See http://drupal.org/patch/create for more information.

Standardizing the language selector for the Philippine language need another run through. It is right to consider that Filipino is the "safe" language to use (in contrast with Tagalog which is still a prevalent living language in many regions of the Philippines). Unfortunately, implementation by other language-related projects to "fil" (which is defined by ISO 639-1 and still has no ISO 639-2 & 639-3 entries) would also have a good debate on this topic.

However, in my strong opinion is that we should not deprecate Tagalog (tl) simply because we have a good reason to initialize Filipino (fil). A lot of other open source projects have massive code base for tl than fil at the moment. Transition may come gradually on a need basis (or until the Philippine government tackles the topic --which is so not happening in 20 years or so due to the slow IT growth & development in the country). To further rationalize, both Philippine dialects are referred to as "living languages" which means that they will grow in their own means. It is safe to say that they deserve distinct l10n workspaces. Redundancy (which is commonly feared in i.t. projects) is accepted in some cases for fil / tl words. It is also true that both have same words with different meanings and/or usage (I'm from a Tagalog-speaking region so I'm 100% confident about this).

With that I humbly object to the task of "removing Tagalog" on Drupal.org. Separate project work-spaces for Tagalog (tl) and Filipino (fil) is highly encouraged.

@JohnNoc:
Since we both gave good arguments about this and there's really nothing wrong about it, let's find a way to endorse the issue to someone who has better code access.

Let's both try to contact goba or webchick in order to formally patch this up for Drupal 7 (and hopefully for Drupal 6 as well).

"Filipino" replaces "Tagalog" on the Drupal project.

Hmm.. I'm not a Drupal user but since the topic is about updating the language selection "Filipino vs. Tagalog", and since there (really) is an effort in mass updating many FLOSS apps (2 or 3 Linux distros will soon switch to "fil"), I'd like to give my share and from what I have gathered so far (from digging and talking to professors).

1) The line is drawn by way of identifying if "borrowed" letters were used. If there are, it is part of the "Ang Bagong Alpabetong Filipino", which is the "Filipino Alphabet" - 28 letters in all. Tagalog language doesn't have these borrowed letters, this is what we know as ABAKADA.
2) Filipino is not a rename of "Pilipino". However, "Pilipino" was a rename of "Tagalog", an attempt to make "Tagalog" the National Language by detaching it to the Tagalog region. It was still opposed because it's clearly just Tagalog under a new name.
3) Filipino, as per the constitution (I can't remember right now which one), was created to solve the debate and to fulfill the formation of having a (true) National Language. It was simply stated that Filipino is the National Language, NO statements were written that says it was a 'renamed' Pilipino language, or that it is mainly Tagalog.

Sad to say, (I think because of budget), the Commission on the Filipino Language weren't able to do much to develop the new, neutral, unbias "Filipino" language. Thus it ended up being mainly Pilipino/Tagalog. Development is going on, but it is slow. Universities were given some power for its development especially in the areas of translating scientific terminologies into Filipino.

One must also remember that, the "Filipino" language is not restricted to Tagalog only, as compared to "Pilipino" which is strictly "Tagalog" (hence, renamed). Filipino is a neutral language, in other words, we can pick words from any Philippine Languages and use it for "Filipino". "Filipino" translators should consider that (since there are no guidelines from the powers that be - CFL/KWF).

My personal guideline, since Filipino is mainly Pilipino/Tagalog and there's nothing we can do about it anymore then:
1) If there are direct translations in more than one Philippine Languages, pick the most fitting word that best describes the word or terminology being translated into Filipino;
2) If there is no direct translation in any Philippine Languages, then time to transliterate into "Filipino". Example: komputer/kompyuter, extensyon (ekstensyon/ekstensiyon = Tagalized IMO, not Filipinized; remember we have a letter 'X' in Filipino).
3) If a word being translated is better left as-is, then leave it. Examples: username (if there's a Cebuano or Bikolano or Moro translation of 'username' then follow #1 above), podcast, website, Massively Multiplayer Online Role-Playing Game, etc. [you get the idea]

Tagalog is ABAKADA. And that's another reason besides the political reason stated above, why "Filipino" was born/created from scratch (supposedly), we need and it is better to use the borrowed letters.

Disclaimer: My research is in no way authoritative on this matter. I'm simply sharing what I have gathered and learned so far.

Here's a patch for current D7 HEAD. The languages have been moved into iso.inc.

@JohnNoc, you were on the right track, but in your patch, the "includes/" needed to be added on the lines:

--- locale.inc	22 Feb 2009 17:55:29 -0000	1.205
+++ locale.inc	28 Feb 2009 04:02:37 -0000

like in this patch...

--- includes/iso.inc	30 Jul 2009 10:14:17 -0000	1.4
+++ includes/iso.inc	25 Aug 2009 04:44:09 -0000

Fascinating discussion...

HEAD is broken.

Cleaning-up the "locale module" issue queue as per http://cyrve.com/criticals.

Looks like agreement has been reached on replacing Tagalog with Filipino, and patch still applies, so marking as RTBC.

Thanks for the great investigation work in this issue!

Needs work because we need an upgrade path from tl => fil since this is a change to database records. (I also thought that there was a problem with the link at the top of the http://api.drupal.org/api/function/_locale_get_predefined_list/7 but I was reading it wrong since I was in a hurry. :))

Updated patch.

webchick is asking for an update function in locale.install to update the {language} table content to match the new name/code/prefix

Would this also need to be updated everywhere langcodes are used? {node}, {url_alias}, etc?

@Dave Reid: yes, sure, not an easy task AAMOF

Edit: I proposed in the past to introduce numeric ids for languages for performance reasons, this would be yet another valid use case, but it's definitely too late now

@plach Thanks! I didn't expect that. :) Anyway, here is an update patch for locale.install, is that how should be written? This is my first D7 patch, so accept the excuse for any mistakes! ^_^

Right, we need to update other tables like what @Dave Reid mentioned.

@nathanjo:

You must provide a single patch holding all the needed changes.

+++ modules/locale/locale.install	2 Sep 2010 15:11:09 -0000
@@ -111,6 +111,18 @@
+ * Update for the Philippine language

This needs to be a little more descriptive. Moreover the final dot is missing (see http://drupal.org/node/1354#functions for the documentation coding standards).

+++ modules/locale/locale.install	2 Sep 2010 15:11:09 -0000
@@ -111,6 +111,18 @@
+      'language' => 'fil'

Also the name and native columns should be updated if I have read the issue right, all the other interested tables should be updated too.

Powered by Dreditor.

Update:

• Update the name and native columns
• Added more description.
• Update language from other tables.

[Updated] - Some coding standard fixes.

@nathanjo:

You have to put also the changes to iso.inc into this patch (only a single patch will be committed).

+++ modules/locale/locale.install	2 Sep 2010 17:11:44 -0000
@@ -111,6 +111,110 @@
+ * Standardize the Philippine language from tl => fil.

I'd suggest 'Standardize the Philippine language from "tl" to "fil".'

+++ modules/locale/locale.install	2 Sep 2010 17:11:44 -0000
@@ -111,6 +111,110 @@
+    );

Wrong indentation.

+++ modules/locale/locale.install	2 Sep 2010 17:11:44 -0000
@@ -111,6 +111,110 @@
+  // Update comment language ¶

All the inline comments have a trailing whitespace instead of a trailing dot.

This will cover the update from D6 sites to D7: many tables above did not exist in D6 or did not have the language column. We need to check this (and testing this properly).

Powered by Dreditor.

[Update]
Added update patch for d6.

I'm sorry, I wanted to RTBC this myself, but all of the sudden I found myself thinking about the upgrade path problems that all the sites previously using the 'tl' code might experience: every single contrib module dealing with language codes should introduce an upgrade path for this. I ain't sure this is a viable solution, I guess we need a committer feedback about this.

Edit: Perhaps we just want to add the 'fil' language code and introduce a list of deprecated/legacy language codes that would be used only on upgraded sites.

Changes are performed in the development version first, backported then.

Perhaps we don't acutally need an upgrade path here: after all any language not listed in iso.inc is actually a custom language but works exactly as a predefined one. It would be interesting if someone could test just the change to iso.inc in a site having the 'tl' language enabled: everything should keep working exactly as before.

Filipino was added and shipped in Drupal 7 via #912218: Add missing languages present on localize.drupal.org. Not sure if this issue has relavance anymore? (Tagalog was not removed there but as people pointed out it might be needed for backwards compatibility).

locale.inc_.patch queued for re-testing.

#41: fil_update_d7.patch queued for re-testing.

standard_language_list has filipino defined instead of tagalog in D8 so assigning to D7.

updating the issue summary (instructions) will help get the committer feedback this needs.

Based on #45, the only BC change here has already been made in D7 and it's no longer relevant for D8, so closing wontfix.