Index Test
1 Explanations
This chapter contains a lot of explanations for terms
↓, which you might want to
↓look up later
↓. Because better sooner
↓ than later, although later
↓ has been repeated twice
↓. Actually, thrice
↓ now.
Do you not want to look any of them up
↓ right now? No problem. You will be able
↓ to do it later, in the index
↓.
Now we will add two cites in one, just because
2,3.
As we will see in
3↓, not everything is clear.
1.1 Magical type face changes in the world
Little more can be added, at least at this point.
1.2 Color and colour
At this other point, however, more could be added, but won’t.
2 Nomenclature
We should explain what an index
↓ is. We can do that with the nomenclature
↓. Normally we will want to mix index
↓↓ and nomenclature terms. But what happens if we actually do? We will know later
↓, when we generate
↓ the file.
2.1 Reminder
We have to remind the reader that things will be remembered
↓.
2.2 Remainder
Whatever remains should be explained
↓ here.
3 Bulk
We actually need a lot more text
↓ in order for our index
↓ to have more terms
↓; so we can find out if the links
↓ are working. Since they are anchors
↓ inside the page
↓, they might otherwise just take us to the
↓top of the page, and we would not like that.
Yes, it would be bad for us. But on the other hand
↓ too much text
↓ can hide
↓errors. So not much more text
↓ is needed.
Thanks for reading us.
Nomenclature
↑generate An activity that requires a source and a destination, something like eLyXer does with files.
↑index A list of terms with a reference to where they occur.
↑nomenclature A list of common words with an explanation.
Bibliography
[1] WordReference.com: “definition of elixir”, accessed March 2009. http://www.wordreference.com/definition/elixir
[2] W3C: “HTML 4.01 Specification”, 24 December 1999. http://www.w3.org/TR/REC-html40/
[3] W3C: “HTML 4.01 Specification”, 24 December 1999. http://www.w3.org/TR/REC-html40/