Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typos, bad English usage in manual (with fix) #7027

Closed
mixxxbot opened this issue Aug 22, 2022 · 11 comments
Closed

Typos, bad English usage in manual (with fix) #7027

mixxxbot opened this issue Aug 22, 2022 · 11 comments
Labels
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: ulatekh
Date: 2013-05-12T02:44:12Z
Status: Fix Released
Importance: Low
Launchpad Issue: lp1179118
Attachments: mixxx-manual-111.patch, mixxx-manual-111.patch, mixxx-manual-111.patch


I finally had a chance to read the 1.11 manual, and found several minor things to fix, mostly in the way of punctuation and the use of the English language.

Enclosed is a patch, made against the 1.11 release branch.

@mixxxbot mixxxbot added the bug label Aug 22, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: ulatekh
Date: 2013-05-12T02:44:12Z
Attachments: mixxx-manual-111.patch

@mixxxbot
Copy link
Collaborator Author

Commented by: ulatekh
Date: 2013-05-12T02:49:05Z


Oh...duh...the patch got applied earlier.
The patcher didn't tell me he did that.

@mixxxbot
Copy link
Collaborator Author

Commented by: ulatekh
Date: 2013-05-12T03:05:49Z
Attachments: mixxx-manual-111.patch


OK, that's odd...only some of them were applied. The enclosed patch contains the rest of my changes.
e.g. "trough" is still not a substitute for "through", and commas aren't the same as semicolons.

@mixxxbot
Copy link
Collaborator Author

Commented by: esbrandt
Date: 2013-05-12T12:09:32Z


Thanks for proofreading Steven.

In your patch:
- Alternatively use the right-click context menu in the library`s :ref:`track list<library-root>`
+ Alternately, use the right-click context menu in the library`s :ref:`track list<library-root>`

Q: We use "alternatively" in other parts of the manual. As a native English speaker, what is the correct use here ?

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2013-05-12T12:46:58Z


"Alternatively" is correct.

@mixxxbot
Copy link
Collaborator Author

Commented by: kain88-de
Date: 2013-05-12T13:05:21Z


That becomes clear when you look at the german translation

alternatively - ersatzweise/alternativ
alternately - abwechselnd

I would stay with alternatively here as well

On Sun, 12 May 2013 12:09:32 -0000
jus <email address hidden> wrote:

Thanks for proofreading Steven.

In your patch:

  • Alternatively use the right-click context menu in the
    librarys :ref:track list`
  • Alternately, use the right-click context menu in the
    librarys :ref:track list`

Q: We use "alternatively" in other parts of the manual. As a native
English speaker, what is the correct use here ?

** Changed in: mixxx
Milestone: None => 1.11.1

** Changed in: mixxx
Importance: Undecided => Low

** Changed in: mixxx
Status: New => Fix Committed

@mixxxbot
Copy link
Collaborator Author

Commented by: ulatekh
Date: 2013-05-12T14:37:52Z


OK, based on reading some references around the Net, "alternatively" is still considered English, but it seems to be deprecated.
You can keep "alternatively" if you want.

@mixxxbot
Copy link
Collaborator Author

Commented by: borfo
Date: 2013-05-12T15:49:45Z


"Alternatively" is perfectly good and current English, and is appropriate in this instance. "Alternately" would work in this instance as well.

@mixxxbot
Copy link
Collaborator Author

Commented by: esbrandt
Date: 2013-05-13T03:26:44Z


Thanks for the input guys. Rolled back to "alternatively".

@mixxxbot
Copy link
Collaborator Author

Commented by: ulatekh
Date: 2013-05-13T15:38:19Z
Attachments: mixxx-manual-111.patch


Looks like one fix got missed...I changed the term "drag-and-dropping" to "dragging-and-dropping".  That term only appeared once in the manual; otherwise, it uses the 2nd term consistently.

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 1.11.1 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant