On 10/10/2013 5:52 AM, Federico Miyara wrote:
>
> Vaughan,
>
>> So do we tell him to ignore it for 2.0.5 or does somebody have an
>> explanation for him?
>
> He is already providing the explanation... There is a line code
>
>> szr3->Add( new wxStaticText(this, wxID_ANY, _("Hz  Stopband Ripple:")), 0 );
>
> that for programming simplicity gathers in a single string "Hz" and
> "Stopband Ripple" ad this seems to be a little confusing. That's all.

My understanding from Yuri was that the problem he was having what that 
the term was unclear to him, so it was difficult to translate. So I 
thought it meant it needed an i18n-hint.

But I guess by saying "contains a word puzzle", he indeed meant the order.


>
> However, I think we shouldn't call these parameters "Passband Ripple"
> or "Stopband Ripple" in the case of Butterworth. They are incorrect
> or at least confusing, since Butterworth doesn't have ripple but only
> attenuation. Thus, they should be "Passband attenuation" and
> "Stopband attenuation". I know it is a a bit tricky, but perhaps
> labels should adapt depending on approximation type (Butterworth,
> Chebychev...).

Still would probably be good to have an i18n-hint, especially per this 
terminological debate. After 2.0.5, please!

Thanks,
Vaughan



>
> Regards,
>
> Federico
>
>

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Audacity-translation mailing list
Audacity-translation@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/audacity-translation

Reply via email to