Difference between revisions of "Help:Guidelines"
From Korean Wiki Project
DigitalSoju (Talk | contribs) |
DigitalSoju (Talk | contribs) |
||
| Line 7: | Line 7: | ||
<div style="border:1px solid #6805ca; background:#bfb5ca; padding:0;"> | <div style="border:1px solid #6805ca; background:#bfb5ca; padding:0;"> | ||
<div style="background:#9966cb; padding:0.2em 0.5em; border-bottom:1px solid #6805ca; text-align:center; font-size:125%; font-weight:bold;">[[Image:Write.png|35px]]General Guidelines</div> | <div style="background:#9966cb; padding:0.2em 0.5em; border-bottom:1px solid #6805ca; text-align:center; font-size:125%; font-weight:bold;">[[Image:Write.png|35px]]General Guidelines</div> | ||
| − | <div style="padding-top:0;">Korean Romanization should be used as little as possible except in beginners sections only. Try at all costs to avoid Romanization in other sections unless absolutely necessary. If you must Romanize, use the [[http://en.wikipedia.org/wiki/Revised_Romanization_of_Korean Revised Romanization of Korean]] system.</div> | + | <div style="padding-top:0;">One of the purposes of this wiki is to have all the content easy to understand. The articles should be dumbed down so the reader never has to scratch his head wondering. In most cases prior knowledge on a topic shouldn't be assumed and all content should be more focused on getting the reader to understand, rather than trying to sound linguistic expert.<br><br> |
| + | |||
| + | Korean Romanization should be used as little as possible except in beginners sections only. Beginners should be encouraged to learn Hangeul first before moving onto grammar and other sections. Try at all costs to avoid Romanization in other sections unless absolutely necessary. If you must Romanize, use the [[http://en.wikipedia.org/wiki/Revised_Romanization_of_Korean Revised Romanization of Korean]] system. If you want to talk about special pronunciation cases, in most cases you should use the IPA instead of Korean Romanization since Korean Romanization can cause improper pronunciation.</div> | ||
</div> | </div> | ||
| Line 16: | Line 18: | ||
<div style="background:#0099ff; border-bottom:1px solid #0166cb; padding:0.2em 0.5em; font-size:125%; font-weight:bold;">[[Image:New page.png|30px]]Creating and Naming Pages</div> | <div style="background:#0099ff; border-bottom:1px solid #0166cb; padding:0.2em 0.5em; font-size:125%; font-weight:bold;">[[Image:New page.png|30px]]Creating and Naming Pages</div> | ||
<div style="border-bottom:1px solid #0166cb; padding:0.4em 1em 0.3em;"> | <div style="border-bottom:1px solid #0166cb; padding:0.4em 1em 0.3em;"> | ||
| − | + symbol usage | + | *+ symbol usage |
| − | + | *On grammar patterns that can have a 요 ending, have the particular grammar's main page be the one with 요 in the title and have the others redirect to it. For example the grammar pattern [[V + (으)ㄹ래요]] would be the main page, while [[V + (으)ㄹ래]] would redirect to [[V + (으)ㄹ래요]]. (explanation needs to be rewritten) | |
| − | no spaces between slashes | + | *no spaces between slashes |
| − | no subject or object markers, if it's necessary list it on the page's content, not in the title | + | *no subject or object markers, if it's necessary list it on the page's content, not in the title |
Optional things, i.e. 이럴 수(가) 있다.. make the main page have the optional thing, then make a similar redirect without it. | Optional things, i.e. 이럴 수(가) 있다.. make the main page have the optional thing, then make a similar redirect without it. | ||
For 아/어/여 pattern, just use 아/어 for other patterns. | For 아/어/여 pattern, just use 아/어 for other patterns. | ||
Revision as of 03:41, 1 May 2009
|
| Help · Cheat Sheet · Community portal |
We would like to hear your opinions on formatting and guidelines of this wiki. Please voice your opinion in the discussion section.
General GuidelinesOne of the purposes of this wiki is to have all the content easy to understand. The articles should be dumbed down so the reader never has to scratch his head wondering. In most cases prior knowledge on a topic shouldn't be assumed and all content should be more focused on getting the reader to understand, rather than trying to sound linguistic expert.
Korean Romanization should be used as little as possible except in beginners sections only. Beginners should be encouraged to learn Hangeul first before moving onto grammar and other sections. Try at all costs to avoid Romanization in other sections unless absolutely necessary. If you must Romanize, use the [Revised Romanization of Korean] system. If you want to talk about special pronunciation cases, in most cases you should use the IPA instead of Korean Romanization since Korean Romanization can cause improper pronunciation.
Korean Romanization should be used as little as possible except in beginners sections only. Beginners should be encouraged to learn Hangeul first before moving onto grammar and other sections. Try at all costs to avoid Romanization in other sections unless absolutely necessary. If you must Romanize, use the [Revised Romanization of Korean] system. If you want to talk about special pronunciation cases, in most cases you should use the IPA instead of Korean Romanization since Korean Romanization can cause improper pronunciation.
 Creating and Naming Pages
Optional things, i.e. 이럴 수(가) 있다.. make the main page have the optional thing, then make a similar redirect without it. For 아/어/여 pattern, just use 아/어 for other patterns.  Sentence Examples
 Categorizing and Sorting
provide examples  Creating Redirectstba Posting Related Linkstba |
Grammar Patterns with Multiple Usages
 Posting Audio
 Colors
|
