I don't know the name for "Wechsellaufwerk" in english, but these devices are not meant to be USB-sticks.
Some PC cases have the possibility to remove a CD drive and you can e.g. replace it with a HDD.
Such devices are really called "Wechsellaufwerk", but the meaning here is "Wechseldatenträger".
Don't see a reason, why we should translate "m" > "meter" -> "Meter" here.
Additionally the tranlation for "0.0m" is untranslated while "m" is translated as "Meter".
So I reverted this here.
Of course most people might now what the meaning of X-Ray is, but I would translate it, because first it sounds more professional than using anglicisms.
* Because these keywords got translated the code can't replace them with values.
* Basicly the idea having these keywords in translation files is just to change the order of them (according to the culture and the region, where another order would be expected).
-> So reverted the translated keywords for german and french.
* Originally taken from my own packaging of Cura on launchpad: ppa:thopiekar/cura - https://launchpad.net/~thopiekar/+archive/ubuntu/cura
* It adds mime-types, which are supported by Cura, to the mime-database, so filemanagers can recognize these files.
* This sharemimeinfo includes currently 3MF, STL and OBJ.
As I upgraded my computer to a developer version of Ubuntu, I noticed that the OpenGL module, which is needed for our workaround, is currently broken.
So I browsed the web and found the reason why it is needed at all and found a alternative.
The reason for the problem is that Qt5 is dynamicly loading libGL.so instead of libGL.so.1, as the OpenGL module loads libGL.so.1.
So if you install the closed-source nvidia drivers it only creates a link from libGL.so.1 to it's binaries and the result is that PyQt5/Qt5 tries to load Mesa binaries together with NVidia binaries.
By importing the OpenGL module you preload the libGL.so.1, but this can also be done directly by using ctypes.
* Replaced the OpenGL fix with the ctypes fix
* Added a TODO
This should be obvious. The thought process was that now we're using the builder instead of making the MeshData object directly, but that has only relevance if you still remember what the old code was.
Contributes to issue CURA-625.
