Translators
-
And depends also...
English --> French is for me something that I can maybe make
but the inverse French --> English is for me worst than the Google translator!
As you can see along my posts, I am not modified genetically for that -
@unknownuser said:
And depends also...
English --> French is for me something that I can maybe make
but the inverse French --> English is for me worst than the Google translator!
As you can see along my posts, I am not modified genetically for thatAnd the 'tone' and 'idiom' is also so important - for example, to recast your last post into an Englishman's English...
...Perhaps I am capable of acceptable English --> French translations,
but my French --> English is worse than even the Google Translator!
As you can see from my posts, I am not genetically modified for that work!
You English was perfectly understandable, BUT it just 'sounds' like a Frenchman speaking English ! I can even hear the accent !!
In the USA an American would probably write
...I can do English --> French translations,
but my French --> English is the worst - jeez! worse than that Google Translator.
I am not genetically suited to that kind of task - as is evidenced by my posts! 
-
Two languages for the same price!
Thx for this comparative lesson -
@tig said:
Damn !
French v Spanish
That's why we need translators...
Of course in English we have 'border' = the edge of something [page/country/etc] - which is not applicable as a 'line' or 'edge' in our contexts...
We also have 'arête/arete' = a geographical feature, a sharp sloping ridge found between two glaciers, glaciated valleys or tarns - which I think is from 'knife-edge' ?Is Edge really the best term? Just thinking, since and Edge can appear on a co-planar surface. Not really and "edge" then?
Doesn't geometry books talk about Lines (infinite) and Line Segments (finite)? Of couse "Line Segment" is more awkward to juggle around in the UI. But it's this kind of things one need to think about when translating, does the word in the original language fit? Getting caught up too much in the terms of the source language is not a good thing. -
But on a co-planar surface, it could be an edge between materials. So in that sense, even on a co-planar surface, it could still be an edge to something
Chris
-
@chris fullmer said:
But on a co-planar surface, it could be an edge between materials. So in that sense, even on a co-planar surface, it could still be an edge to something
Chris
Not necessarily, could be separating two co-planar faces of the same material...
-
To most users an 'edge' borders a 'face', and a 'line' is an 'edge' without a 'face'.
But then in SUp a curve is a polyline and isn't necessarily curved at all !
It's all very confusing...
Being picky my ExtrudeEdgesByRails should be called say ExtrudeCurveProfilesByCurveRails or ExtrudePolylineProfilesByPolylineRails ? BUT 'curves' are made of 'edges', as 'lines' are 'edges' too in SUp-speak -
@thomthom said:
Not necessarily, could be separating two co-planar faces of the same material...
We might introduce the term "seam" as this special case of edge.
thots?
-
I wasn't thinking that we change the existing terms in SU. Plugins should use the terms used by Sketchup for consistency. But it was more of a reflection on how computer terms are used. And when translating, when one feel that the word is lacking in the target language, then basing it on the original might not be the best. As in the case of an Edge - it's not always representing the edge of something. So when transfering that to a new language, one might want to think twice.
Back to the case of French, and the term Edge - isn't there an French version of SU? What does it use?
-
And what does the Entity Info window say when you select an Edge?
-
Edge style = "Style d'Arêtes" in French version of SU
Display edges = "Affichages des arêtes"
Profil = "Arêtes profilées"
Depthcue = "Arêtes avec effet de profondeur"
Extention = "Arêtes prolongées"
French is some prolix -
@unknownuser said:
Entity info = "Infos sur l'entité" ("s" is always written even when only one thing is selected
..., I see that English gives never s to "Info"because it's the noun that is pluralized:
"Entity" (singular)
"Entities" (plural)"Info" is a short slang for "Information"
"Information" is not pluralized, just as "Data" is not. -
Entity info = "Infos sur l'entité" ("s" is always writed even only one thing is selected
French is prudent, I see that English gives never s to "Info" English is foolhardy
"Arête" again when one edge is selected
"2 Arêtes" when you select 2 edges -
This explain that
-
@thomthom said:
And what does the Entity Info window say when you select an Edge?
I think TT wants to know what the object title says in French.
(The dialog title is always the same.)
If a single edge is selected, it says "Edge" (in English.)
But when many objects are selected, the object title says (in English.): "n Entities" where n is the number selected.
Pilou already said ...
"Arête" [] when one edge is selected
"2 Arêtes" when you select 2 edges [etc]
Sp a Sketchup Edge is an 'Arête' in French, although a direct translation might give us 'Bord'... but it's not used in SUp... -
@unknownuser said:
Entity info = "Infos sur l'entité"
This is an example of non-direct translation.
Info de l'entité = Entity Info
Infos sur l'entité = About the entity
(If you capitalize the 'e' in entité, the Google translator gives "Entity Info" in English, for both phrases.)Propriétés de l'Entité = Entity Properties
-
@unknownuser said:
This is an example of non-direct translation.
Yes it's the fix's title on the French SU Window info box !
In SU English Title is also fixed!Ps Entities is very elaborate, elements is more curent
-
@unknownuser said:
@unknownuser said:
This is an example of non-direct translation.
Yes it's the fixed title on the French SU Window info box !
In SU English Title is also fixed!Ps Entities is very elaborate, elements is more curent
elaborate = formal?
We cannot call them element because the Ruby classname is Entity, and the Ruby collection of them is named Entities.
So we must be formal. -
elaborate = literary
-
Here's an example of a Norwegian translation problem:
Face = Overflate
Overflate is directly translated as Surface - as direct translation of Face doesn't sound good.
But, in SU there is a distinction between Face and Surface. If you click on a Face where the adjacent faces are separated by a soft edge, Entity Info then displays Surface.
That leads to a problem when translating to Norwegian, as one need to find a way to distinguish between Face and Surface., despite that both words really would have been translated as Overflate.
Using the MS search tool is of no futher help, as it only lists Overflate as translation for Face.
Advertisement