Comment on revision r13985 in audacity

0 views
Skip to first unread message

auda...@googlecode.com

unread,
Jul 9, 2015, 5:02:50 AM7/9/15
to audaci...@googlegroups.com
Comment by v.audac...@gmail.com:

Score: Negative

General Comment:
I'm totally -1 on degrading to hyphenated usage, as I wrote elsewhere. I
haven't seen it hyphenated among tech-savvy users, for about 25 years.

For more information:
https://code.google.com/p/audacity/source/detail?r=13985

auda...@googlecode.com

unread,
Jul 9, 2015, 11:35:22 AM7/9/15
to audaci...@googlegroups.com
Comment by windinthew:

Score: Neutral

General Comment:
I agree with you. I think if we want "email" which most of us do, we should
also have "plugins" in text on sites, so all the instances of plugins
should be unhyphenated.

However Peter and Steve insisted on this change, against my vote and
despite I said you would disagree with it.

The problem is that we cannot change the name of the "Plug-Ins"
(hyphenated) folder that Audacity uses without creating usability issues.
So if we did not hyphenate plugins in text, Audacity Manual would need text
like "Add your plugins to the Audacity "Plug-Ins" folder". I think doing
that (with "Plug-Ins" quoted) is much less bad than having "email"
and "plug-ins" juxtaposed on a web page, but Peter and Steve won't accept
that.

auda...@googlecode.com

unread,
Jul 14, 2015, 6:46:58 AM7/14/15
to audaci...@googlegroups.com
Comment by v.audac...@gmail.com:

Score: Negative

General Comment:
That's not what I heard from Peter and Steve off-list -- they both agreed
with me that whatever we do going forward, a *news* item (and this on
already been up for more than 3 months), should not be modified
retroactively. If that's allowed, it opens the door for other revisionist
history.

It's inane to have discussed this so extensively. And impolite for you
change my text without asking *me*, when you apparently knew I would
disagree, rather than just acting on what you thought they wanted. What
if I went through all your previous news posts, and modified them to my
preferred wordings/spellings?

=====

Regarding the folder name, I haven't looked at the code recently, but for
YEARS it handled *finding* either "plug-ins" or "plugins", or both, and
regardless of capitalization, because earlier versions wrote it
differently. That's super easy to check for in the code, so if it isn't
doing that any longer, that's an introduced bug, and easily fixed.

auda...@googlecode.com

unread,
Jul 14, 2015, 9:14:40 AM7/14/15
to audaci...@googlegroups.com
Comment by windinthew:

Score: Neutral

General Comment:
If there was a typo discovered subsequently in a news item, we would
correct it. It is consistency, not rewriting history.

The vote was +0.5 for "plug-ins" even allowing for your and my -1. On that
basis Peter directly asked me to make the changes.

Neither of us contributed to the onlist discussion about it (
http://audacity.238276.n2.nabble.com/bug-915-Audacity-creates-a-folder-called-Plug-Ins-td7568997.html
). However Audacity recognising both hyphenated and unhyphenated folders
was discussed as an option there and rejected.

Vaughan Johnson

unread,
Jul 14, 2015, 11:25:25 PM7/14/15
to audaci...@googlegroups.com
This wasn't a typo, it was what I intentionally wrote. 

I don't understand your "Audacity recognising both hyphenated and unhyphenated folders was discussed as an option there and rejected."  The software still actually does that, right?




--
You received this message because you are subscribed to the Google Groups "Audacity-SVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to audacity-svn...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages