Updating and internationalizing documentation

Ah, I see, that is still only your fork. (At least I hope it is a fork, not a simple copy....)
In your fork you could simply commit the changes directly, and after that create a pull request to the main deviationTx/deviation repository.
So now you can merge it, and create a pull request to deviation.

You can learn more about the docker environment here:
www.deviationtx.com/wiki/development/docker
Note, that since you have an own GitHub fork, you need to create the docker container pointing to your existing GitHub directory outside the docker...

Almost.
You have merged your own pull request into your own repository, but you still need to create a new pull request to the deviationTx/deviation repository.

Just go to your repo, and click on the Pull request link on the upper right, under the buttons.
All the default values should be right, and the results would look like this:
github.com/DeviationTX/deviation/compare...er...Morlacus:master
Then click on the big green button to create the new pull request, and that's it...

@Moeder
What file naming convention do I need for the translated images?

Yes, now it is fine.
Goebish can check better if it is valid, and will merge it.

It is possible to use translated images, which I plan to make, but forgot how should I name them, so they can be recognized...

I've checked the file name convention for the translated images, it is:
<base_name>.<language>.<extension>

For example if the original filename is:...then your translated one should be named:

Despite I agree that the sub-directory structure is nicer, actually renaming them in the same directory was easier. I didn't need to copy or remember the file name when saved the new image, but selected the old one in the SaveAs dialog, and just added the language tag.
So far I've only uploaded a few, so I can easily change them to the subdir structure if you wish...

I'm glad you think this way, because I've just uploaded a bunch of translated Devo8 images.
Now I'm translating the SVGs, then will continue with the B&W images.
Actually most of the SVGs are outdated, and so far I haven't tried to replace the image in them, only translated the text in the boxes...

Yes, the best way is to use the emulator, and reproduce the screen shown in the english version, then make a screenshot (Alt+PrintScreen). You will need an image editor to cut out the screen portion. I use Photoshop, because I can save the selection, and reapply for each new screenshot, but probably there are aother easy ways to do that.

Save as 8bit PNGs without transparency so save space, and name them as the original was, but with the added language tag, like this:
<original_name>.<language>.<extension>
For example:
model_menu.fr.png

To upload them there are more ways, just like in case of the language file were:

1. You can go into the image directory of the source, for example:
github.com/DeviationTX/deviation-manual/...es/devo8/ch_advanced
Then click on the "Upload file" button on the upper right, choose your files, gice a commit message (and a description if you like), choose the "Create a new branch for this commit and start a pull request." option, and press the "Commit changes" button.

2. If you have a GitHub fork of the deviation-manual repository, and an up-to-date local repository, then simply add the proper imager into the appropriate foldes, use "git add ." to include them, make a commit to your repo, push your changes back to your fork, and then make a pull request from there to the main deviationTx/deviation-manual repository.

The SVG files are harder. So far I only translated the additional texts in the boxes, which are simple XML content. You can use any editor (like notepad++) to edit them, and check the result in a browser.
So far I had no luck with the SVG editors, but I haven't yet gave up on them...

Moeder wrote: In HTML builds, after make html-release the files en.zip, fr.zip etc. Are found in html-devo8 (or 10), each zip contains the subdirectory html-devo8-en and so on.

...

We can change the output process in Makefile if you prefer something else for the upload script.

@Moeder:
Could you change the name of the HTML zip files in the build script to match the directory name they contain?
So they would called like for example: html-devo8-en.zip

Thanks!