BIBO and members from the BIBO group on Facebook say this printer should be run at 40-45mm/s and not the FDMprinter default of 60mm/s. BIBO provided test gcode files also show that they are setting 40mm/s in the slicer to create their test files.
This change sets the print speed override so the printer profile does not start at the FDMPrinter print speed default of 60mm/s but at the reccommended value of 40mm/s
Otherwise they don't get loaded.
These profiles didn't use any of the settings that were renamed or removed, so they can be upgraded with just their setting version.
Contributes to issue CURA-6774.
I'm not a native speaker of French or Portuguese but enough to make those corrections of not translating 'Trimesh'. I'm not an expert of the Korean language to fix that missing translation but I made do with someone who learnt it as a second language. I am an expert at Dutch so I made a couple of fixes there.
Contributes to issue CURA-6768.
The Japanese sentence with 'update existing' was confusing to the translators. I've asked for a better translation from a native. I'll improve the context for the next release.
This space triggers PoEdit to give a warning that the translation doesn't have the space there. That's okay, since it's a column and the space doesn't influence spacing then.
In theory it should be possible to add stages, but there is no possiblity to add any other stage in between. Therefore I moved the weights by 10+n*10. So we can add 10 before prepare and 9 stages between those 3 known stages.
It is probably possible to set the same weight to multiple stages, but I'm not sure how Cura decides, which stage to take first then. By the moment the plugin's init is called? Or by alphabet?
Therefore putting some space in between the weights should give some clearity.
... so don't use gl_PrimitiveID at all when in compatibility mode. This direct commit partly fixes github #6387 -- but see also the forthcoming PR in Uranium.
