Re: [Audacity-devel] AUDACITY_NAME

[James C. <cr...@in...>]

On 27/04/2011 01:39, Vaughan Johnson wrote:
> I see several places #ifdef AUDACITY_NAME, but it's never defined.
> What's the idea there?
It was introduced by Lynn Alan for Cleanspeech, as he changed the name 
of Audacity to Cleanspeech when compiled in that mode.  As a result 
names of preferences files and the like changed - not such a bad thing 
as it reduced risk of conflict between the variants.

We should not be changing the name of the APP for minor mode changes, 
particularly as we're moving towards doing such mode changes through 
plug-ins.  You shouldn't need to worry about the AUDACITY_NAME code.  
It's all inactive.  It's history now.

> And there are numerous occurrences of wxT("Audacity") that I think
> should probably be AUDACITY_NAME.
I don't see we gain anything we want by making that change.

> And there's one occurrence of _("Audacity"), but it's the trademarked
> name of the app, so should never be translated, right?
>
We also have 36 translated strings that start with _("Audacity, so it is 
more a question of deciding a consistent policy with the translators - 
one that might even vary between languages.  The idea that the name 
Audacity has something to do with audio might well get lost in 
translation....  It means that including 'Audacity' in a translatable 
string is just fine.


Overall, we don't particularly want to encourage people to take Audacity 
source, rename it as 'MyWhizzBangDAW' and sell it on at e-Bay as a new 
product, so worrying about trying to factor out the name Audacity is not 
useful effort.

We did decide that for custom builds of Audacity for specific 
applications, we'd use a formula like 'Powered by Audacity'.  It should 
therefore never be a surprise to a user of a specialized version to see 
a phrase like 'Audacity could not open file...', at least the 'Audacity' 
in the message should not be a surprise.

The more vital and more difficult topic is whether to have separate 
versions of preferences with a new name for customized versions, 
including versions customized by plug-in.  That depends on how extensive 
the preferences changes are.  I'd say that mostly we won't.

--James.