Browsing Spanish translation

172.

An in-text target can be achieved by placing the text to be linked within accent marks preceded by an underscrore: ``_`the internal reference```. Referencing is the usual ``:ref:`[text that is linked] <the internal reference>```.

173.

Translators beware

174.

Do not change the target for internal links that is placed between < >. If you do, the reference cannot be found. There should always be an explanatory text right before the pointy brackets. You can change that.

175.

Similarly, you can change the text for a URL but not the URL itself unless you want to replace it with a URL to a site in your language.

176.

If you translate the screenshots and other images, please ensure that you keep the folder structure of the 'images' folder as you can see in the respective branch of the manual version you are editing in `Git <https://git.mahara.org/user-manual/manual>`_, for example for `Mahara 18.10 <https://git.mahara.org/user-manual/manual/tree/18.10_STABLE/source/images>`_.

177.

You can find original images used for the manual in the folder 'images_original' and then their respective subfolders. You can use them for your own translations if you only want to exchange the background but keep the callouts.

178.

You do not have to redo any images that you do not 'translate', e.g. block icons, general buttons around Mahara and the text editor buttons. Any images that are not in your translation will be taken from the English original.

179.

The manual is updated once a day and new translation strings pulled in from Launchpad and images uploaded to Git prior to the compilation of the manual if there are any changes.

180.

If you want to mention the names of the main translators of the manual for your language, you can add a sentence right after 'The Mahara manual is written by Mahara community members.' That paragraph appears before the table of contents. There is no equivalent sentence in the English manual because it is not a translation.