[Bf-translations-dev] German translation - some edits

[Gaia]

Hi there;

Cool to see that the german translation moves on :)
I have a few remarks about anglicisms:

I believe that it is very problematic to avoid anglicisms,
especially for very common terms like Face, Vertex, Clip...

I personally would focus more on translating the tool tips and
keep the visible GUI elements mostly as they are.

Why that ? Because you will get a hell of a problem
when you are trying to follow a non native tutorial
which was made with the default setup while you work
with your native setup.

And most tutorials on the web are made with the
default settings (maybe on purpose).

At the end it might be a matter of taste,
so this are just my 2 cents here :)


On 15.06.2012 19:36, Michael Färber wrote:
> Hi Cody,
>
>
>> great to hear that from you! I stumbled upon your comments several times
>> in the PO file, looks like you've been one of the most active german
>> translators :)
> I feel honoured. :)
>
>> Using infinitives is deffo a general decision and should be noted
>> somewhere ->   new wiki page?
>>
>> http://wiki.blender.org/index.php?title=Dev:DE/Doc/How_to/Translate_Blender&action=edit
> That's a very good idea. I created the wiki page and put in some text
> which I sent to a previous translator some time ago. Feel free to add
> your ideas there.
>
>> Mont29 gave me svn access and I already commited without further changes
>> (I'm always afraid of data loss due to hardware defects and such), might
>> be worth to revert and re-commit with changes following your suggestions.
> I agree with what Bastien wrote; I'll review your changes and adapt
> them, if necessary.
>
>> Is there a Windows-alternative for POedit which works well together with
>> SVN?
>>
>> Better PO editor - http://sourceforge.net/projects/betterpoeditor/
>> GTed - http://www.gted.org/#Screenshots
> I don't know about this, because I don't use Windows, but I use a simple
> text editor in Linux and execute SVN commands manually. That worked
> quite well for me so far.
>
>> An addon for in-place translation would be awesome indeed, it would let
>> translators focus on important strings visible in UI, leaving Operator
>> descriptions untouched for now (the ones which show in pyconsole on
>> autocomplete).
>>
>> But I wonder if this is going to work... Aren't identical strings
>> grouped together? Like... Volume properties for Speakers and Render
>> types -->   both msgid "Volume". If I translated the latter, wouldn't both
>> change?
> Indeed, such a thing would be amazing! :)
> Anyway, in some cases like your "Volume" example, such an automatic
> solution would fail, but it would definitely help in>95% of all strings.
>
>> Decisions we have to make on how to translate certain words:
>>
>> Vertices - Eckpunkte / Vertices?
>> -->   should we avoid anglicisms whenever possible?
> I am all for avoiding unnecessary anglicisms. :)
> In this case, I favour "Eckpunkte".
>
>> Face, surface - Fläche / Face, Oberfläche
> How about "Seitenfläche" and "Oberfläche"?
>
>> Mask edit(ing) - Masken / Masken bearbeiten (mode dropdown list)
> Not sure here ...
>
>> Sculpt mode - Skulpturmodus / Skulptur / Meißeln / Formen
> I like "Skulpturmodus".
>
>> F-Curve - Kurve, Funktionskurve, Verlaufskurve, Segmentkurve?
> I favour "F-Kurve", because F-Curve seems to stand for "function curve",
> and we could translate that one to one to "F-Kurve".
>
>> NLA, Strip - ???
> "Streifen"? I would leave NLA as it is ... do you know what it actually
> means?
>
>> Clip - Clip? (Videoausschnitt / Filmstück would be sort of awkward...)
> "Film"?
>
>> Bevel - Abrunden, Fase, Abschrägung? (but Curve bevel seems to add
>> thickness, so more generic "Runden" might be a better choice)
> What about "Schrägen"? That's at least what dict.cc offers ... ;)
>
>> Collapse - kollabieren, (ein)stürzen, kippen, zusammenfalten, ...
> In which context? If we use it in the context of tree views,
> "Einklappen" or something like that might be appropriate.
>
>> Rip - Auseinanderreißen?
> I'm a bit clueless here, that depends completely on the context.
>
>
>> I wonder if certain words were better kept as anglicisms, to avoid
>> confusion for python programmers. The bpy api itself won't be translated:
>>
>> bpy.data.meshes[0] -->   not bpy.daten.netze[0] in german translation
>>
>> If mesh was kept as Mesh, people could find API data structure more
>> easily. In other cases, it would be silly to use the english word, e.g.
>> Rip - doesn't mean anything to a german who don't knows any english :(
> I have actually already translated Mesh as "Mesh", so I'd stick to that
> in the particular case.
> But yes, in general, we should see that we don't completely reinvent CG
> language, but find a good mix of German and English.
>
>> We should really decide about often used words and put them on Wiki, so
>> everyone can look them up.
> I'm not sure about that; I think such a list might get quite big pretty
> soon and updating it all the time might be a hassle, but if you take up
> the effort, why not? :)
> What I do in general is to search through the translation if somebody
> already translated a specific item; e.g. when looking for a translation
> of Mesh, I looked for
>
> msgstr ".*Mesh
>
> (where .* is a regular expression standing for an amount of characters)
> to find out whether I had already translated something as "Mesh", and
> that brought up "Mesh-Optionen".
> So if you look for a good PO editor, you might consider its ability to
> search in translations.
>
>
> Cheers,
> Much
>
>
> P.S.: Oh, and welcome to the German translation team! :)
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev