Get our free book on rainwater now - To Catch the Rain.

Appropedia:Languages

From Appropedia
Jump to: navigation, search
Shortcut:
A:LANG
This is a proposed Appropedia policy. You can edit it, or discuss it on the talk page or at the Appropedia policy discussion page.
For now, this should be considered an essay by one or more Appropedians, and not as a policy or guideline.

Although Appropedia has started in English, we wish to welcome contributors in all languages. So far there is some material in Spanish, and within the Appropedia community of editors there at least a couple of other languages spoken (and this will no doubt increase).

Naming[edit]

The article should be created with a prefix for the language, followed by a colon, and the title in that language. For simplicity and clarity, use the same prefixes as in Wikipedia etc. So, for example, a page in Indonesian about absorption wells will have the title id:Sumur resapan.


When linking, it is important to add a colon before the language prefix, e.g. [[:id:Sumur resapan]].

The prefixes haven't taken off in use (and do look ugly), so simply name the article in the relevant language, and when we get subdomains the problem will become simpler. (added 08:11, 3 July 2010 (UTC) by Chriswaterguy)

Which languages?[edit]

All people should be catered for, ideally. Where people know more than one language, priority should be given to languages which are most widespread - for example, Indonesian rather than Madurese, and Spanish rather than Quechua. At the same time, if skilled literate users are eager to begin work in a target language, that is enough to begin the work.

This is a guideline, and not part of the official policy. There may be a good argument for putting certain practical pages such as how-tos into the mother tongue. And if a person is passionate about a language and wants to translate into that language, we are happy to encourage that.

Question: What are the minimum resources needed to support a language?[edit]

  • Presumably we need various resources in the target language, and they need to be verified as accurate and clear
    • disclaimer
    • copyright notices
    • basic help pages

Long-term solution: Subdomains[edit]

Ultimately we will probably want to use the same approach as Wikipedia, Wikibooks and Wiktionary, using subdomains (e.g. en.wikipedia.org for English, id.wikipedia.org for Indonesian, es.wikipedia.org for Spanish, etc). However, that requires being certain that there is a viable editing community in that language.

Separate subdomains will be (decided by consensus? approved by (a committee?) based on whether there is are enough active editors to justify a separate wiki.

Interlanguage links - "This topic in other languages"[edit]

While there are no separate subdomains, it is suggested that links to such articles are placed on the relevant page, under the heading "This topic in other languages" - which may be placed after "See also" and before "External links."

If Appropedia creates different subdomains for different languages, we can then imitate the interlanguage links approach used by Wikipedia etc, where for example [[id:Sumur resapan]] creates a hidden link, adding the link to the list of "this article in other languages" in the left column or under the page header.

Userboxes[edit]

Let people know which language you speak with a language userbox.

These have not been made yet. Should we import language userboxes wholesale from Wikipedia, or another Wikimedia project? Can we simplify categorization using bots? I suggest putting everyone who speaks a language into the basic category for that language, as well as into a subcategory. So, the base category should not be used specifically for native speakers, and there should be no userboxes that are as vague as just "This user speaks Swahili" - there should be some indication of level, or native-speaker status. It doesn't quite make sense to have subcategories with only one person. --Chriswaterguy · talk 17:56, 25 April 2007 (PDT)

See also[edit]


External links[edit]