I just released version 1.2.0-pre2.
Translations to the website are needed. You should be able to copy
and paste most of the text for the homepage. The other page I
would recommend updating soon is betanotes-1.2.0-pre1.php, which
has been updated to include the changes in both 1.2.0-pre1 and
Reminder: go to http://audacity.sourceforge.net/edit/ and type
the password. Email me for the password if you need it.
All recent translation updates have been backed up successfully.
However, just to be safe, you can check the translation editor
after 24 hours. If any of your pages are still marked
"pending", that means they were NOT backed up - please contact
me and I will fix the problem.
running Nyquist plug-ins with Audacity-1.2.0-pre1 + pre2 results in an
error ("No Audio Data"), when there is another language then english
selected. First I thought it depends on my german translation... but
this crazy thing will happen with lots of other language files, too.
Problems by using Nyquist with other languages than English at most by
Audacity 1.2.0-pre1 and pre2
OS: Win2K, WinXP(at most) and Win98SE
Affected Plugins: nearly all.
On Linux based systems most things go better, but in two cases the same
problems will happen: Using 'Click Track' and 'Pluck' with other
languages than English = 'No Audio Data'...
Matt, Dominic... any ideas?
Op wo 01-10-2003, om 10:20 schreef Heiko:
> running Nyquist plug-ins with Audacity-1.2.0-pre1 + pre2 results in an
> error ("No Audio Data"), when there is another language then english
> selected. First I thought it depends on my german translation... but
> this crazy thing will happen with lots of other language files, too.
This happens in languages that use a ',' instead of a '.' as a decimal
If you do an
before starting up audacity, the problem is gone.
But it would be nice if this could be fixed before 1.2.0
thanks a lot for your message!!!
Am Mit, 2003-10-01 um 13.45 schrieb Tino Meinen:
> This happens in languages that use a ',' instead of a '.' as a decimal
> If you do an
> export LANG=C
THATS IT! ;-)
I just hope that this will be fixed in the 1.2.0 Final. Anyway... for me
it's okay for now. ;-)