Interesting, I might join and help later on if you like, when time allows. Have done quite a lot of software translations before, and know how tricky this can be.
I personally agree, that many things are best left untranslated. “Tag” for instance. Dutch does not have a proper word for that, and it wouldn’t be just as recognizable.
“Headroom” is a tricky one, because it is an inaccurate description of this setting. Translating that, gives nonsense like “dynamic margin/reserve”, which is not what it does.
In reality, this setting gives you ATTENUATION (Dutch : verzwakking). Or GAIN actually, taking the negative sign in account. Nothing more, nothing less. But that doesn’t sound as sexy, as “headroom” :).
Setting this to -3dB does not give you negative headroom obviously :). And neither does it give +3dB headroom : it gives you the headroom of your music file, an extra 3dB headroom, and then subtracting the gain of the following DSP.
The end result could still be clipping (=no headroom available).
There are probably more cases like this one, where the English wording is not accurate enough, for a direct translation.
Some suggestions :
Tag -> ? Niet vertalen.
Highlights -> Depends on context, but I feel “Uitgelicht” seems appropriate. Not ‘here is the best-of-the best’, but : “I have these and these examples for you”.
Folder -> Map
Volume Leveling -> “Volume normaliseren”. More accurate, but also more ugly : “Luidheid normaliseren” (normalize loudness) ?
Headroom -> “Dynamische marge”, “dynamische reserve” (but I would prefer the more accurate gain/attenuation, see above).
Mapping -> Kanaaltoewijzing (I’m sure there is a better one, it’s on the tip of my tongue :P)
Item -> I’m missing the context on this one, no suggestions. “Item” is a fine Dutch word in my book, anyway :).
(Oh, I see that the translations site is ‘wikipedia’-style, with possibility for commenting/voting on each separate entry. Wouldn’t it be more logical/structured to have discussions like these over there, instead of here on the forums ?)
