Thread: [Audacity-devel] wxT and things
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Alexandre P. <ale...@gm...> - 2011-09-17 23:08:38
|
Hi, There seems to be some abuse of wxT lately: it's used for messages that should be translatable and they can't be while they are marked with wxT. I fixed a couple of such cases, but a quick grep over src/ shows a lot more occurencies. The problem is that I'm not sure which things are user visible. For example, some of GStreamer related messages sound like they are intended to be read, e.g.: src/GStreamerLoader.cpp: return wxString(wxT("GStreamer support is not compiled in")); src/GStreamerLoader.cpp: wxString extensions = wxT("Extensions:"); src/GStreamerLoader.cpp: wxString versionString = wxT("GStreamer is not found"); But I simply don't know how to check that, because I don't see how to compile Audacity with support for GStreamer. There is no ./configure switch for that. Any hints? Alexandre Prokoudine http://libregraphicsworld.org |
From: Richard A. <ri...@au...> - 2011-09-19 11:23:48
|
On Sun, 2011-09-18 at 03:08 +0400, Alexandre Prokoudine wrote: > But I simply don't know how to check that, because I don't see how to > compile Audacity with support for GStreamer. There is no ./configure > switch for that. > > Any hints? It was added by LRN (who did the FFmpeg support), but as he only built on Windows, didn't make it into the configure build system. We've never thought of it as a releaseable feature, and I've never tried to make it build (I can't even remember which grstreamer version it requires). For that reason, keeping the strings out of the translation files seems reasonable, as they will otherwise be work for no benefit. Richard |
From: Alexandre P. <ale...@gm...> - 2011-09-19 11:28:41
|
On Mon, Sep 19, 2011 at 3:23 PM, Richard Ash wrote: > It was added by LRN (who did the FFmpeg support), but as he only built > on Windows, didn't make it into the configure build system. We've never > thought of it as a releaseable feature, and I've never tried to make it > build (I can't even remember which grstreamer version it requires). > > For that reason, keeping the strings out of the translation files seems > reasonable, as they will otherwise be work for no benefit. Fine with me :) Will I not break some sort of a strings freeze if I fix more GStreamer unrelated messages, should I stumble upon them withing next couple of weeks? Alexandre Prokoudine http://libregraphicsworld.org |
From: Martyn S. <mar...@gm...> - 2011-09-19 23:17:28
|
<snip> > Will I not break some sort of a strings freeze if I fix more GStreamer > unrelated messages, should I stumble upon them withing next couple of > weeks? As far as I know, there is no 'string freeze' present at the moment. We are in a very long 'feature freeze' trying to solve a particularly difficult P2 prior to a release, which is stopping a lot of development and rather killing enthusiasm. But I see no reason not to go ahead with these type of changes. HTH Martyn > Alexandre Prokoudine > http://libregraphicsworld.org > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > Learn about the latest advances in developing for the > BlackBerry® mobile platform with sessions, labs& more. > See new tools and technologies. Register for BlackBerry® DevCon today! > http://p.sf.net/sfu/rim-devcon-copy1 > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Gale A. <ga...@au...> - 2011-09-21 19:29:05
|
| From Martyn Shaw <mar...@gm...> | Tue, 20 Sep 2011 00:17:20 +0100 | Subject: [Audacity-devel] wxT and things > <snip> > > > Will I not break some sort of a strings freeze if I fix more GStreamer > > unrelated messages, should I stumble upon them withing next couple of > > weeks? > > As far as I know, there is no 'string freeze' present at the moment. > We are in a very long 'feature freeze' trying to solve a particularly > difficult P2 prior to a release, which is stopping a lot of > development and rather killing enthusiasm. But I see no reason not to > go ahead with these type of changes. My understanding is that we are not making any "unnecessary" string changes until after 2.0 - changing a string that was wrong or badly misleading/confusing is still probably OK, a "would be nice tweak" should probably be left because it risks making translations incomplete. But it there was no translation at all before, it seems fine to me to add strings where they are missing? Gale |