Translators
-
For my deBabelizer lingvo files it's been
TIG [me!]- English = EN-US
Didier Bur and Pilou - French = FR
Defisto and Diego-Rodriguez - Spanish = ES
Hebeijianke - Chinese = ZH-CN
Burkhard - German = DE -
I have also translated a couple (like Rick's Windowizer4) and also started to translate some (but never finished). My concern is that since there is no Hungarian version for SU anyway, I am not sure how big the "market" would be. Also, when I started to translate Twilight for instance, I realised that I do not even know if there are "common" Hungarian terms for certain rendering expressions
-
@gaieus said:
I realised that I do not even know if there are "common" Hungarian terms for certain rendering expressions
Yes - same problem in Norwegian. Some terms are hard to translate. Just the other day I tried to work out a translation for "Soft Selection".
Some years ago when I did some translations I was searching for guidance to translating - and some of the best tips I found was for a Norwegian mozilla page where they listed many common UI elements.And - the most crucial part of localizing: Don't translate the words - translate the meaning.
I see all too often in Norwegian translation that the words are translated literally, which just ends up as near nonsense.
-
@tig said:
For my deBabelizer lingvo files it's been
TIG [me!]- English = EN-US
Didier Bur and Pilou - French = FR
Defisto and Diego-Rodriguez - Spanish = ES
Hebeijianke - Chinese = ZH-CN
Burkhard - German = DEThat looks to be most major languages - and probably the most relevant.
I've not made my plugins translatable as so far. It's really not been a priority. But I'm looking into it now. Thinking I'll add a generic system to my TT_Lib. I was looking at the bundled SU system, but I was no happy about it. Too verbose for each string.
-
Yes be more simple possible and don't forget that the caracters'number of the tooltip is limited!!!
-
Came across this today: http://msdn.microsoft.com/en-gb/goglobal/bb688105.aspx
MS has a great search service online where one can search in computer software terms which MS uses in their products and see how they are translated. -
It's hard to get the exact translation even in French or Spanish - my translators argue about edges/lines = borde ou arête... [EDIT: correction it's 'bord'
] and what 'Loft' is in Spanish... in the end it's a compromise... BUT the way I write my lingvo files any user can change the text to suit what they want it to be anyway ! E,G. change your EN-US file to Esperanto words to the right of the <==> and now you are cooking [nun vi kuiri]... -
This is where taking reference from other applications help. What terms has been established before. (All though it's a judgement call to decide if previous translations are good ones)
-
Human's read is always necessary
Example : the above TIG@unknownuser said:
edge/line = borde ou arête
even this word "borde" exist it can't be here in this situation
"bord" yes
After all depends of the context
bord/ligne
côté/ligne
arête/ligne
segment/ligne
etc... -
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' ? -
@ TIG for your edit
no plural is "bords" ! "border" is a verb -->"il borde" (3 th person "he limits"
"bordé" exist on a boat (with accent) Plural will be here "bordés"
-
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?
Advertisement