Message files for wxWidgets 2.8.10
|
|
Leland (Audacity Team)
|
I've uploaded the Windows 2.8.10 version of the wxWidgets message files to:
http://audacity.homerow.net/index.php?dir=windows%2F&download=locales-2.8.10-msw.zip These need to be unzipped and included in the next beta and subsequent betas/releases as they contain the translations for all of the Widgets strings. Leland ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Gale (Audacity Team)
|
| From Leland <[hidden email]> | Thu, 09 Jul 2009 10:29:56 -0500 | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > I've uploaded the Windows 2.8.10 version of the wxWidgets message files to: > > http://audacity.homerow.net/index.php?dir=windows%2F&download=locales-2.8.10-msw.zip > > These need to be unzipped and included in the next beta and subsequent > betas/releases as they > contain the translations for all of the Widgets strings. Hi Leland Looks as if I missed some e-mails someplace. Is this so translators can translate shortcuts? And are these to go alongside the Audacity.mo files in each language folder? Gale ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Leland (Audacity Team)
|
Gale Andrews wrote:
> | From Leland <[hidden email]> > | Thu, 09 Jul 2009 10:29:56 -0500 > | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 >> I've uploaded the Windows 2.8.10 version of the wxWidgets message files to: >> >> http://audacity.homerow.net/index.php?dir=windows%2F&download=locales-2.8.10-msw.zip >> >> These need to be unzipped and included in the next beta and subsequent >> betas/releases as they >> contain the translations for all of the Widgets strings. > > Hi Leland > > Looks as if I missed some e-mails someplace. Is this so translators > can translate shortcuts? And are these to go alongside the Audacity.mo > files in each language folder? Yes to both. I'll do the shortcut thing automatically, but I haven't spent enough time on it and didn't want push it into 1.3.8. Leland ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Martyn Shaw-2
|
Leland wrote: > Gale Andrews wrote: >> | From Leland <[hidden email]> >> | Thu, 09 Jul 2009 10:29:56 -0500 >> | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 >>> I've uploaded the Windows 2.8.10 version of the wxWidgets message files to: >>> >>> http://audacity.homerow.net/index.php?dir=windows%2F&download=locales-2.8.10-msw.zip >>> >>> These need to be unzipped and included in the next beta and subsequent >>> betas/releases as they >>> contain the translations for all of the Widgets strings. >> Hi Leland >> >> Looks as if I missed some e-mails someplace. Is this so translators >> can translate shortcuts? And are these to go alongside the Audacity.mo >> files in each language folder? > > Yes to both. I'll do the shortcut thing automatically, but I haven't > spent enough time on it and didn't want push it into 1.3.8. So af/wxstd.mo ends up as installDir\Languages\af\wxstd.mo once the user has installed Audacity? I guess only person actually doing the release build needs to do this, so who is that? Martyn > Leland > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Vaughan Johnson
|
Martyn Shaw wrote: > Leland wrote: > >> Gale Andrews wrote: >> >>> | From Leland <[hidden email]> >>> | Thu, 09 Jul 2009 10:29:56 -0500 >>> | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 >>> >>>> I've uploaded the Windows 2.8.10 version of the wxWidgets message files to: >>>> >>>> http://audacity.homerow.net/index.php?dir=windows%2F&download=locales-2.8.10-msw.zip >>>> >>>> These need to be unzipped and included in the next beta and subsequent >>>> betas/releases as they >>>> contain the translations for all of the Widgets strings. >>>> >>> Hi Leland >>> >>> Looks as if I missed some e-mails someplace. Is this so translators >>> can translate shortcuts? And are these to go alongside the Audacity.mo >>> files in each language folder? >>> >> Yes to both. I'll do the shortcut thing automatically, but I haven't >> spent enough time on it and didn't want push it into 1.3.8. >> > > So af/wxstd.mo ends up as installDir\Languages\af\wxstd.mo once the > user has installed Audacity? > > I guess only person actually doing the release build needs to do this, > so who is that? > > - V > Martyn > > >> Leland >> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> >> > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Vaughan Johnson <[hidden email]> | Fri, 10 Jul 2009 15:49:43 -0700 | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > Martyn Shaw wrote: > > Leland wrote: > > > >> Gale Andrews wrote: > >> > >>> | From Leland <[hidden email]> > >>> | Thu, 09 Jul 2009 10:29:56 -0500 > >>> | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > >>> > >>>> I've uploaded the Windows 2.8.10 version of the wxWidgets message files to: > >>>> > >>>> http://audacity.homerow.net/index.php?dir=windows%2F&download=locales-2.8.10-msw.zip > >>>> > >>>> These need to be unzipped and included in the next beta and subsequent > >>>> betas/releases as they > >>>> contain the translations for all of the Widgets strings. > >>>> > >>> Hi Leland > >>> > >>> Looks as if I missed some e-mails someplace. Is this so translators > >>> can translate shortcuts? And are these to go alongside the Audacity.mo > >>> files in each language folder? > >>> > >> Yes to both. I'll do the shortcut thing automatically, but I haven't > >> spent enough time on it and didn't want push it into 1.3.8. > >> > > > > So af/wxstd.mo ends up as installDir\Languages\af\wxstd.mo once the > > user has installed Audacity? > > > > I guess only person actually doing the release build needs to do this, > > so who is that? > > > > > I can do the Windows builds, unless Gale wants to. At the moment I think I'm OK with doing it on Sunday, if it's circa 19:00 UTC or thereafter? Before then, I won't be able to. Since I'll be building both releases anyway till then, it may make more sense. Either way: * Do I assume the wxstd.mo files will have any visible effect yet in how the shortcuts appear in the interface? I don't see any effect in French (the only one I tried) * Are the two Windows zip files including help? * Are we agreed as discussed that the Windows executable is called audacity_beta.exe? This appears to work OK with appropriate changes to the installer if you rename "audacity.exe" to "audacity_beta" exe in the build folder before building the installer. The point of this is so that people who already have audacity.exe (Stable) installed can create "open with" associations with 1.3.8 for MP3, OGG, WAV, WMA, FLV etc. Otherwise, they cannot, due to Windows limitations. Downside is I suppose we need separate .iss files for Beta? * Reading the "rules" on Google Code, it seems we can label old download files as "deprecated" so that the "current" view only has currently supported files. Anyone wanting unsupported ones has to choose the "All downloads" or "Deprecated downloads" view. So would we label the 1.3.7 downloads as "deprecated"? Gale ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Leland (Audacity Team)
|
Gale Andrews wrote:
> > * Do I assume the wxstd.mo files will have any visible effect > yet in how the shortcuts appear in the interface? I don't see > any effect in French (the only one I tried) > They menu shortcuts will not change based on locale in 1.3.8. I will get that in soon after release. But, those message files are much more than menu shortcuts as there's a little less than 1500 individual message strings. ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Vaughan Johnson
|
In reply to this post
by Gale (Audacity Team)
Gale Andrews wrote: > | From Vaughan Johnson <[hidden email]> > | Fri, 10 Jul 2009 15:49:43 -0700 > | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > >>> ... >>> >>> >> I can do the Windows builds, unless Gale wants to. >> > > At the moment I think I'm OK with doing it on Sunday, if it's > circa 19:00 UTC or thereafter? Before then, I won't be able to. > Since I'll be building both releases anyway till then, it may > make more sense. > chance on getting the MixerBoard in shape! > ... > * Are we agreed as discussed that the Windows executable > is called audacity_beta.exe? This appears to work OK > with appropriate changes to the installer if you rename > "audacity.exe" to "audacity_beta" exe in the build folder > before building the installer. The point of this is so that people > who already have audacity.exe (Stable) installed can > create "open with" associations with 1.3.8 for MP3, OGG, > WAV, WMA, FLV etc. Hadn't heard that idea. We could make the sln build it with that name, so it doesn't have to be renamed. Just have to change the sln again when it goes back to a stable release. > Otherwise, they cannot, due to > Windows limitations. Downside is I suppose we need separate > .iss files for Beta? > Not really. The two iss files have to change for every release anyway, so we can just change them to use audacity_beta. And change it back for the stable release. Seems like a pretty marginal case for the extra work, though. I doubt a very big percentage of users have both versions of Audacity installed and know enough to set up file associations. > > * Reading the "rules" on Google Code, it seems we can label old > download files as "deprecated" so that the "current" view only > has currently supported files. Anyone wanting unsupported ones > has to choose the "All downloads" or "Deprecated downloads" > view. So would we label the 1.3.7 downloads as "deprecated"? > > Sounds reasonable to me. But I don't think it matters because we'll be linking directly to the files, right? So most users will never see the list or a Google Code page at all. - V ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Vaughan Johnson <[hidden email]> | Sat, 11 Jul 2009 14:04:09 -0700 | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > Gale Andrews wrote: > > | From Vaughan Johnson <[hidden email]> > > | Fri, 10 Jul 2009 15:49:43 -0700 > > | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > > > ... > > * Are we agreed as discussed that the Windows executable > > is called audacity_beta.exe? This appears to work OK > > with appropriate changes to the installer if you rename > > "audacity.exe" to "audacity_beta" exe in the build folder > > before building the installer. The point of this is so that people > > who already have audacity.exe (Stable) installed can > > create "open with" associations with 1.3.8 for MP3, OGG, > > WAV, WMA, FLV etc. > Hadn't heard that idea. We could make the sln build it with that name, > so it doesn't have to be renamed. Just have to change the sln again > when it goes back to a stable release. It was discussed here in context of the "Open with" bug with .aup association that turned out not to be a bug: http://n2.nabble.com/P4-Audacity-executable-in-%22Open-With...%22-td2646747.html#a2646747 > > Otherwise, they cannot, due to > > Windows limitations. Downside is I suppose we need separate > > .iss files for Beta? > > > Not really. The two iss files have to change for every release anyway, > so we can just change them to use audacity_beta. And change it back for > the stable release. > > Seems like a pretty marginal case for the extra work, though. I doubt a > very big percentage of users have both versions of Audacity installed > and know enough to set up file associations. I think of those Windows users who use the Beta, quite a high proportion do install alongside the Stable, not uninstall it. We make a point of mentioning this on the site, and it happens by default if the user doesn't change the Beta installation path. I see this "file association" issue coming up once a twice or month, so not huge but irritating for those savvy enough to try it. Plus there are some people who see "audacity.exe" in the Beta installation folder, and think their Stable installation may have been overwritten because the executable name is the same. I would certainly make this change, and probably just rename the executable we build and note it in win/release.txt. > > * Reading the "rules" on Google Code, it seems we can label old > > download files as "deprecated" so that the "current" view only > > has currently supported files. Anyone wanting unsupported ones > > has to choose the "All downloads" or "Deprecated downloads" > > view. So would we label the 1.3.7 downloads as "deprecated"? > > > > > Sounds reasonable to me. But I don't think it matters because we'll be > linking directly to the files, right? So most users will never see the > list or a Google Code page at all. Yes. I would imagine users would only go there if they clicked the "alternate download" link. But if they do go there, it suggests they are having problems, so limiting the files they have to look at in the current downloads view makes sense to me. * If no other comments, I will leave the Help out of the zip. I'll try and make time to make a link to a zip of the dump on the front page of the Manual, which I think was agreed. * I see we are installing the "Modules" directory. Is there any actual functionality switched on that uses this? Gale ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Vaughan Johnson
|
Gale, I think this extra work is unwarranted at this point, since we're
going to release a new stable version in ~3 months. Distinguishing from 1.2.6 will be moot. We'd also need to make the beta installer know about the 1.3.7 exe by the different name. I just think it's too much overhead to switch it all now and switch it back before 2.0, and not very high priority. The small 1.3.8 (& 1.3.9) audience that wants it will just have to wait a few months. Okay? - V Gale Andrews wrote: > | From Vaughan Johnson <[hidden email]> > | Sat, 11 Jul 2009 14:04:09 -0700 > | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > >> Gale Andrews wrote: >> >>> | From Vaughan Johnson <[hidden email]> >>> | Fri, 10 Jul 2009 15:49:43 -0700 >>> | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 >>> >>> ... >>> * Are we agreed as discussed that the Windows executable >>> is called audacity_beta.exe? This appears to work OK >>> with appropriate changes to the installer if you rename >>> "audacity.exe" to "audacity_beta" exe in the build folder >>> before building the installer. The point of this is so that people >>> who already have audacity.exe (Stable) installed can >>> create "open with" associations with 1.3.8 for MP3, OGG, >>> WAV, WMA, FLV etc. >>> >> Hadn't heard that idea. We could make the sln build it with that name, >> so it doesn't have to be renamed. Just have to change the sln again >> when it goes back to a stable release. >> > > It was discussed here in context of the "Open with" bug with .aup > association that turned out not to be a bug: > http://n2.nabble.com/P4-Audacity-executable-in-%22Open-With...%22-td2646747.html#a2646747 > > > >>> Otherwise, they cannot, due to >>> Windows limitations. Downside is I suppose we need separate >>> .iss files for Beta? >>> >>> >> Not really. The two iss files have to change for every release anyway, >> so we can just change them to use audacity_beta. And change it back for >> the stable release. >> >> Seems like a pretty marginal case for the extra work, though. I doubt a >> very big percentage of users have both versions of Audacity installed >> and know enough to set up file associations. >> > > I think of those Windows users who use the Beta, quite a high > proportion do install alongside the Stable, not uninstall it. > We make a point of mentioning this on the site, and it happens > by default if the user doesn't change the Beta installation path. > > I see this "file association" issue coming up once a twice or month, > so not huge but irritating for those savvy enough to try it. Plus > there are some people who see "audacity.exe" in the Beta installation > folder, and think their Stable installation may have been overwritten > because the executable name is the same. I would certainly make this > change, and probably just rename the executable we build and note it > in win/release.txt. > > > >>> * Reading the "rules" on Google Code, it seems we can label old >>> download files as "deprecated" so that the "current" view only >>> has currently supported files. Anyone wanting unsupported ones >>> has to choose the "All downloads" or "Deprecated downloads" >>> view. So would we label the 1.3.7 downloads as "deprecated"? >>> >>> >>> >> Sounds reasonable to me. But I don't think it matters because we'll be >> linking directly to the files, right? So most users will never see the >> list or a Google Code page at all. >> > > Yes. I would imagine users would only go there if they clicked > the "alternate download" link. But if they do go there, it suggests > they are having problems, so limiting the files they have to look > at in the current downloads view makes sense to me. > > * If no other comments, I will leave the Help out of the zip. I'll try > and make time to make a link to a zip of the dump on the front > page of the Manual, which I think was agreed. > > * I see we are installing the "Modules" directory. Is there any > actual functionality switched on that uses this? > > > > > Gale > > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Vaughan Johnson <[hidden email]> | Mon, 13 Jul 2009 14:52:10 -0700 | Subject: [Audacity-devel] "audacity_beta.exe" (was Re: Message files for wxWidgets 2.8.10) > Gale, I think this extra work is unwarranted at this point, since we're > going to release a new stable version in ~3 months. Distinguishing from > 1.2.6 will be moot. We'd also need to make the beta installer know about > the 1.3.7 exe by the different name. I just think it's too much overhead > to switch it all now and switch it back before 2.0, and not very high > priority. The small 1.3.8 (& 1.3.9) audience that wants it will just > have to wait a few months. Okay? > > - V Yes, I wondered subsequently if we'd have to have the installer remove audacity.exe from the Beta installation directory. I'm quite OK with not changing now, but I think we should release note the user problem. I'll make my 1.3.9-alphas "audacity.exe" too. Forward from 2.0, I still think having the Stable and Beta executables named the same can lead to confusion (aside from the specific Windows limitation at issue). Would you be agreed in principle to have the executable as "audacity_beta" from 2.1.0 onwards (when the installation folder will be "Audacity 2.1 (Beta)" I presume)? Gale > Gale Andrews wrote: > > | From Vaughan Johnson <[hidden email]> > > | Sat, 11 Jul 2009 14:04:09 -0700 > > | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > > > >> Gale Andrews wrote: > >> > >>> | From Vaughan Johnson <[hidden email]> > >>> | Fri, 10 Jul 2009 15:49:43 -0700 > >>> | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 > >>> > >>> ... > >>> * Are we agreed as discussed that the Windows executable > >>> is called audacity_beta.exe? This appears to work OK > >>> with appropriate changes to the installer if you rename > >>> "audacity.exe" to "audacity_beta" exe in the build folder > >>> before building the installer. The point of this is so that people > >>> who already have audacity.exe (Stable) installed can > >>> create "open with" associations with 1.3.8 for MP3, OGG, > >>> WAV, WMA, FLV etc. > >>> > >> Hadn't heard that idea. We could make the sln build it with that name, > >> so it doesn't have to be renamed. Just have to change the sln again > >> when it goes back to a stable release. > >> > > > > It was discussed here in context of the "Open with" bug with .aup > > association that turned out not to be a bug: > > http://n2.nabble.com/P4-Audacity-executable-in-%22Open-With...%22-td2646747.html#a2646747 > > > > > > > >>> Otherwise, they cannot, due to > >>> Windows limitations. Downside is I suppose we need separate > >>> .iss files for Beta? > >>> > >>> > >> Not really. The two iss files have to change for every release anyway, > >> so we can just change them to use audacity_beta. And change it back for > >> the stable release. > >> > >> Seems like a pretty marginal case for the extra work, though. I doubt a > >> very big percentage of users have both versions of Audacity installed > >> and know enough to set up file associations. > >> > > > > I think of those Windows users who use the Beta, quite a high > > proportion do install alongside the Stable, not uninstall it. > > We make a point of mentioning this on the site, and it happens > > by default if the user doesn't change the Beta installation path. > > > > I see this "file association" issue coming up once a twice or month, > > so not huge but irritating for those savvy enough to try it. Plus > > there are some people who see "audacity.exe" in the Beta installation > > folder, and think their Stable installation may have been overwritten > > because the executable name is the same. I would certainly make this > > change, and probably just rename the executable we build and note it > > in win/release.txt. > > > > > > > >>> * Reading the "rules" on Google Code, it seems we can label old > >>> download files as "deprecated" so that the "current" view only > >>> has currently supported files. Anyone wanting unsupported ones > >>> has to choose the "All downloads" or "Deprecated downloads" > >>> view. So would we label the 1.3.7 downloads as "deprecated"? > >>> > >>> > >>> > >> Sounds reasonable to me. But I don't think it matters because we'll be > >> linking directly to the files, right? So most users will never see the > >> list or a Google Code page at all. > >> > > > > Yes. I would imagine users would only go there if they clicked > > the "alternate download" link. But if they do go there, it suggests > > they are having problems, so limiting the files they have to look > > at in the current downloads view makes sense to me. > > > > * If no other comments, I will leave the Help out of the zip. I'll try > > and make time to make a link to a zip of the dump on the front > > page of the Manual, which I think was agreed. > > > > * I see we are installing the "Modules" directory. Is there any > > actual functionality switched on that uses this? > > > > > > > > > > Gale > > > > > > > > ------------------------------------------------------------------------------ > > Enter the BlackBerry Developer Challenge > > This is your chance to win up to $100,000 in prizes! For a limited time, > > vendors submitting new applications to BlackBerry App World(TM) will have > > the opportunity to enter the BlackBerry Developer Challenge. See full prize > > details at: http://p.sf.net/sfu/Challenge > > _______________________________________________ > > audacity-devel mailing list > > [hidden email] > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Vaughan Johnson
|
Gale Andrews wrote: > | From Vaughan Johnson <[hidden email]> > | Mon, 13 Jul 2009 14:52:10 -0700 > | Subject: [Audacity-devel] "audacity_beta.exe" (was Re: Message files for wxWidgets 2.8.10) > >> Gale, I think this extra work is unwarranted at this point, since we're >> going to release a new stable version in ~3 months. Distinguishing from >> 1.2.6 will be moot. We'd also need to make the beta installer know about >> the 1.3.7 exe by the different name. I just think it's too much overhead >> to switch it all now and switch it back before 2.0, and not very high >> priority. The small 1.3.8 (& 1.3.9) audience that wants it will just >> have to wait a few months. Okay? >> >> - V >> > > Yes, I wondered subsequently if we'd have to have the installer remove > audacity.exe from the Beta installation directory. I'm quite OK with not > changing now, but I think we should release note the user problem. I'll > make my 1.3.9-alphas "audacity.exe" too. > > Forward from 2.0, I still think having the Stable and Beta executables > named the same can lead to confusion (aside from the specific Windows > limitation at issue). Would you be agreed in principle to have the > executable as "audacity_beta" from 2.1.0 onwards (when the installation > folder will be "Audacity 2.1 (Beta)" I presume)? > I think that makes sense if we continue to have many beta releases and long intervals between stable releases. But I very much prefer we release stable versions *much* more often, like semi-annually rather than tri-annually (which 2.0 will almost be -- 1.2.6 was November 2006!). That would mean a much smaller percentage of users would want to keep both installed. Also, I think we agreed a while ago to change the naming convention away from the Linux standard of odd numbered revisions (which a small percentage of users know), and use "b" suffix for betas. So the next beta would be 2.1.0b or even 2.1b. But that discussion isn't urgent, by any means. - V > > > > Gale > > > > >> Gale Andrews wrote: >> >>> | From Vaughan Johnson <[hidden email]> >>> | Sat, 11 Jul 2009 14:04:09 -0700 >>> | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 >>> >>> >>>> Gale Andrews wrote: >>>> >>>> >>>>> | From Vaughan Johnson <[hidden email]> >>>>> | Fri, 10 Jul 2009 15:49:43 -0700 >>>>> | Subject: [Audacity-devel] Message files for wxWidgets 2.8.10 >>>>> >>>>> ... >>>>> * Are we agreed as discussed that the Windows executable >>>>> is called audacity_beta.exe? This appears to work OK >>>>> with appropriate changes to the installer if you rename >>>>> "audacity.exe" to "audacity_beta" exe in the build folder >>>>> before building the installer. The point of this is so that people >>>>> who already have audacity.exe (Stable) installed can >>>>> create "open with" associations with 1.3.8 for MP3, OGG, >>>>> WAV, WMA, FLV etc. >>>>> >>>>> >>>> Hadn't heard that idea. We could make the sln build it with that name, >>>> so it doesn't have to be renamed. Just have to change the sln again >>>> when it goes back to a stable release. >>>> >>>> >>> It was discussed here in context of the "Open with" bug with .aup >>> association that turned out not to be a bug: >>> http://n2.nabble.com/P4-Audacity-executable-in-%22Open-With...%22-td2646747.html#a2646747 >>> >>> >>> >>> >>>>> Otherwise, they cannot, due to >>>>> Windows limitations. Downside is I suppose we need separate >>>>> .iss files for Beta? >>>>> >>>>> >>>>> >>>> Not really. The two iss files have to change for every release anyway, >>>> so we can just change them to use audacity_beta. And change it back for >>>> the stable release. >>>> >>>> Seems like a pretty marginal case for the extra work, though. I doubt a >>>> very big percentage of users have both versions of Audacity installed >>>> and know enough to set up file associations. >>>> >>>> >>> I think of those Windows users who use the Beta, quite a high >>> proportion do install alongside the Stable, not uninstall it. >>> We make a point of mentioning this on the site, and it happens >>> by default if the user doesn't change the Beta installation path. >>> >>> I see this "file association" issue coming up once a twice or month, >>> so not huge but irritating for those savvy enough to try it. Plus >>> there are some people who see "audacity.exe" in the Beta installation >>> folder, and think their Stable installation may have been overwritten >>> because the executable name is the same. I would certainly make this >>> change, and probably just rename the executable we build and note it >>> in win/release.txt. >>> >>> >>> >>> >>>>> * Reading the "rules" on Google Code, it seems we can label old >>>>> download files as "deprecated" so that the "current" view only >>>>> has currently supported files. Anyone wanting unsupported ones >>>>> has to choose the "All downloads" or "Deprecated downloads" >>>>> view. So would we label the 1.3.7 downloads as "deprecated"? >>>>> >>>>> >>>>> >>>>> >>>> Sounds reasonable to me. But I don't think it matters because we'll be >>>> linking directly to the files, right? So most users will never see the >>>> list or a Google Code page at all. >>>> >>>> >>> Yes. I would imagine users would only go there if they clicked >>> the "alternate download" link. But if they do go there, it suggests >>> they are having problems, so limiting the files they have to look >>> at in the current downloads view makes sense to me. >>> >>> * If no other comments, I will leave the Help out of the zip. I'll try >>> and make time to make a link to a zip of the dump on the front >>> page of the Manual, which I think was agreed. >>> >>> * I see we are installing the "Modules" directory. Is there any >>> actual functionality switched on that uses this? >>> >>> >>> >>> >>> Gale >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Enter the BlackBerry Developer Challenge >>> This is your chance to win up to $100,000 in prizes! For a limited time, >>> vendors submitting new applications to BlackBerry App World(TM) will have >>> the opportunity to enter the BlackBerry Developer Challenge. See full prize >>> details at: http://p.sf.net/sfu/Challenge >>> _______________________________________________ >>> audacity-devel mailing list >>> [hidden email] >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>> >>> >>> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
