Arguments to avoid in language proposal discussions
 | This is an essay. It expresses the opinions and ideas of some Wikimedians but may not have wide support. This is not policy on Meta, but it may be a policy or guideline on other Wikimedia projects. Feel free to update this page as needed, or use the discussion page to propose major changes. |
When discussing the proposal for a new language edition of a Wikimedia project, certain arguments often come up that do not align with the Language Proposal Policy. Sticking to the policy helps keep discussions objective and separate from political influences.
Arguments to avoid (against)
[edit]It is not a real language; it is just a broken form of this other language
[edit]This misunderstanding overlooks how languages develop. Two varieties may come from the same ancestor, but that does not make one a “broken” version of the other. If two forms are not mutually intelligible and each has its own grammar, vocabulary, and sound patterns, they are considered separate languages or distinct varieties. Lower social prestige does not make a form any less valid for use in Wikimedia projects.
This language has only X speakers
[edit]Not every language is spoken by millions of people: thousands of languages are endangered, and some of those are on the verge of extinction. However, a small number of speakers does not necessarily imply that a Wikimedia project is useless, nor that it is doomed to fail, just like the existence of millions of native speakers are no guarantee for a successful project either. What really matters is that a sufficient number of native or proficient speakers are willing to work on it.
This language has a lot of variation
[edit]All living languages exhibit variation. This variation can manifest as regional dialects, social registers, or differences in spelling and pronunciation. The existence of multiple dialects or a lack of a single, widely-agreed-upon standardized written form is not a reason to reject a language proposal. The key factor is mutual intelligibility within the proposed language community. If regional dialects differ so much that speakers cannot easily understand one another, then separate projects may be considered for those varieties, in accordance with recognized linguistic authorities such as ISO 639-3, SIL International, Ethnologue, Glottolog, or other reputable academic sources.
The speakers of this language also know this other language
[edit]While it's true that many speakers of a less-resourced language may also be bilingual or multilingual and speak a more dominant language, this does not justify denying them a project in their preferred language. Not all speakers are bilingual, and proficiency levels in the second language can vary significantly. More importantly, offering content in a user's primary or preferred language increases their ability to consume and contribute knowledge authentically and effectively. Users should have the autonomy to choose the language in which they wish to engage with and contribute to Wikimedia content, which is a core principle of accessibility and inclusivity.
This will cause division among speakers of this other language
[edit]The idea that approving a specific language would fracture the broader language or national community is largely speculative. Recognizing a minority or regional language is about providing access to information in the community’s preferred language. It acknowledges linguistic diversity without causing division. Ensuring people can access knowledge in their own language supports inclusion and does not threaten unity. Concerns about political consequences should not block efforts to create valid language projects that serve their speakers.
Nobody I know will want to contribute to this project
[edit]Many languages begin with few editors because digital content and community involvement are initially limited. Wikimedia projects aim to help grow these communities by providing a space to create and share knowledge. A test project helps demonstrate genuine interest and the potential for contributors over time. Without such a trial, dismissing a language proposal based on current or speculative future contributor numbers is premature.
No official standardization of this language exists, so writing in this language is like original research
[edit]This argument fundamentally misapplies the "No original research (NOR)" principle found within Wikimedia projects. The NOR policy applies to content creation within an existing project (e.g., prohibiting editors from adding unpublished theories or personal analysis to a Wikipedia article). It does not apply to the establishment of a new language project itself or the collaborative process of developing a written standard. When a community proposes a project for a language with little to no written ortography, the community is free to adopt or develop a standardized orthography that works for them.
This is my own mother tongue and I am against a project in this language
[edit]This argument is based on personal preference, not policy. Often, someone making this claim is already proficient in another language and can comfortably use some of the other existing Wikimedia projects in that language. However, not all speakers of the language have that same proficiency, and many benefit from access to information in the proposed language. Similarly, the project will benefit from their contributions. The Language Proposal Policy focuses on linguistic criteria, not personal preferences.
Arguments to avoid (in favor)
[edit]This language used to be the official language of a great empire
[edit]Historical prestige or former official status is not a valid reason to approve a language proposal. Wikimedia's language proposal policy requires that a language be currently living, meaning it has an active community of real speakers using it naturally in everyday communication.
We need a separate project because some users write this language in a different script
[edit]Having a different writing system does not justify creating a separate Wikimedia project. The language proposal policy treats languages, not scripts, as the basis for new projects. If a language is written in multiple scripts, those varieties are not eligible for separate projects. Instead, Wikimedia uses script converters (formerly called language converters), which allow readers and editors to switch seamlessly between scripts while editing within the same project. This avoids content duplication, prevents communities from being split artificially, and ensures that all contributors continue working in one unified project while still accommodating different writing systems.
This language deserves a separate project, because some other language has a separate project, too
[edit]The existence of a separate Wikimedia project in one language does not automatically entitle another language to have one as well. Before the Language proposal policy was introduced, several projects were created that would not meet today's requirements for creating a new project. Examples are ancient languages, constructed languages without a substantial user base, "simple" versions of existing projects, and historical or otherwise alternative orthographies of existing languages.
This language definitly needs its own project
[edit]While this argument is not invalid in itself, it should never be used as an argument for submitting a proposal. Unless you are proficient in the language or, at the very least, maintain close contact with its native speakers, you should not propose a project just because you think it would be a nice idea to have one. After all, the viability of a project is determined by people who are both competent and willing to work on it.