|
|
16.
|
|
|
todo: for keeping a running ToDo list
|
|
|
|
|
takenlijst: voor het bijhouden van een takenlijst
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:26
|
|
|
17.
|
|
|
Buttons such as *Save* or *Copy page* and also portfolio sections such as *Content*, *Porfolio* etc. are highlighted as emphasized text (with a single \*).
|
|
|
|
|
Knoppen zoals * Bewaar* of *Kopieer pagina* en ook portfoliosecties zoals *Inhoud*; *Portfolio* enz worden benadrukt als vette tekst (met een enkele \*).
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:73
|
|
|
18.
|
|
|
Little buttons can be included in the text like |edit|, |manage|. They are added through a substitution. All replacements are kept in the file *shortcuts.rstext* which is included at the beginning of each file in which a substitution is used. They are referenced in the text as "*Edit* button |edit|" for example pointing out what the action is that you do with them.
|
|
|
|
|
Kleine knopjes kunnen in de tekst gezet worden, zoal |edit|, |manage|. Zij worden toegevoegd door vervanging. Alle vervangingen worden bijgehouden in het bestand *shortcuts.rstext* dat toegevoegd wordt aan het begin van elk bestand waarin een vervanging gebruikt wordt. Ze worden in de tekst gerefereerd als *Bewerk*-knop |edit| om bijvoorbeeld aan te tonen wat de actie is die er er kan mee doen.
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:29
|
|
|
19.
|
|
|
An index entry should be created for each section.
|
|
|
|
|
Er moet een indexverwijzing gemaakt worden voor elke sectie.
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:138
|
|
|
20.
|
|
|
New features receive an index entry as well in the form "single: New in Mahara 1.5; [the thing that is new]".
|
|
|
|
|
Nieuwe functies krijgen een ook index in de vorm "single: Nieuw in Mahara 1.5; [de nieuwe funchtie]".
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:31
|
|
|
21.
|
|
|
Long sections should be broken up into several pages to make the editing more manageable.
|
|
|
|
|
Lange secties moeten verdeeld worden over meerdere pagina's om het bewerken meer beheersbaar te maken.
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:55
|
|
|
22.
|
|
|
reStructuredText does not have a set hierarchy of heading levels. They depend on the individual files. However, to be consistent, the following convention exists:
|
|
|
|
|
reStructuredText heeft geen hiërarchische set voor hoofding. Ze hangen af van de individuele bestanden. Om consistent te zijn, bestaat volgende afspraak:
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:147
|
|
|
23.
|
|
|
Heading 1, e.g. 1.: ===============
|
|
|
|
|
Hoofding 1, vb. 1.: ===============
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:149
|
|
|
24.
|
|
|
Heading 2, e.g. 1.1.: ---------------
|
|
|
|
|
Hoofding 2, vb. 1.1.: ---------------
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:150
|
|
|
25.
|
|
|
Heading 3, e.g. 1.1.1.: ~~~~~~~~~~~~~~~
|
|
|
|
|
Hoofding 3, vb. 1.1.1.: ~~~~~~~~~~~~~~~
|
|
Translated and reviewed by
Koen Roggemans
|
|
|
|
Located in
../source/documentation_info.rst:151
|
