Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 767 - Incorrect Use of uncapitalised rms in Contrast and project files.
Incorrect Use of uncapitalised rms in Contrast and project files.
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: User Interface
2.0.7
Per OS All
: P4 Repeatable
Assigned To: Default Assignee for New Bugs
http://audacity.238276.n2.nabble.com/...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-09 11:43 UTC by Gale Andrews
Modified: 2018-08-20 11:51 UTC (History)
5 users (show)

See Also:
Steps To Reproduce:
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00


Attachments
Capitalises RMS in Contrast and project files. (5.15 KB, patch)
2014-10-09 11:43 UTC, Gale Andrews
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gale Andrews 2014-10-09 11:43:19 UTC
Created attachment 513 [details]
Capitalises RMS in Contrast and project files.

It was agreed in cited thread to use RMS (capitalised) consistently where users
can see it. Attached patch makes Contrast GUI and exported text file use RMS.

Also (if wanted) it makes the AUP/AUTOSAVE file write "RMS" instead of "rms". I
tested it with recording and On-Demand Import, but obviously if we do want
that, please check how it's been done.
Comment 1 Richard Ash 2014-10-10 17:21:52 UTC
The UI changes have been committed in SVN rev 13431
There is no way the project file changes are going in, because they will break compatibility, for no user-facing gain.
The issue that started this was consistency in the UI. The project files do not constitute part of the UI, so no need to change them.

== Manual ==
The Contrast tool screenshot will need updating as the text has (minor) changed. May also affect associated page.

== Testing ==
This is a UI string change so does not require specific testing as the affected strings have now been changed.
Comment 2 Gale Andrews 2014-10-11 04:31:34 UTC
Richard wrote:
> There is no way the project file changes are going in, because 
> they will break compatibility
Fair enough, though I'll admit I'm not sure exactly what you mean. AFAICT, any 1.3.x or later release of Audacity will open a project saved by Audacity compiled with those changes, will save over that project, which can then be opened by the patched build and saved over.   

> for no user-facing gain.
There is a small amount of user-facing gain. Most days on the Forum we have to direct a user to open the AUP file or the AUTOSAVE file in a text editor to rescue some problem they are having, or we might post an example AUP to show the AUP structure. If we ever documented the project structure in the Manual, which arguably we should, "rms" would be inconsistent.
Comment 3 Gale Andrews 2014-10-11 05:06:26 UTC
Updated the Manual and removed "manual" keyword. The Manual now has tracking for all code changes, not just bugs at http://manual.audacityteam.org/man/Code_Review_2.0.7 (or whatever the version is) so we may not need this keyword.