Some Spanish translation issues #102030

Open
opened 2022-10-24 02:12:33 +02:00 by Carlos · 28 comments

System Information
Operating system: Linux-6.0.2-2-MANJARO-x86_64-with-glibc2.36 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06

Blender Version
Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-21 18:48, hash: 04eab0fd01
Worked: (?)

Short description of error

Hi, thank you for Blender!!

I recently change the interface to Spanish and I found some misspellings, words not translated, and maybe chances for improvement (I'm from México).

Shader Editor
image.png

Reset Node = Reiniciar Nodo
Material Output = Salida del Material
(Possibly an improvement)
Change "Metálico" to "Brillo Metálico". Metálico is for the conductivity character of the material, not the appearance, brillo metalico is the way we know this quality.

image.png
Missing Paths = Rutas Faltantes

image.png
White Noise Texture = Textura Ruido Blanco or Textura de Ruido Blanco

image.png
Select frame's members (children) = Seleccionar marco(s) hijo(s)
Select parent frame = Seleccionar marco padre
(Possibly an improvement)
"(De)seleccionar todo" to "Deseleccionar todo" the parenthesis is not needed.

3D Viewport
image.png
"Enegono" doesn't exist, could be "Ngono" which reads "enegono"
(Possibly some improvements)
"Tipo de extremos" to "Tipo de bases" (cylinder)
"Entorno" to "Global", Global has the same meaning (cognate), entorno means environment.

Properties & 3D Viewport (Possibly an improvement)
image.png
In tradicional sculpture, and stop motion is also used "Armadura" (Armature) in Spanish for the core of the sculpture/model to pose it.

Outliner

image.png
The Scene menu is not completely translated
Copy Settings = Copiar Ajustes, also, copiar configuración
Linked Copy = Copia Vinculada, also, copia enlazada.
Full Copy = Copia Completa, also copia total

Thank you!!

**System Information** Operating system: Linux-6.0.2-2-MANJARO-x86_64-with-glibc2.36 64 Bits Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06 **Blender Version** Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-21 18:48, hash: `04eab0fd01` Worked: (?) **Short description of error** Hi, thank you for Blender!! I recently change the interface to Spanish and I found some misspellings, words not translated, and maybe chances for improvement (I'm from México). **Shader Editor** ![image.png](https://archive.blender.org/developer/F13754154/image.png) Reset Node = Reiniciar Nodo Material Output = Salida del Material (Possibly an improvement) Change "Metálico" to "Brillo Metálico". Metálico is for the conductivity character of the material, not the appearance, brillo metalico is the way we know this quality. ![image.png](https://archive.blender.org/developer/F13754162/image.png) Missing Paths = Rutas Faltantes ![image.png](https://archive.blender.org/developer/F13754170/image.png) White Noise Texture = Textura Ruido Blanco or Textura de Ruido Blanco ![image.png](https://archive.blender.org/developer/F13754179/image.png) Select frame's members (children) = Seleccionar marco(s) hijo(s) Select parent frame = Seleccionar marco padre (Possibly an improvement) "(De)seleccionar todo" to "Deseleccionar todo" the parenthesis is not needed. **3D Viewport** ![image.png](https://archive.blender.org/developer/F13754200/image.png) "Enegono" doesn't exist, could be "Ngono" which reads "enegono" (Possibly some improvements) "Tipo de extremos" to "Tipo de bases" (cylinder) "Entorno" to "Global", Global has the same meaning (cognate), entorno means environment. **Properties & 3D Viewport** (Possibly an improvement) ![image.png](https://archive.blender.org/developer/F13754221/image.png) In tradicional sculpture, and stop motion is also used "Armadura" (Armature) in Spanish for the core of the sculpture/model to pose it. **Outliner** ![image.png](https://archive.blender.org/developer/F13754279/image.png) The Scene menu is not completely translated Copy Settings = Copiar Ajustes, also, copiar configuración Linked Copy = Copia Vinculada, also, copia enlazada. Full Copy = Copia Completa, also copia total Thank you!!
Author

Added subscriber: @Confabulatori

Added subscriber: @Confabulatori
Member

Added subscribers: @mont29, @PratikPB2123

Added subscribers: @mont29, @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

@mont29 hi, who is responsible for Spanish translation?

@mont29 hi, who is responsible for Spanish translation?

Added subscriber: @GabrielGazzan

Added subscriber: @GabrielGazzan

Hi @PratikPB2123 and @Confabulatori

I'm in charge of Spanish translation.
Currently all available strings are translated, so there must be some ones that are still not extracted?

Carlos, thanks for the time taken in gathering all the cases and posting them here.
I'll respond to each of them in the next message.

Hi @PratikPB2123 and @Confabulatori I'm in charge of Spanish translation. Currently all available strings are translated, so there must be some ones that are still not extracted? Carlos, thanks for the time taken in gathering all the cases and posting them here. I'll respond to each of them in the next message.
Author

Thank you @GabrielGazzan !!

Thank you @GabrielGazzan !!

Added subscriber: @pioverfour

Added subscriber: @pioverfour

Carlos,
As I commented in the previous message, currently (as of today: Oct 24 2022), all text strings available for translators to work on are translated into Spanish. So for all texts you happen to see untranslated we (translators) are still not able to give them any translation into any language.
Most probably they will be translated in time, though, for the 3.4 release.
Still, it's useful that you report them, wherever you find them, because sometimes they go unnoticed and thus, not being made translatable.

But, still, please take into consideration that as you are using a preliminary (in this case an alpha) version of the program, some unfinished work is expected to be seen potentially all over the place.

Now I will move on and give you some feedback on the other suggestions you kindly made for improvements:

First, let me spend a moment trying to explain the concept behind the Spanish translation effort.
As Spanish is a language used natively by more than 400 million people in at least 3 continents, and 22 or so countries, at a certain point it will be unavoidable to notice certain words as "not the most common word I would use for" any concept. There's simply no way to achieve that with a single translation.
So, I try to favor the use of universal (so to speak) words that every hispanic native could extract the intended meaning from.
For all that, this could be regarded as a "neutral" Spanish translation.
Another thing that's avoided are personal pronouns, preferring instead the use of infinitive forms in sentences, so the user would not feel any kind of inappropriate/uncomfortable treatment when interacting with it.
So, you will find no:
"Tu debes abrir el archivo para realizar la operación" or
"Ud. debe abrir el archivo para realizar la operación", but instead you will find
"Se debe abrir el archivo para realizar la operación".

Another thing that's specifically avoided are literal translations, especially when there is a better way of conveying the right concept to the user's mind. (Many times the underlaying concepts behind the UI controls and tools in Blender, that we're trying the user to navigate through, are really complex and not present in the day to day life of almost anybody. So making the effort to find the clearest, simplest and shortest way of giving the right clue to the user, is always a desired target.

With all that in mind, I'll go to the specifics of your valued report:

Shader Editor

Change "Metálico" to "Brillo Metálico". Metálico is for the conductivity character of the material, not the appearance, brillo metalico is the way we know this quality.

I understand your request, but I'm not so sure it is the right thing to do.
In the manual it basically says:
"Metallic: Blends between a non-metallic and metallic material model. (and it goes on...)"
So, as I understand it, it's referring to a "material model" and not to the surface brightness specifically (although it obviously has a direct impact on it).
So "Metálico" is refering to "Un modelo metálico" (a metallic model), and in that sense the wording seems to be right...

Note to Devs: It'd be great to have tooltips for all of the Principled BSDF node options. They would be so useful for users trying to delve their way in the complexities of BSDF materials.

"(De)seleccionar todo" to "Deseleccionar todo" the parenthesis is not needed.

Functions that are labeled this way are toggles. So one time it selects and the next deselects. That's the reason the parenthesis are there.

3D Viewport

"Enegono" doesn't exist, could be "Ngono" which reads "enegono"

An Ngon is basically a polygon of N sides (or more correctly: angles). It's mainly a theoretical concept, for as long as a specific polygon is defined it will also have a specific number of sides, and so it will not be an Ngon any more, but a pentagon, hexagon, etc.
In Spanish the concept remains the same, so as the letter N is read "ene" it could be written as "Ngono" or "enégono". Personally I find much more readable the word "enégono" than the other option, as the structure of "Ngono" is not normal for a word in spanish and as all the letters are jointed in a single word, that N at the start of the word would sound just as a gutural "n" and not as "ene". Perhaps it could also be written as "N gono" which could make the start be read correctly as "ene", but then it'd be strange when finding the "gono" part, as there's really no such Spanish word, and it'd remain as a meaningless part in people's minds, even it they read it right.

Finally, as with almost any tricky concept that is not trivial to translate I try to find more occurrences online, and there definitely are several, so the word exists and is used with that precise meaning.
imagen.png

"Tipo de extremos" to "Tipo de bases" (cylinder)

Yes, you are right.
That string is only used for that feature and then it would be better translated as you suggest.
You should see it changed in Blender from tomorrow night on. Thanks!
imagen.png

"Entorno" to "Global", Global has the same meaning (cognate), entorno means environment.

Yes, that one is coming...
Traditionally, throughout the IU, there have been several strings that (as in English they use the same word for several distinct concepts) they were assigned to the same single text string. So translators have faced that problem for a loooong time. If you translate it to be the right one on one place, then other places look wrong.
Currently, thanks to @pioverfour , who's puting a lot of effort in it, those problematic strings are being made independent.
The one you found certainly is one of the many soon to be changed. :)
If you wish you can follow the progress of that task at #43295

Properties & 3D Viewport

In tradicional sculpture, and stop motion is also used "Armadura" (Armature) in Spanish for the core of the sculpture/model to pose it.

"Armadura" is a word that in Spanish can also convey a concept just the opposite of a skeleton.
That is, an "Armadura" is what Medieval Knights would use to protect their bodies in combat, basically an exoskeleton, the opposite of a skeleton. So the word "Esqueleto" was preferred in part because it has not any possible ambiguous meanings.
Besides that, I personally find that since in Blender an Armature is composed of individual "Bones", just like any animal skeleton (for which in Spanish, the undisputed most used word is "Esqueleto"), the correct candidate for that string would be, you guessed itÑ Esqueleto.
But that's not all, in almost all other popular 3D software I know of and used, the word for that concept (a bones or joints structure to deform a mesh), even in English, is Skeleton.

Outliner (Note: it's the Header really)

The (New) Scene menu is not completely translated

mmm... this is translated on my end and committed to the repository
check to see if next week it's still untranslated, because I see it in Spanish (screen-capture below).
New Scene.png

Note on used glossary:
"Settings" is translated as "Opciones" throughout the program UI, "configuración" is also a suitable word, but one should be chosen...
"Ajustes" is used for translating the concept of "Presets" (Ajustes prestablecidos) but as this is quite lengthy for many of the places where the string is used, I kept it in its shorter form Ajustes.

"Parent" and "Child" are not directly translated as "father" and "son" as you suggest, but instead as the relationship in a command hierarchy, where you could find one or more subordinate elements to a single superior element, which in turn could have its own superior, etc, etc. Moreover, we all know it is frequent for sons not to respect fathers' designs and we certainly don't want this to happen in Blender. :P

Carlos, As I commented in the previous message, currently (as of today: Oct 24 2022), all text strings available for translators to work on are translated into Spanish. So for all texts you happen to see untranslated we (translators) are still not able to give them any translation into any language. Most probably they will be translated in time, though, for the 3.4 release. Still, it's useful that you report them, wherever you find them, because sometimes they go unnoticed and thus, not being made translatable. But, still, please take into consideration that as you are using a preliminary (in this case an alpha) version of the program, some unfinished work is expected to be seen potentially all over the place. Now I will move on and give you some feedback on the other suggestions you kindly made for improvements: First, let me spend a moment trying to explain the concept behind the Spanish translation effort. As Spanish is a language used natively by more than 400 million people in at least 3 continents, and 22 or so countries, at a certain point it will be unavoidable to notice certain words as "not the most common word I would use for" any concept. There's simply no way to achieve that with a single translation. So, I try to favor the use of universal (so to speak) words that every hispanic native could extract the intended meaning from. For all that, this could be regarded as a "neutral" Spanish translation. Another thing that's avoided are personal pronouns, preferring instead the use of infinitive forms in sentences, so the user would not feel any kind of inappropriate/uncomfortable treatment when interacting with it. So, you will find no: "Tu debes abrir el archivo para realizar la operación" or "Ud. debe abrir el archivo para realizar la operación", but instead you will find "Se debe abrir el archivo para realizar la operación". Another thing that's specifically avoided are literal translations, especially when there is a better way of conveying the right concept to the user's mind. (Many times the underlaying concepts behind the UI controls and tools in Blender, that we're trying the user to navigate through, are really complex and not present in the day to day life of almost anybody. So making the effort to find the clearest, simplest and shortest way of giving the right clue to the user, is always a desired target. With all that in mind, I'll go to the specifics of your valued report: **Shader Editor** > Change "Metálico" to "Brillo Metálico". Metálico is for the conductivity character of the material, not the appearance, brillo metalico is the way we know this quality. I understand your request, but I'm not so sure it is the right thing to do. In the manual it basically says: "Metallic: Blends between a non-metallic and metallic material model. (and it goes on...)" So, as I understand it, it's referring to a "material model" and not to the surface brightness specifically (although it obviously has a direct impact on it). So "Metálico" is refering to "Un modelo metálico" (a metallic model), and in that sense the wording seems to be right... Note to Devs: It'd be great to have tooltips for all of the Principled BSDF node options. They would be so useful for users trying to delve their way in the complexities of BSDF materials. > "(De)seleccionar todo" to "Deseleccionar todo" the parenthesis is not needed. Functions that are labeled this way are toggles. So one time it selects and the next deselects. That's the reason the parenthesis are there. **3D Viewport** > "Enegono" doesn't exist, could be "Ngono" which reads "enegono" An Ngon is basically a polygon of N sides (or more correctly: angles). It's mainly a theoretical concept, for as long as a specific polygon is defined it will also have a specific number of sides, and so it will not be an Ngon any more, but a pentagon, hexagon, etc. In Spanish the concept remains the same, so as the letter N is read "ene" it could be written as "Ngono" or "enégono". Personally I find much more readable the word "enégono" than the other option, as the structure of "Ngono" is not normal for a word in spanish and as all the letters are jointed in a single word, that N at the start of the word would sound just as a gutural "n" and not as "ene". Perhaps it could also be written as "N gono" which could make the start be read correctly as "ene", but then it'd be strange when finding the "gono" part, as there's really no such Spanish word, and it'd remain as a meaningless part in people's minds, even it they read it right. Finally, as with almost any tricky concept that is not trivial to translate I try to find more occurrences online, and there definitely are several, so the word exists and is used with that precise meaning. ![imagen.png](https://archive.blender.org/developer/F13755628/imagen.png) > "Tipo de extremos" to "Tipo de bases" (cylinder) Yes, you are right. That string is only used for that feature and then it would be better translated as you suggest. You should see it changed in Blender from tomorrow night on. Thanks! ![imagen.png](https://archive.blender.org/developer/F13755790/imagen.png) > "Entorno" to "Global", Global has the same meaning (cognate), entorno means environment. Yes, that one is coming... Traditionally, throughout the IU, there have been several strings that (as in English they use the same word for several distinct concepts) they were assigned to the same single text string. So translators have faced that problem for a loooong time. If you translate it to be the right one on one place, then other places look wrong. Currently, thanks to @pioverfour , who's puting a lot of effort in it, those problematic strings are being made independent. The one you found certainly is one of the many soon to be changed. :) If you wish you can follow the progress of that task at #43295 **Properties & 3D Viewport** > In tradicional sculpture, and stop motion is also used "Armadura" (Armature) in Spanish for the core of the sculpture/model to pose it. "Armadura" is a word that in Spanish can also convey a concept just the opposite of a skeleton. That is, an "Armadura" is what Medieval Knights would use to protect their bodies in combat, basically an exoskeleton, the opposite of a skeleton. So the word "Esqueleto" was preferred in part because it has not any possible ambiguous meanings. Besides that, I personally find that since in Blender an Armature is composed of individual "Bones", just like any animal skeleton (for which in Spanish, the undisputed most used word is "Esqueleto"), the correct candidate for that string would be, you guessed itÑ Esqueleto. But that's not all, in almost all other popular 3D software I know of and used, the word for that concept (a bones or joints structure to deform a mesh), even in English, is Skeleton. **Outliner** (Note: it's the Header really) > The (New) Scene menu is not completely translated mmm... this is translated on my end and committed to the repository check to see if next week it's still untranslated, because I see it in Spanish (screen-capture below). ![New Scene.png](https://archive.blender.org/developer/F13755066/New_Scene.png) Note on used glossary: "Settings" is translated as "Opciones" throughout the program UI, "configuración" is also a suitable word, but one should be chosen... "Ajustes" is used for translating the concept of "Presets" (Ajustes prestablecidos) but as this is quite lengthy for many of the places where the string is used, I kept it in its shorter form Ajustes. "Parent" and "Child" are not directly translated as "father" and "son" as you suggest, but instead as the relationship in a command hierarchy, where you could find one or more subordinate elements to a single superior element, which in turn could have its own superior, etc, etc. Moreover, we all know it is frequent for sons not to respect fathers' designs and we certainly don't want this to happen in Blender. :P

Added subscriber: @Yuuki21597

Added subscriber: @Yuuki21597

Isn't it possible to use «Polygon» instead «Enégono»? For example, when someone adds a cylinder, Blender uses «Abanico de triángulos». I would think that if any phrase that includes "Cuadrado" in itself does not appear in the list, but "Polígonos" appears, it's because the polygon will be an Ngon.

On the other hand, I always misread «Enegono» as «Eneágono» (a Nonagon). I feel that «Enegono» is weird, but I'm a one person. Perhaps I need to get out and talk to more people xD

For Parent and Childs elements, isn't «sub-» a good option?

Sorry if I said some nonsense. I like languages, and am a hobbyst translator, but my english knowlegde is still very basic.

Isn't it possible to use «Polygon» instead «Enégono»? For example, when someone adds a cylinder, Blender uses «Abanico de triángulos». I would think that if any phrase that includes "Cuadrado" in itself does not appear in the list, but "Polígonos" appears, it's because the polygon will be an Ngon. On the other hand, I always misread «Enegono» as «Eneágono» (a Nonagon). I feel that «Enegono» is weird, but I'm a one person. Perhaps I need to get out and talk to more people xD For Parent and Childs elements, isn't «sub-» a good option? Sorry if I said some nonsense. I like languages, and am a hobbyst translator, but my english knowlegde is still very basic.
Author

Thanks

@GabrielGazzan

For all that, this could be regarded as a "neutral" Spanish translation.

Yes, I have read the guidelines time ago, I wanted to help with the manual translation but I saw it was very complicated for a non expert like me. And yes I know not everyone uses the same Spanish.

Functions that are labeled this way are toggles

I had a suspicion it was for emphasis, didn't know this was a toggle!

so as the letter N is read "ene" it could be written as "Ngono" or "enégono"

I studied technical drawing for 5 years and never seen that, a variable writen this way, but as I said I'm from México I know not every one use the same words or language "rules". Also never seen N-gono or ngono until 3D school, maybe this is a word taken from de English Ngon.

Isn't it possible to use «Polygon» instead «Enégono»?

@Yuuki21597

Maybe this could be the best but Ngon is the word used also in Spanish, also quad and tris, maybe the people wont want to change it, although are unnecessary "extranjerismos" (words taken from other language) cuz we have words for that. I like yours -poligono- is clearer for me and is in Spanish.

I feel that «Enegono» is weird, but I'm a one person

Also for me.

"Parent" and "Child" are not directly translated as "father" and "son" as you suggest, but instead as the relationship in a command hierarchy

For Parent and Childs elements, isn't «sub-» a good option?

image.png
image.png
https://es.wikipedia.org/wiki/%C3%81rbol_(inform%C3%A1tica)

I've always seen padre-hijo.

There is always debate on language things, I only mention the things that you might not have seen so that you do what you consider best.

Thanks @GabrielGazzan > For all that, this could be regarded as a "neutral" Spanish translation. > Yes, I have read the guidelines time ago, I wanted to help with the manual translation but I saw it was very complicated for a non expert like me. And yes I know not everyone uses the same Spanish. > Functions that are labeled this way are toggles > I had a suspicion it was for emphasis, didn't know this was a toggle! > so as the letter N is read "ene" it could be written as "Ngono" or "enégono" > I studied technical drawing for 5 years and never seen that, a variable writen this way, but as I said I'm from México I know not every one use the same words or language "rules". Also never seen N-gono or ngono until 3D school, maybe this is a word taken from de English Ngon. > Isn't it possible to use «Polygon» instead «Enégono»? > @Yuuki21597 Maybe this could be the best but Ngon is the word used also in Spanish, also quad and tris, maybe the people wont want to change it, although are unnecessary "extranjerismos" (words taken from other language) cuz we have words for that. I like yours -poligono- is clearer for me and is in Spanish. > I feel that «Enegono» is weird, but I'm a one person > Also for me. > "Parent" and "Child" are not directly translated as "father" and "son" as you suggest, but instead as the relationship in a command hierarchy > > For Parent and Childs elements, isn't «sub-» a good option? > ![image.png](https://archive.blender.org/developer/F13757610/image.png) ![image.png](https://archive.blender.org/developer/F13757600/image.png) https://es.wikipedia.org/wiki/%C3%81rbol_(inform%C3%A1tica) I've always seen padre-hijo. There is always debate on language things, I only mention the things that you might not have seen so that you do what you consider best.

Isn't it possible to use «Polygon» instead «Enégono»?

Well, an Ngon is in fact a polygon, but then a triangle is a polygon too...
Moreover, a triangle also fits inside the definition of Ngon as well (when N=3), so even the original alternatives for this option in English are, to me, not quite good ones.
Perhaps "Single Polygon" and "Triangle Fan" could be clearer alternatives to the user, also in English.

Regarding the Parent/Child translation
I know it's debatable, as there are not a wide array of credible widespread examples in Spanish to standardize the concept on.
I personally find the translation of Parent/Child directly as Father/Son as a rather naive one, and quite possibly a misleading one too. Because a father gives birth to a son or creates it, and this is just not the case here; here there are simple hierarchical behaviors imposed from one object to other ones without one being created from the other. There even exist the possibility of breaking that relationship between the two, whereas in a Father/Son one that could just not be possible by the very nature of it.
So I find hierarchical terminology to be far more descriptive for what is happening there.

As a secondary factor, Parent/Child in English are more generic and gender neutral terms than the proposed Padre/Hijo (Father/Son) in Spanish (which specifically refer to the male parent and to the male child), and to me those characteristics make the padre/hijo combo less desirable, both because of potential technical problems in the translation (having to cope with gender) and from a social point of view too. Suzanne, for example is a female monkey: a "mona" and not a "mono" (in Spanish we refer to animals as he/she), but if this object was to be in a hierarchical relationship it'd be referred to as the father or the son of others. :)

> Isn't it possible to use «Polygon» instead «Enégono»? Well, an Ngon is in fact a polygon, but then a triangle is a polygon too... Moreover, a triangle also fits inside the definition of Ngon as well (when N=3), so even the original alternatives for this option in English are, to me, not quite good ones. Perhaps "Single Polygon" and "Triangle Fan" could be clearer alternatives to the user, also in English. **Regarding the Parent/Child translation** I know it's debatable, as there are not a wide array of credible widespread examples in Spanish to standardize the concept on. I personally find the translation of Parent/Child directly as Father/Son as a rather naive one, and quite possibly a misleading one too. Because a father gives birth to a son or creates it, and this is just not the case here; here there are simple hierarchical behaviors imposed from one object to other ones without one being created from the other. There even exist the possibility of breaking that relationship between the two, whereas in a Father/Son one that could just not be possible by the very nature of it. So I find hierarchical terminology to be far more descriptive for what is happening there. As a secondary factor, Parent/Child in English are more generic and gender neutral terms than the proposed Padre/Hijo (Father/Son) in Spanish (which specifically refer to the male parent and to the male child), and to me those characteristics make the padre/hijo combo less desirable, both because of potential technical problems in the translation (having to cope with gender) and from a social point of view too. Suzanne, for example is a female monkey: a "mona" and not a "mono" (in Spanish we refer to animals as he/she), but if this object was to be in a hierarchical relationship it'd be referred to as the father or the son of others. :)
Member

Hello @Confabulatori, thank you for reporting all these, it is very useful to know what cannot yet be translated by the team.

Some details in addition to what Gabriel said:

  • Reset Node, Select frame's members (children) and Select parent frame cannot be translated in the same way as the rest of the UI because they come from the Node Wrangler add-on. This is not an “official” level add-on, which means maintained by the Blender Foundation. Right now add-ons' translations are not easily available to translators, so their UI remains in English. A practical solution may be found in the future but it’s not a current priority.
  • Some of the things you found that cannot yet be translated are complex to fix, I’ll try to have a look when I can. I’ll add them to the to-do list in the mean time.
  • This won’t help the discussion, but just a fun fact: in French, the chosen translation for n-gon (or ngon) is n-gone. I’ve never seen ènegone or the like, but the ordinal adjective “nth” may be translated to either énième or n-ième, the latter being more formal—I think.
Hello @Confabulatori, thank you for reporting all these, it is very useful to know what cannot yet be translated by the team. Some details in addition to what Gabriel said: - *Reset Node*, *Select frame's members (children)* and *Select parent frame* cannot be translated in the same way as the rest of the UI because they come from the Node Wrangler add-on. This is not an “official” level add-on, which means maintained by the Blender Foundation. Right now add-ons' translations are not easily available to translators, so their UI remains in English. A practical solution may be found in the future but it’s not a current priority. - Some of the things you found that cannot yet be translated are complex to fix, I’ll try to have a look when I can. I’ll add them to the to-do list in the mean time. - This won’t help the discussion, but just a fun fact: in French, the chosen translation for n-gon (or ngon) is *n-gone*. I’ve never seen *ènegone* or the like, but the ordinal adjective “nth” may be translated to either *énième* or *n-ième*, the latter being more formal—I think.
Author

Thank you @pioverfour , is true, those are from the addon, it is understable.

Thank you @pioverfour , is true, those are from the addon, it is understable.
Member

Regarding the World message (Entorno vs Global vs Mundo), I tackled it a few weeks ago so hopefully it should be fixed, but it was quite messy so maybe I messed up some messages.
In any case, the plain "World" message (without context) should be in the sense “align to the world”, or Global in your translation, but it’s currently “Entorno”.

Regarding the World message (*Entorno* vs *Global* vs *Mundo*), I tackled it a few weeks ago so hopefully it should be fixed, but it was quite messy so maybe I messed up some messages. In any case, the plain "World" message (without context) should be in the sense “align to the world”, or *Global* in your translation, but it’s currently “Entorno”.
Author

“align to the world”

My mistake, you are right, is not "Global" is World, "Mundo", to align to the world.

> “align to the world” > My mistake, you are right, is not "Global" is World, "Mundo", to align to the world.
Author

@GabrielGazzan I think is not an accurate translation, not neutral Spanish, but your own reinterpretation (change) of mathematical terminology. But I don't want to continue with this topic, as I told you I just wanted to tell you some things you could have missed, thats all.

@GabrielGazzan I think is not an accurate translation, not neutral Spanish, but your own reinterpretation (change) of mathematical terminology. But I don't want to continue with this topic, as I told you I just wanted to tell you some things you could have missed, thats all.
Author

@pioverfour
Maybe this could be changed, all the names of the default file are not translated.
image.png

@pioverfour Maybe this could be changed, all the names of the default file are not translated. ![image.png](https://archive.blender.org/developer/F13776969/image.png)
Member

In #102030#1437705, @Confabulatori wrote:
@pioverfour
Maybe this could be changed, all the names of the default file are not translated.

This is a known issue, and other things are not translated either: world, material, workspaces, render slots… I’d like to improve this situation but it’s another complex one. My workaround as a user is to rename those manually and save the default file, but it’s not very satisfactory.

> In #102030#1437705, @Confabulatori wrote: > @pioverfour > Maybe this could be changed, all the names of the default file are not translated. This is a known issue, and other things are not translated either: world, material, workspaces, render slots… I’d like to improve this situation but it’s another complex one. My workaround as a user is to rename those manually and save the default file, but it’s not very satisfactory.
Author

I supposed it, are variables chosen by the user, in this case the Blender Institute. Maybe with a script for search and replace running after the initial setup or whenever the language is changed.

I supposed it, are variables chosen by the user, in this case the Blender Institute. Maybe with a script for search and replace running after the initial setup or whenever the language is changed.

This issue was referenced by 9d732445b9

This issue was referenced by 9d732445b90a32c42364b80954818c16cec5eae0
Bastien Montagne added this to the User Interface project 2023-02-09 15:34:10 +01:00
Member

If we move this out of the triaging queue (by changing status label to Needs Information from Developers), this needs to be the responsibility of a module (so a Module label must be added)

If we move this out of the triaging queue (by changing status label to `Needs Information from Developers`), this needs to be the responsibility of a module (so a `Module` label must be added)
Philipp Oeser added the
Module
User Interface
label 2023-02-14 11:42:41 +01:00

@pioverfour @blender-admin which file should be modified

@pioverfour @blender-admin which file should be modified
Member

@pioverfour @blender-admin which file should be modified

Hi, I don’t know what exactly you’re referring to, many different problems are described in this task.

In general for this kind of issue, the translation files should be modified. More info in the wiki, in the localisation and internationalisation pages. However, do note that translation is handled by the team for the language. The team for Spanish consists of Gabriel Gazzán, and he is already aware of the issues, so if what you’re thinking of is a translation issue I don’t think there is anything you can do about it.

If you want to take a look at a specific problem maybe I can try to help you but I don’t have much time at the moment.

> @pioverfour @blender-admin which file should be modified Hi, I don’t know what exactly you’re referring to, many different problems are described in this task. In general for this kind of issue, the translation files should be modified. More info in the wiki, in the [localisation](https://wiki.blender.org/wiki/Process/Translate_Blender) and [internationalisation](https://wiki.blender.org/wiki/Source/Interface/Internationalization) pages. However, do note that translation is handled by the team for the language. The team for Spanish consists of Gabriel Gazzán, and he is already aware of the issues, so if what you’re thinking of is a translation issue I don’t think there is anything you can do about it. If you want to take a look at a specific problem maybe I can try to help you but I don’t have much time at the moment.

@pioverfour yes, I'm always reading...
As you say, this issue covers a lot of ground, some on my side of the court, others don't (several reported untranslatable messages, that I think you already addressed).

Of the things I can control, I remember some proposals were taken and incorporated into the translation, others were more of a preference of the reporter (local based or for other reasons), but not mistakes per se that needed a fix IMO.
I'll do a full revision again to see if there's something left that could be improved, based of the requests here.

@pioverfour yes, I'm always reading... As you say, this issue covers a lot of ground, some on my side of the court, others don't (several reported untranslatable messages, that I think you already addressed). Of the things I can control, I remember some proposals were taken and incorporated into the translation, others were more of a preference of the reporter (local based or for other reasons), but not mistakes per se that needed a fix IMO. I'll do a full revision again to see if there's something left that could be improved, based of the requests here.

Regarding the World message (Entorno vs Global vs Mundo), I tackled it a few weeks ago so hopefully it should be fixed, but it was quite messy so maybe I messed up some messages.
In any case, the plain "World" message (without context) should be in the sense “align to the world”, or Global in your translation, but it’s currently “Entorno”.

I've just done a review of this term specifically, and wanted to expose here the current use cases I've found for it in Blender:

Main conceptual uses of the term "World":
1- As an Environment (something that encircles the whole scene and can be seen from the camera, not necessarily in a static fashion).
i.e. "I've loaded an HDRI for use as my scene environment light".

2- Universal coordinate system of an absolute nature, that is immutable.
i.e. "When translating the parented object, please don't do it in global space, do it in parent space coordinates".

3- Set of global parameters under which, for example, a physics simulation can be computed.
i.e. "The first step to work with a Rigid Body System is to create a new set of global parameters for it, a new Rigid Body World".

In Spanish I've used, the following terms for:
1- Entorno (environment)
2- Global (global), could have been Universal (Universal) or Absoluto (absolute) too, but the used in English is also Global, so...
3- Entorno, perhaps it could have been Sistema (system) or Opciones Globales (global settings) too. Entorno being shorter.

...and, last, I've not used Mundo (world) for each case because:
1- Simply put Entorno (environment) is much more descriptive of the visual nature of these options, than Mundo (world).

2- Mundo (world) in Spanish is not linearly interchangeable with Universo (universe), as mundo is more used to talk about a large system containing a lot of things, and perhaps having its own set of rules, but also a system that has its boundaries. As an example, the Earth could be said to be a "mundo", but one would not usually refer to it as a "universo". Moreover, the Earth moves, while the universe does not (not that we know of yet, at least :) So, as in the English UI the term Global is already used for the absolute coordinate system, I just kept using it when terms like "World Space" needed to be translated, and turned out as "Espacio global" (Global Space).

3- Mundo (world) is never ever used to describe a set of global parameters of a system in Spanish, so I found it unsuitable. I chose the equivalent of environment instead, of which I'm not particularly fond of, I must admit, but at the same time is shorter than more descriptive alternatives as "Parámetros Globales" or "Opciones Generales".

Bottom line, I think that sometimes, as a translator, one should admit none of the possible chosen words will be the perfect one. Especially when the strings are used in several different contexts and use cases, as happen in such a big application as Blender.
I think I prefer to strive for an understandable result, instead.

Finally, in my review, I've found 5 instances of the term World, used as a single word, and all of them I would translate as Entorno (environment).

> Regarding the World message (*Entorno* vs *Global* vs *Mundo*), I tackled it a few weeks ago so hopefully it should be fixed, but it was quite messy so maybe I messed up some messages. > In any case, the plain "World" message (without context) should be in the sense “align to the world”, or *Global* in your translation, but it’s currently “Entorno”. I've just done a review of this term specifically, and wanted to expose here the current use cases I've found for it in Blender: Main conceptual uses of the term "World": 1- As an Environment (something that encircles the whole scene and can be seen from the camera, not necessarily in a static fashion). i.e. "I've loaded an HDRI for use as my scene environment light". 2- Universal coordinate system of an absolute nature, that is immutable. i.e. "When translating the parented object, please don't do it in global space, do it in parent space coordinates". 3- Set of global parameters under which, for example, a physics simulation can be computed. i.e. "The first step to work with a Rigid Body System is to create a new set of global parameters for it, a new Rigid Body World". In Spanish I've used, the following terms for: 1- Entorno (environment) 2- Global (global), could have been Universal (Universal) or Absoluto (absolute) too, but the used in English is also Global, so... 3- Entorno, perhaps it could have been Sistema (system) or Opciones Globales (global settings) too. Entorno being shorter. ...and, last, I've not used Mundo (world) for each case because: 1- Simply put Entorno (environment) is much more descriptive of the visual nature of these options, than Mundo (world). 2- Mundo (world) in Spanish is not linearly interchangeable with Universo (universe), as mundo is more used to talk about a large system containing a lot of things, and perhaps having its own set of rules, but also a system that has its boundaries. As an example, the Earth could be said to be a "mundo", but one would not usually refer to it as a "universo". Moreover, the Earth moves, while the universe does not (not that we know of yet, at least :) So, as in the English UI the term Global is already used for the absolute coordinate system, I just kept using it when terms like "World Space" needed to be translated, and turned out as "Espacio global" (Global Space). 3- Mundo (world) is never ever used to describe a set of global parameters of a system in Spanish, so I found it unsuitable. I chose the equivalent of environment instead, of which I'm not particularly fond of, I must admit, but at the same time is shorter than more descriptive alternatives as "Parámetros Globales" or "Opciones Generales". Bottom line, I think that sometimes, as a translator, one should admit none of the possible chosen words will be the perfect one. Especially when the strings are used in several different contexts and use cases, as happen in such a big application as Blender. I think I prefer to strive for an understandable result, instead. Finally, in my review, I've found 5 instances of the term World, used as a single word, and all of them I would translate as Entorno (environment).
Member

Finally, in my review, I've found 5 instances of the term World, used as a single word, and all of them I would translate as Entorno (environment).

Oh ok, my bad then!

> Finally, in my review, I've found 5 instances of the term World, used as a single word, and all of them I would translate as Entorno (environment). Oh ok, my bad then!
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#102030
No description provided.