I have been translating to swedish on crowdin.
I have a question regarding how other languages translate the Body and Part containers in respect to a "part" or "body" (normal language use VS container)?
I have kept the english Part and Body when i think it refers to the containers but translated the words otherwise to what i think is proper for the specific case.
I have seen a few cases where i think it refers to containers but the words are not in capital. Will see if i mess things up.
I have also seen several terms refering to the same thing? solid, part, object, detail, but its a bit hard to read out as its often out of context.. do we have some kind of guidelines on what terms to use to keep the text consistant?
Body, body, Part, part, translations
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: Body, body, Part, part, translations
I think we can well use some technical terms as names which don't have necessarily to be translated, like workbench names or special constructs like "Body". They are often things that can be translated but they have in FreeCAD very technical meanings so I often leave them untranslated.
A Sketcher Lecture with in-depth information is available in English, auf Deutsch, en français, en español.
Re: Body, body, Part, part, translations
Technically, this is not really about the wiki, but the FreeCAD UI translation.
In French, we translated both "Part" and "Body". Otherwise, what's translation for? A long-standing gripe of mine is that the tool is translated in the GUI menus/tooltips, but the object label it creates in the tree remains in English (this is true for 99% of FreeCAD commands ). In any commercial CAD program, when it is in a different language, 100% of the GUI is translated, including the tree objects.
On the wiki, when talking about the Part container, I always mention it as the "Part container", never "Part" alone because it is too confusing (excepted for the Std Part page in which I think confusion should be minimal). In some contexts, for example if the PartDesign Body is mentioned outside of the PartDesign documentation, then I will try to label it as PartDesign Body than just "body" alone which is a generic CAD term. Then I will use the uppercase on Body.
Depending on context, I do not always use uppercase - in English it is often used, but this is not the case in French.
If you're not sure about context, don't hesitate to post a question in the right sidebar (preferably in English), and others will provide insight.
I'll also tell you: here and there I've taken "artistic license" with the French translation. Sometimes making a straight translation from English simply makes no sense, because the English text string hardly makes sense to begin with!!! One example is the "Thickness" tool, which on the face of it is a ridiculous name. Apply a thickness to a part? Duh, every solid has a thickness. All other CAD programs use variations of shell/thick shell/thin shell which is a lot more telling about what the command actually does. Of course, this term can clash with the fact that shell is already a topological term used in Open Cascade. Which is why "thick shell" wouldn't be a bad idea in my opinion. Or maybe "solid shell"? Anyway.
Before the v0.17 release I didn't have the time to translate much, but I spent some of my Holiday proofreading the Part, PartDesign, Sketcher and TechDraw translations for 0.18. And to heck with it, I changed the PartDesign Thickness translation to the equivalent of "shell" in French.
In French, we translated both "Part" and "Body". Otherwise, what's translation for? A long-standing gripe of mine is that the tool is translated in the GUI menus/tooltips, but the object label it creates in the tree remains in English (this is true for 99% of FreeCAD commands ). In any commercial CAD program, when it is in a different language, 100% of the GUI is translated, including the tree objects.
On the wiki, when talking about the Part container, I always mention it as the "Part container", never "Part" alone because it is too confusing (excepted for the Std Part page in which I think confusion should be minimal). In some contexts, for example if the PartDesign Body is mentioned outside of the PartDesign documentation, then I will try to label it as PartDesign Body than just "body" alone which is a generic CAD term. Then I will use the uppercase on Body.
Depending on context, I do not always use uppercase - in English it is often used, but this is not the case in French.
Unfortunately we don't. You can add shape, item, element to the list!
If you're not sure about context, don't hesitate to post a question in the right sidebar (preferably in English), and others will provide insight.
I'll also tell you: here and there I've taken "artistic license" with the French translation. Sometimes making a straight translation from English simply makes no sense, because the English text string hardly makes sense to begin with!!! One example is the "Thickness" tool, which on the face of it is a ridiculous name. Apply a thickness to a part? Duh, every solid has a thickness. All other CAD programs use variations of shell/thick shell/thin shell which is a lot more telling about what the command actually does. Of course, this term can clash with the fact that shell is already a topological term used in Open Cascade. Which is why "thick shell" wouldn't be a bad idea in my opinion. Or maybe "solid shell"? Anyway.
Before the v0.17 release I didn't have the time to translate much, but I spent some of my Holiday proofreading the Part, PartDesign, Sketcher and TechDraw translations for 0.18. And to heck with it, I changed the PartDesign Thickness translation to the equivalent of "shell" in French.
Re: Body, body, Part, part, translations
I know its ui related, but the discussion i wanted was a bit more about generic technical terms and how/when to translate them, this applies to the wiki as well.
Its not my intention to complain or starting some flame war, but rather to discuss if and what we can change to improve the text for users and translators.
I really think we should have a look at all our english text after 0.18 release to make sure things makes sense. Clean things up, use fewer terms to describe the same things and really think through our naming.
I know this is a bit sensetive and will mess things up for current users, but when you need to clean, you need to clean..
One thing that i find annoying is the "body" "part" container names.
From physics a body is a isolated physical entity, and hence the "solid" = "body" makes sense. But part is a way to generic term.. "group" or "assembly" would be better but not great...
Now think of the sentence: " the human body consists of several parts" then try to use the part and body containers, that is what a lot of new users are exposed to
Its not my intention to complain or starting some flame war, but rather to discuss if and what we can change to improve the text for users and translators.
I really think we should have a look at all our english text after 0.18 release to make sure things makes sense. Clean things up, use fewer terms to describe the same things and really think through our naming.
I know this is a bit sensetive and will mess things up for current users, but when you need to clean, you need to clean..
One thing that i find annoying is the "body" "part" container names.
From physics a body is a isolated physical entity, and hence the "solid" = "body" makes sense. But part is a way to generic term.. "group" or "assembly" would be better but not great...
Now think of the sentence: " the human body consists of several parts" then try to use the part and body containers, that is what a lot of new users are exposed to
Re: Body, body, Part, part, translations
+1
The problem is that we need solids of different tastes, and there might not be just one word describing what a FreeCAD body is. Furthermore it is sensible to look at other 3D modeling tools and the terms they use. Meanwhile I almost made friends with all of these different terms meaning almost the same in normal life.From physics a body is a isolated physical entity, and hence the "solid" = "body" makes sense. But part is a way to generic term.. "group" or "assembly" would be better but not great...
In FreeCAD a body is a special technical term, as is a Part container. You can leave them as such even in a translation - in German it seems to be far more common to use anglizisms than e.g. in French - or you have to find a translated term which you use from then on in the same technical sense.
An example for this is the term "element". When writing my sketcher tutorial bejant pointed out that this should be used for geometric elments only. Of course I could talk about the elements in a body, in a boolean union etc. But I never do. In FreeCAD speech an element is always a geometric element.
We have to find more of these sharp definitions.
A Sketcher Lecture with in-depth information is available in English, auf Deutsch, en français, en español.
-
- Veteran
- Posts: 2611
- Joined: Tue Feb 21, 2012 8:07 pm
- Location: Torino - Italy
Re: Body, body, Part, part, translations
Hi everyone.
The problem is common to all translators, but the discussion is endless .... The best thing is to know the terms in both languages, perhaps.
Glossary was activated for defining terms, but it seems to me little used.
The problem is common to all translators, but the discussion is endless .... The best thing is to know the terms in both languages, perhaps.
Glossary was activated for defining terms, but it seems to me little used.