These are the result of running the lionbridge_import.py script on the translation files that we received from Lionbridge through Smartling. It contains the new translations for Cura 4.7.
Contributes to issue CURA-7622.
This reverts commit 458acb356f11f50c3327b5af0be8531fb761548f.
The change was wrong. The code refers to PrinterOutputModel.extruders which is not deprecated, not to GlobalStack.extruders (which is deprecated).
Fixes#8204.
Previously this was disabled because you should probably use the ZigZag pattern then. But I'm enabling it now because of two inconsistencies:
* The setting still works. So you can change the setting by switching to grid, triangles, cross or gyroid, then switch back to lines and still get connected support lines.
* The same happens with the infill patterns, where this setting is visible for the lines pattern.
Rather than changing the other two things (which involves changes to CuraEngine too to make it ignore the setting value for the lines pattern), I've opted to change it here and fix both inconsistencies at once. If I were to make the setting dysfunctional, it would also lead to user confusion, because they then need to discover that they need to change the infill pattern, which may look unlogical to them.
Fixes#8192.
Possibly this is a problem if the tooltip is invisible. We're not sure yet how to reproduce that bug though. In any case, it's neater to not catch mouse events you don't need.
This was decided on by the material & process engineers. It's a pretty safe change since the support brim pretty much has only advantages if there is no support infill.
Fixes ST-3552.
These have moved. The Support Structure setting was already present in the support category.
Done as a 5 minute fix while working on the Settings Guide.
I think for the support meshes, some settings were simply missed because they are in completely different categories. For instance, the support flow rate also applies to support meshes so those settings should be visible.
For the tree support settings, I think that when the tree support became activated by support_structure, the developer checked for instances where the support_tree_enable setting made a setting visible (as alternative to the normal support_enable setting). Like Support Infill Density used to be visible if normal support or tree support was enabled, and now needs to check only for normal support. However they didn't also look for settings that are ONLY available for normal support and not for tree support. So those settings now have extra conditions that disable them if the support structure is set to tree support.
With this I tried to word the check correctly in case we ever get a third support construction type. Like, sometimes a setting is not shown with tree support because tree support explicitly doesn't support it (e.g. Conical Support), but sometimes it's not shown with tree support because it's specific to area support (e.g. support join distance).
Done as a five minute fix (although typing this commit message also took five minutes) as I encountered these problems while working on the settings guide.
That was still missing, oops. I'm aborting the translations to get this in. It's important enough to break the string freeze and restart the translations process at this stage.
Contributes to issue CURA-7622.
Some printers stylize themselves with allcaps to gain more attention or because they use fonts that don't have lowercase (especially Asian brands) or to mix it with fixed-width characters. Here we'd like to keep them all equal, so they get proper name-style capitalisation.
