Browsing Korean translation

9.

should have as few instructions as possible about the steps that are to be taken in them. Preferably, only the step numbers so that they can be exchanged more easily and the text of the steps is translatable because it is text and not part of the image. That could also mean that translators can translate the steps but don't immediately have to change the screenshots.

10.

|new in Mahara 1.6| get callouts that are created in Gimp with the `script <https://mahara.org/view/view.php?id=60234>`_ that Iñaki adapted.

11.

that have callouts refer to the steps that need to be taken and that are explained below the figure.

12.

should only show the necessary area and not the entire screen or URL address bars etc. where not necessary.

13.

Most screenshots are added with the *figure* directive:

14.

Example of including a screenshot

15.

The first line provides the path to the file. The \* replaces the file extension and Sphinx chooses the file that is most appropriate. Thus, files could have different image extensions or you could have the same screenshots in different file formats that are then chosen by the programme to best suit the end format of the manual.

16.

The second line represents the alt text that is dispalayed when hovering over the image, when no images are displayed or when viewing the page via a screen reader.

17.

The third line must follow an empty line. This is the text that is displayed below the screenshot as figure description. In the PDF output, the descriptions will be numbered continuously.

18.

If you want to include an image inline with the text and don't want to or can't use the regular figure, you should create a substitution and place it into the shortcuts.rstext file.