Re: [Audacity-quality] "Show Log"

[Vaughan J. <va...@au...>]

On 8/18/2010 1:53 PM, Gale Andrews wrote:
> 
> | From Richard Ash <ri...@au...> 
> | Wed, 18 Aug 2010 20:46:24 +0100
> | Subject: [Audacity-quality] "Show Log"
>> On Tue, 2010-08-17 at 16:08 -0700, Vaughan Johnson wrote:
>>> Btw, most (maybe all) of these are wrapped in wxT, so they don't get
>>> translated. I hate to add a burden on the translators, but I think they
>>> should be translated if the user is going to see them (i.e., wxLogDebug
>>> need not be translated because they appear only in debug builds, but the
>>> others should). Agree?
>>
>> It would be nice, but it's not a high priority for translators. It also
>> reduces the googleability of the log messages. Pity there's no mechanism
>> for marking the "priority" of messages in the pot file so as to indicate
>> what is important (major parts of the UI) vs what is not so important
>> (rarely used error messages). Some sort of profiler for strings?
> 
> Translating an Audacity warning like "Project check found inconsistencies 
> inspecting the loaded project data" is OK, but I wouldn't think you'd want 
> to translate any error that the OS produced, would you?

Those are generated within wxWidgets, and that code (e.g., "can't open
file...") already is marked for translation. So that's another reason to
mark ours for translation.


> 
> Another point IMO would be to raise the priority of getting the Manual 
> translated, which I'd think should have priority over most parts of the 
> translation except the UI. But the ad hoc Manual Wiki translating we 
> have now doesn't seem to appeal much to current translators.

Different topic. Maybe start a thread on audacity-translation to get
ideas on that.


> 
>  
>>>>> Does it make sense to move it to the View menu, in the list with
>>>>> History, etc?
>>>>
>>>> If it contains only error information, my slight preference would be that it 
>>>> stays in the Help menu (and maybe it's called "Error Log").
>>>
>>> No, it still has several info-only messages, that I think the user will
>>> actually find useful (vs the ones about loading each component of
>>> FFmpeg, for example).
>>
>> I think it does, in particular if I commit some of the local changes I
>> made to debug mixer toolbar issues which print quite a lot of
>> information about what devices are found and what we can control to the
>> log (and explain why sometimes the toolbar isn't there).
> 
> Given some analogous information is in Audio Device Info, that again 
> suggests to me that perhaps the Log should remain under Help. 
> 
I don't feel strongly about it, so okay. But it seems to me, then, that
Show Log should be grouped with Audio Device Info rather than with the
Manual.

- Vaughan