Browsing Ojibwe translation

25.

Each section that is related to a navigation menu item should have the path listed, e.g. *Content → Files*. It is best if you copy the arrow to get the correct one.

26.

Buttons such as *Save* or *Copy page* and also portfolio sections such as *Content*, *Porfolio* etc. are highlighted as emphasized text (with a single \*).

27.

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 in each file in which a substitution is used by placing "``.. include:: /shortcuts.rstext``" in the first line of the file. Substitutions are referenced in the text as "``*Edit* button |edit|``" for example pointing out what the action is that you do with them. Translators should not edit the substitution "``|edit|``" itself, but only change "``*Edit* button``" taking care to include the \* again without placing any spaces between the \* and the text.

28.

An index entry should be created for each section.

29.

New features receive an index entry as well in the form "single: New in Mahara 1.6; [the functionality that is new]".

30.

Long sections should be broken up into several pages to make the editing more manageable.

31.

reStructuredText does not have a set hierarchy of heading levels. They depend on the individual files. However, to be consistent, the following convention exists:

32.

Heading 1, e.g. 1.: ===============

33.

Heading 2, e.g. 1.1.: ---------------

34.

Heading 3, e.g. 1.1.1.: ~~~~~~~~~~~~~~~