search

looooo / freecad.gears

a gear module for freecad
GNU General Public License v3.0
252 stars 95 forks source link

[Discussion] Implementing GUI translation on Crowdin. #152

Open kaktusus opened 7 months ago

kaktusus commented 7 months ago

Hey.

@looooo I can help you with running translations on the FreeCAD-addons repository in Crowdin. It is not complicated and does not require much time. I expect that this will make your workbench more widely used. :smile:

hasecilu commented 7 months ago

From what I have seen on the main FreeCAD Crowdin project almost every day FreeCAD is being translated, on the addons project only 7 external WB are there from more than 100!. The point is that having the same people that translates main FreeCAD translating the addons will help end users by having a level of consistency on the whole FreeCAD environment.

I'm sure doing this fellow translators that are already helping FreeCAD ecosystem would notice the translation support more easily on Crowdin that here on GitHub.

kaktusus commented 7 months ago

@hasecilu you said it very nicely.

luzpaz commented 3 weeks ago

What's holding up getting gear wb translations on crowdin ?

kaktusus commented 3 weeks ago

In principle, the author of this workbench has not yet expressed his opinion on this subject. :wilted_flower:

Maybe he is very busy or maybe he is not interested in such a turn of events .... :interrobang:

luzpaz commented 3 weeks ago

Probably busy. @looooo do you need any assistance to make this happen ?

looooo commented 3 weeks ago

I am currently in vacation. It would be nice to add translations.

kaktusus commented 3 weeks ago

The translation file has already been imported into Crowdin is in the test directory of the Freecad-addons repository.

hasecilu commented 3 weeks ago

Just a note here: I think this was the first WB to which I added translation support, at that time I just used translate() function because that's what I saw on Fasteners and SheetMetal WBs.

The thing is that the correct way is to use QT_TRANSLATE_NOOP() with the command name as context (not the class name), as example see my recent changes on Render and CfdOF WBs.

The problem of not doing it like this is that some accented characters would not be well rendered. So let me finish a patch to fix this potential issue, there is a catch though: I would like that #153 is merged, the reason: enable users to use What's this? command on FCGear commands and get the correct Wiki article opened.

Having the commands' names renamed I could use those names for the contexts of strings, of course, if is not merged I can still use the current names but Wiki pages will not be open correctly. =(

kaktusus commented 3 weeks ago

When you're ready (one of these ways) let me know then I'll do a source string export to Crowdin.