Help:Formatting: Difference between revisions

Added Guidlines section, corrected a few other things
(→‎Useful Tips, Characters, and Codes: Added note about double spaces after perods.)
(Added Guidlines section, corrected a few other things)
Line 66:
:*253 ² (Squared)
: On Linux with German keyboard layout, the following key combinations will usually work:
:* AltGRAltGr + U: →
:* AltGr + ^: ¬
:* AltGr + Shift + Q: Ω
Line 100:
*To add superscripted text, put <nowiki><sup></sup></nowiki> around it. <nowiki><sup>example</sup></nowiki> shows <sup>example</sup>.
*To add subscripted text, put <nowiki><sub></sub></nowiki> around it. <nowiki><sub>example</sub></nowiki> shows <sub>example</sub>.
*When you add programming examples to a page, make sure you insert them in the proper alphabetical order.
:*Case-insensitive
:*Longer words come after shorter words that start with the same sequence ("bar" comes before "barber" and [[C]] comes before [[C++]])
Line 107 ⟶ 106:
This is not code.
This is totally code.
*Spelling and grammar count...PROOFREAD! Firefox has spell check built-in (tools → options → advanced tab → "Check my spelling as I type").
*Putting two spaces after a period (as is common practice) will only show up as one space when typing plain text. It basically wastes server space.
*If you change only a small portion of a page, check the "This is a minor edit" box so that people can filter out typo fixes when they search.
*If you have a question about something on a page, ask! Sometimes even we are wrong about coding, so if you think you see a problem or don't understand something, click the "discussion" tab at the top of the page and tell us about it.
*AddTo add your signature (<nowiki>--~~~~</nowiki>) to the end of messages on talk pages, and indent responses underneath previous messages:
 
Message 1.
Line 126 ⟶ 123:
 
*See [[Help:Contribute Content]] for more help on specific types of pages.
 
==Guidelines (not rules)==
*Spelling and grammar count...PROOFREAD! Firefox has spell check built-in (tools → options → advanced tab → "Check my spelling as I type").
*When you add programming examples to a page, make sure you insert them in the proper alphabetical order.
*If you change only a small portion of a page (correcting spelling, adding punctuation, etc.), check the "This is a minor edit" box so that people can filter out typo fixes when they search.
*Try to make the most of each edit. Five minor edits to a page in a ten minute span crowds the [[Special:Recentchanges|recent changes]] page.
*Try to add explanation in sentences to more complex examples. Write as if someone who has never heard of your language is reading.
Anonymous user