Updating and internationalizing documentation

I reread the old thread where PB discussed the pdf building process and why he stuck to it. It seems actually that rst2pdf gives more problems than anything also, albeit it's easy to use. But since I had some latex experience, I wasn't afraid to do the switch. I'm currently cleaning up the build process in my repo. One of the major problems was latex not being able to parse svgs, but I solved this and now the basic manual building works.
Please note I haven't done anything to the style files, so this is a pretty basic Sphinx look, which we can still adapt to our liking. And you will get your logo back if you want to

Translations will still be pulled from the same transifex project, we will only need to add a token for transifex to the DeviationTX travis settings. So if you want to you can continue work, but honestly I'd suggest we wait with translations (except some test ones I'll also do to test the multi language output) until we are in main repo in case something gets messed up (but which I think is pretty unlikely as it is already working pretty solid).

edit: the logo is back

I know, but I was just going through conf.py options when "latex_logo" struck me

@FDR How should we go on from here? Should I set up a temporary upload solution for all languages at a separate location and grant you write access to my fork, so we can test manual and transifex changes a little more?

Well, we are changing the english pdf for this, but except for minor glitches it is looking pretty good to me.

I will recheck everything, clean up the Makefile including zipping html directory (is that how you upload it to DeviationTX or could we also directly upload html manual?) and make a pull request.

I've made a pull request, as all is working fine except pushing back translations to the git repository.

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.

For PDF, after make latexpdf-release, devo8manual_en.pdf and all others can be found in pdf-devo8.

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

Well, why not use them? They are automatically build, so we might as well publish them.

You could make links to PDF and HTML on www.deviationtx.com/user-manual

I meant something like www.deviationtx.com/user-manual/en etc.

BTW: All Travis builds passed

Looking pretty good! Except the file naming. But we can fix that.

edit: the files size differences between old and new pdfs are amazing...