Ferskil tusken ferzjes fan "Meidogger oerlis:Snakesteuben/Berjocht/Meidogger/follyglot"

gjin bewurkingsgearfetting
__TOC__
== FAQ ==
== Caveats ==
 
<div class="noprint" style="border: 1px solid blue; background-color: #FFFFAA; padding: 5px;">
Q: Why would anyone in her right mind do that?
(Frysktalige ferzje folgend tel; ik hoop.) Stub quality; very much in progress. Scratched together to explain my "vision" for this category/community, which exists across several projects/languages. <small>Recently tasked with porting a complicated template to "as many languages as you can," I believe this is a useful skill to search for.</small>
 
[[User:Snakesteuben|Winter S.]] ([[User talk:Snakesteuben|talk]]) 05:35, 23 March 2008 (UTC)
A: I am in no way saying that what the question presupposes is true, but...
</div>
 
In my case it's mainly templates and links. Stuff like: Porting a template to a new project, particularly where [[Like_this_one|redlinks]] show users trying to use that template where it doesn't exist. Tweaking tiny errors in ported/untested templates. Adding helpful [[w:InterWikimedia links|InterWikimedia links]], ''e.g.'', to the English language version of the same page if it's missing in the polyglot pane, etc., enz, itd/итд, etc., usw, o.s.v, itp., ...
__TOC__
== Caveats--Where should/shouldn't you contribute where your language skills are weak==
== Caveats ==
 
==='''know your audience'''===
(90% complete)
 
====What's the purpose of the project?====
Different communities have different norms. Some smaller communities are aggressively seeking content, and are happy to take it in pretty sloppy format. Recognising that it's easier to clean up grammar and suboptimally chosen words than to create content from scratch, they're quite gracious when you do your best and tack a "Help! Please clean this up for me!" in the discussion page.
Different wiki communities have different norms.
 
Some smaller communities aggressively seek content. They appreciate your good faith effort. They're happy to accept your submissions in less than perfect condition, since it's easier than creating content from scratch. They're gracious when you do your best and tack a "Help! Please clean this up for me!" in the discussion page. Somebody will eventually clean up grammar, translate interspersed English words, have a giggle while fixing words that are just plain wrong, and ask about or simply delete the occasional sentence that makes no sense whatsoever.
When I create an id on a new language project, I try to put xx-0 in my babel box right away. Then I'll see if I get a welcome message. Twice I've gotten a clueful one that even noticed my entry and responded appropriately. They were in this "sloppy help welcome" category. See, e.g., last line of this welcome message: http://nl.wiktionary.org/wiki/Overleg_gebruiker:Snakesteuben.
 
OnOTOH, thea otherprimary hand,purpose aof fewsome smallsmaller communitieswikis areis justcultural identity. They're as muchconcerned (ifwith notother more)goals, aboutfor culturalexample, identitypreserving thanan endangered language, as much as amassing content, if not moreso. Users on these sites tend tooften share fluency in one or more languagelanguages in addition to the project's language. They'reThere notare crazyfew aboutif contentany inusers mixedwho languages,can andread they'recontent notin likelyonly tothe beproject's aslanguage. gratefulSince forthey verydon't sloppyreally contentneed asyour arecontributions sitesfor wherethat somepurpose, memberswe arecan't 3+expect fluentthem into onlybe thatas language.grateful Forfor wantsloppy ofcontent aas betterthose term,who Ido. affectionately call these "boutique sites."
 
For want of a better term, I affectionately call these latter sites "boutique sites."
 
====How can you gauge a given wiki's receptiveness (or desperation)?====
 
When I create an id on a new language project, I try to put xx-0 in my babel box right away. Then I'll see if I get a welcome message. Twice I've gotten a clueful onewelcome that even noticed my entry and responded appropriately., Theymaking werespecific insuggestions thisof "sloppyhow helpan welcome"English category.speaker ''could'' See, econtribute.g., last line of this welcome message: http://nl.wiktionary.org/wiki/Overleg_gebruiker:Snakesteuben.
 
If you don't get a welcome, take a look around before you post something you're not sure of. Google on xx.wikyy.org for 'help English welcome contribution foreign language' yada yada. See if you turn up any express or implied policies, or pages written with you in mind in particular! E.g., courtesy of the exceptionally gracious Croatians: http://hr.wikipedia.org/wiki/Wikipedija:Kafi%C4%87/Foreign_languages and Dutch http://nl.wiktionary.org/wiki/WikiWoordenboek:Welcome_to_our_foreign_guests.
 
(alsoAlso explain how to look incheck the blocked/banned/deletion logs,. findMost theprojects have 2-4 mods with a bad attitudeattitudes. thatTake EVERYa projectquick has,look and see if language ispurity, form over function, etc., might be one of the bugs up their arse.)
 
==Specific contribution types==
=== Programming; Creating menus/templates inwhere your Babel xx-<1 == =
(40%)
 
Porting templates that require no native language content should always be OK, even on the boutique sites. If the template uses standard wiki language like "Template" and "User," in most projects, the standard English terms will work just as well as the native. For example, my Frisian user discussion page is http://fy.wikipedia.org/wiki/Meidogger_oerlis:Snakesteuben. finishBut laterif you go to my English discussion page and just replace the "en" with "fy" this gets you there, too. http://fy.wikipedia.org/wiki/User_talk:Snakesteuben.
 
But try to go one better when you can. SetIf you're inserting a link, set your display language to the language of the project, open the page you want, and see what the native word is. ...If lateryou're ..offering functionality, navigate to a similar menu choice on the site, and grab the verbiage from there the best you can. blahThe blah"all system messages" templates can be a goldmine for stock phrases in any project's language.
 
At very least you should do this for the menus. An example: (complex template draft in progress) http://fy.wikipedia.org/wiki/Meidogger:Snakesteuben/berjocht/ut/checkuser
 
(Disclaimer, I do know some Frisian. But I could have constructed the menu part even if I didn't.)
 
=== Hints for creating rudimentary content in a language with which you are unfamiliar ===
(in progress)
(10%)
 
I speak virtually no Croatian.
(I'll explain later how I used two similar entries and the links and articles linked in those entries to construct these.)
 
The Babel template pt-1 did not exist on the Croatian project. Creating the template using an example from another language was simple enough. blahBut as you know, Babel templates link articles on the subject language. I just ''couldn't'' leave those redlinks in something I created, y'know? blah
 
So, I examined similar templates and followed their links.
 
(to be continued)
 
== FAQ ==
 
Q: Why would anyone in her right mind do thatthis?
 
A: I am in no way saying that what the question presupposes is true, but...
 
In my case it's mainly templates and links. Stuff like: Porting a template to a new project, particularly where [[Like_this_one|redlinks]] show users trying to use that template where it doesn't exist. Tweaking tiny errors in ported/untested templates. Adding helpful [[w:InterWikimedia links|InterWikimedia links]], ''e.g.'', to the English language version of the same page if it's missing in the polyglot pane, etc., enz, itd/итд, etc., usw, o.s.v, itp., ...
169

bewurkings