v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Difference between revisions of "User talk:N9103"

From Dwarf Fortress Wiki
Jump to navigation Jump to search
m (WTF is with this auto-ToC?)
Line 1: Line 1:
 
 
== Test Space ==
 
== Test Space ==
 
Anyone care to point me to how to get rid of an automatic ToC, other than removing sections?
 
Anyone care to point me to how to get rid of an automatic ToC, other than removing sections?
 +
:From Wikipedia (http://en.wikipedia.org/wiki/Help:TOC#Creation_and_numbering_of_sections):
 +
:(outdent due to quoting)
 +
Table of contents (TOC)
 +
For each page with more than three headings, a table of contents (TOC) is automatically generated from the section headings, unless:
 +
 +
(for a user) preferences are set to turn it off
 +
(for an article) the magic word __NOTOC__ (with two underscores on either side of the word) is added in the edit box
 +
When either __FORCETOC__ or __TOC__ (with two underscores on either side of the word) is placed in the wikitext, a TOC is added even if the page has fewer than four headings.
 +
 +
With __FORCETOC__, the TOC is placed before the first section heading. With __TOC__, it is placed at the same position where this code is placed. This allows any positioning, e.g. on the right or in a table cell. In old versions of MediaWiki, it also allows multiple occurrence, e.g. in every section (However, this seems only useful if the sections are long, so that the TOCs take up only a small part of the total space.).
 +
 +
There may be some introductory text before the TOC, known as the "lead". Although usually a heading after the TOC is preferable, __TOC__ can be used to avoid being forced to insert a meaningless heading just to position the TOC correctly, i.e., not too low.
 +
 +
Using __NOTOC__ it is possible to disable the normal Table of Contents. Section links as explained below allow to create compact ToCs, e.g. alphabetical [[#A|A]] [[#B|B]] etc.
 +
  
 +
:in short, try  __NOTOC__ near the top of the page.[[User:GarrieIrons|GarrieIrons]] 06:48, 4 January 2008 (EST)
  
 
== Comments/Opinions/Rants Welcome Here ==
 
== Comments/Opinions/Rants Welcome Here ==

Revision as of 11:48, 4 January 2008

Test Space

Anyone care to point me to how to get rid of an automatic ToC, other than removing sections?

From Wikipedia (http://en.wikipedia.org/wiki/Help:TOC#Creation_and_numbering_of_sections):
(outdent due to quoting)

Table of contents (TOC) For each page with more than three headings, a table of contents (TOC) is automatically generated from the section headings, unless:

(for a user) preferences are set to turn it off (for an article) the magic word (with two underscores on either side of the word) is added in the edit box

When either or

(with two underscores on either side of the word) is placed in the wikitext, a TOC is added even if the page has fewer than four headings.

With , the TOC is placed before the first section heading. With , it is placed at the same position where this code is placed. This allows any positioning, e.g. on the right or in a table cell. In old versions of MediaWiki, it also allows multiple occurrence, e.g. in every section (However, this seems only useful if the sections are long, so that the TOCs take up only a small part of the total space.).

There may be some introductory text before the TOC, known as the "lead". Although usually a heading after the TOC is preferable, can be used to avoid being forced to insert a meaningless heading just to position the TOC correctly, i.e., not too low.

Using it is possible to disable the normal Table of Contents. Section links as explained below allow to create compact ToCs, e.g. alphabetical A B etc.


in short, try near the top of the page.GarrieIrons 06:48, 4 January 2008 (EST)

Comments/Opinions/Rants Welcome Here

Problems/Mistakes/Corrections

Forgive me for the occasional slip up. Just make a note here of where I managed to screw up, so that I may endeavor to learn from my mistakes.--N9103 15:54, 23 December 2007 (EST)

Flames Go Here