Requests for new languages/Wikisource Tagalog

From Meta, a Wikimedia project coordination wiki

Tagalog Wikisource[edit]

submitted verification final decision

This language has been verified as eligible.
The language is eligible for a project, which means that the subdomain can be created once there is an active community and a localized interface, as described in the language proposal policy. You can discuss the creation of this language project on this page.

Once the criteria are met, the language committee can proceed with the approval.

If you think the criteria are met, but the project is still waiting for approval, feel free to notify the committee and ask them to consider its approval.

  • The community needs to develop an active test project; it must remain active until approval (automated statistics). It is generally considered active if the analysis lists at least three active, not-grayed-out editors listed in the sections for the previous few months.
  • The community needs to complete required MediaWiki interface translations in that language (about localization, translatewiki, check completion).
  • The community needs to discuss and complete the settings table below:
What Value Example / Explanation
Proposal
Language code tl (SILGlottolog) A valid ISO 639-1 or 639-3 language code, like "fr", "de", "nso", ...
Language name Tagalog Language name in English
Language name Tagalog Language name in your language. This will appear in the language list on Special:Preferences, in the interwiki sidebar on other wikis, ...
Language Wikidata item Q34057 - item has currently the following values:
Item about the language at Wikidata. It would normally include the Wikimedia language code, name of the language, etc. Please complete at Wikidata if needed.
Directionality LTR Is the language written from left to right (LTR) or from right to left (RTL)?
Links Links to previous requests, or references to external websites or documents.

Settings
Project name "Wikisource" in your language
Project namespace usually the same as the project name
Project talk namespace "Wikisource talk" (the discussion namespace of the project namespace)
Enable uploads no Default is "no". Preferably, files should be uploaded to Commons.
If you want, you can enable local file uploading, either by any user ("yes") or by administrators only ("admin").
Notes: (1) This setting can be changed afterwards. The setting can only be "yes" or "admin" at approval if the test creates an Exemption Doctrine Policy (EDP) first. (2) Files on Commons can be used on all Wikis. (3) Uploading fair-use images is not allowed on Commons (more info). (4) Localisation to your language may be insufficient on Commons.
Optional settings
Project logo This needs to be an SVG image (instructions for logo creation).
Default project timezone Continent/City "Continent/City", e.g. "Europe/Brussels" or "America/Mexico City" (see list of valid timezones)
Additional namespaces For example, a Wikisource would need "Page", "Page talk", "Index", "Index talk", "Author", "Author talk".
Additional settings Anything else that should be set
submit Phabricator task. It will include everything automatically, except additional namespaces/settings. After creating the task, add a link to the comment.

Proposal[edit]

This would be the perfect place for Tagalog literature, and their official translations from different languages and vice versa.

A Filipino version of Wikisource may be a companion for this. While tl.wikisource would contain classical writings, fil.wikisource could sport modern, published literature.

Discussion[edit]

Arguments in favour[edit]

  • Support, but without the proponent's Tagalog-Filipino split. The Tagalog Wikisource can easily handle both types of texts. --Sky Harbor (talk) 09:10, 3 November 2010 (UTC)[reply]
  • Support, specifying that this is the Filipino version of Wikisource while stressing the need for another written in Baybayin.--23prootie 00:17, 21 November 2010 (UTC)[reply]
    Comment We DO NOT need to distinguish the two. What exactly is the point of a Baybayin Wikisource if they can coexist in a single Tagalog Wikisource anyway? Because there is a corpus of Baybayin Tagalog text, I can see the point of coexistence in Wikisource given that it is a free repository of texts (there can be a single text, like the Doctrina Christiana, in Baybayin, the Abecedario, the Filipino alphabet and in Spanish). However, what I find utterly ridiculous is that there are few Filipino Wikimedians as it is actively editing the projects, and we have to resort to splintering the community along the basis of script simply because there is a revivalist movement which isn't even endorsed by the mainstream organizations advocating the use of regional languages. If ever, not only is this useless (since almost ALL Filipinos write using the Latin script anyway), but worthless as well (again, since almost all Filipinos write and read in the Latin script). --Sky Harbor (talk) 11:38, 25 November 2010 (UTC)[reply]

Arguments against[edit]

  1. Oppose --Pitpisit (talk) 09:09, 15 May 2017 (UTC)[reply]

Other discussion[edit]

  • Florante at Laura exists at tl.wikibooks. Perhaps this can be moved to this proposed Wikisource and serve as the needed test project? --Icqgirl 14:41, 21 April 2011 (UTC)[reply]
    • The Florante at Laura Wikibook is supposedly a textbook which incorporates interpretations of the text. I think we can keep both in their respective places, especially as Wikibooks develops to incorporate more Tagalog-language textbooks. --Sky Harbor (talk) 05:13, 11 May 2011 (UTC)[reply]
  • Currently the localisation is completely done. However I did not find a test project at Wikisource, so you should start one if you want to get the Tagalog Wikisource approved. SPQRobin (talk) 14:58, 21 April 2011 (UTC)[reply]
    • There are Tagalog-language texts on the multilingual Wikisource, but there's no Main Page yet. I'd make one though if I have the time and if I wasn't splitting myself between the three existing Tagalog projects, plus other responsibilities. :P --Sky Harbor (talk) 10:02, 25 September 2011 (UTC)[reply]