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

[CoDEmanX]

Hi Michael,

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 :)

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

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.

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

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?


Decisions we have to make on how to translate certain words:

Vertices - Eckpunkte / Vertices?
--> should we avoid anglicisms whenever possible?

Face, surface - Fläche / Face, Oberfläche

Mask edit(ing) - Masken / Masken bearbeiten (mode dropdown list)

Sculpt mode - Skulpturmodus / Skulptur / Meißeln / Formen

F-Curve - Kurve, Funktionskurve, Verlaufskurve, Segmentkurve?

NLA, Strip - ???

Clip - Clip? (Videoausschnitt / Filmstück would be sort of awkward...)

Bevel - Abrunden, Fase, Abschrägung? (but Curve bevel seems to add 
thickness, so more generic "Runden" might be a better choice)

Collapse - kollabieren, (ein)stürzen, kippen, zusammenfalten, ...

Rip - Auseinanderreißen?

and many many more...


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 :(


We should really decide about often used words and put them on Wiki, so 
everyone can look them up.

Looking forward to a localized german blender,
kind regards,

Cody



Am 15.06.2012 12:55, schrieb Michael Färber:
> Hi,
>
>
> thanks for your effort!
> At the moment, I put my own translation efforts on hold, mostly because
> it is very tedious to translate the program well for now. However,
> Bastien recently wrote that he would try to find some time for a
> translation addon, which would simplify the translation process greatly.
> For example, when you are able to translate the program from within the
> GUI, you will avoid most context problems, where you may mistranslate
> strings because you don't know how they are used in the GUI. At the
> moment, to avoid errors, you basically have to find out in which places
> a certain string is used before translating it, and that eats enormous
> amounts of time.
>
> Anyway, I looked at your updates, and a very large amount of them looks
> very good. :)
> I'll try to find some time soon to check them and commit them afterwards!
> Just some comments in the meanwhile: Please don't use PoEdit if you can,
> because it modifies files in a way that makes patches unnecessarily big.
> Also, always use the infinitive when translating verbs -- you've done a
> /very/ good job on this in general, but I encountered one string which
> you translated as "Stoppt die Animations-Wiedergabe", whereas it should
> be something like "Animations-Wiedergabe stoppen". But considering how
> well you translated the rest, that's just nitpicking really. :)
>
> So, thanks again, I'll look at it in more detail soon!
>
>
> Cheers,
> Michael
>
>
> P.S.: For general decisions on how to translate certain terms, I'm open
> to suggestions. :) It would be cool if you could note such terms as you
> encounter them, and we discuss possible translations afterwards. In
> general, it is helpful to also find out where such terms appear in the UI.
>
>
> Le 2012-06-14 17:49, CoDEmanX a écrit :
>> So i had a look at the german translation and a realized, that less
>> than 12% were done, thousand fuzzy.
>>
>> I spent some time on it, but this is really nothing 1 person could do.
>>
>> This really needs a translation team of 5 or more persons and some
>> general decisions, how to translate certain words.
>>
>> Is there anyone from old translation team?
>>
>>
>> _______________________________________________
>> Bf-translations-dev mailing list
>> Bf-translations-dev at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>
>
>
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev