Using the same original image files
Ideally, we try to use the same image file as was in the original article. For example, in the translation of article 3336, the images will be retained as-is, that is, they are called using the same links (
<img2048|center>) as in the original article. In order that these images can also be used for every language, they are not assigned any title nor any description.
Translating the text in the images
Wherever possible, we avoid creating images that embed text. If a textual explanation is necessary, it is better to put it into the fields made available for the ("title" and "description") to make it easier to do the translations. In this way, a diagram that requires explanations will be easier to translate if it includes includes reference numbers, and that the explanations corresponding to those numbers are referenced in the description field: we then only need to made a copy of the image file for us to be able to translate the title and description directly in private zone, which eliminate any need to use an image editing programme at all.
Nonetheless, it is sometimes necessary to "translate" some images when they actually do contain text. To translate the few textual images included in SPIP’s documentation, you will need to use an image editing programme.
For example, the document above was created using Fireworks based on the French image (in the original article 877), but with the text translated into Spanish (for the translated version in article 93). You can reuse such a document if it can help you quickly make a translation into another language.
Screen shots in the right language
Numerous illustrations in the documentation are screen shots of SPIP’s private zone. When there is text visible in such images, it is better to create a new screen shot in the same language as that of the article which will embed that image, as a way to make that image relevant and useful to the reader.