Re: spelling corrections

[Edward Sanford Sutton, III]

On Monday March 22 2004 08:07, David Bobroff wrote:
> On Sun, 2004-03-21 at 03:51, Edward Sanford Sutton, III wrote:
> > Here are a few more findings; changes found based on 2.1.32 cvs. Let me
> > know if any are not preferred changes or if you have any other feedback.
> > explicitely=explicitly (note: occurs in ./COPYING )
> > mimics=mimicks
>
> I would just point out that 'mimicks' was recently changed to 'mimics'
> (US spelling).  This was a couple of weeks ago.  The person who made the
> change specifically asked if the developers wanted US or UK style.  They
> said US.
>
> -David

  If I remember right, I asked and Han-Wen answered. Am I too tired to 
understand what is being stated here? It was decided to use US over UK if I 
remember right; mimicks=???  mimics=US and UK (I'm too tired to veify with 
non-handy resources right now)...mimicks should now be mimics in the manual 
if the patch went through successfully.
  I decided to look through the docs again since there were previously 
undecided/inappropriately handled issues from before, issues with my patch 
files, and maybe some were just missed. More importantly, I wasn't able to 
correct some later problems I noticed because I didn't know to look into 
the .scm files to safely play and correct other problems I saw. I tried to 
make this recursive in fixing all I could presently find (swept the full 
manual mentioning almost all findings within either the patch or question 
email).
  I also sent out an email with my usual corresponding questions, but I found 
I received a message back that it was processed as email commands. Perhaps 
it'll work better when restated below...
  If the server steps in with processing or holding messages back, should I 
resend in a way that doesn't process it trigger a delay for it (and delete 
the old if possible).
  Well, its back to school weeks for me and I threw away a good portion of the 
evening fixing our front door's lock; I'll resume work on the manual later 
when I have time, and resync to it first, but I'll get on to a patch for the 
replies to the following questions if It isn't patched by the time I get back 
to it.


Is there a preference between:
judgement and judgment
Section 2.11 of the manual (tutorial.itely) has @cindex for both acciaccatura 
and accacciatura. Is this right? Italian word is acciaccatura if I remember 
right
Is anacruse supposed to be anacrusi?
Section 3.11.3 mentions _lyrics_s; should this be changed?
4.6.2 has both 8th note and eighth note; do we have preferred numbering 
conventions yet?
In the viewer/editor section, is Control-Mousebutton stated as is instead of 
Mouse Button for sequence/entry clarity?
Is ghostscript representing the data format specifically, or should it be 
capitalized like Ghostscript
is barcheck or bar check preferred?
Should 'Alist of partial chord exceptions' and similar expressions be changed 
to 'A list'?
Did we decide on (de)crescendo version (de)crescendi before; each is used 
within a couple of lines of each other at one point.
Is barnumber or bar number what we want?
Should staffspace(s) be staff spaces(s)?
Should NoteNames context be NoteName Context
Should uglifyed=uglified (not that either has the nice professional formal 
view)
Should linebreak be line break?
Does bream quating score mean the same as beam quantizing score?
Should centre be center?
Should G.Schirmer be G. Schirmer?
The programmer's reference mentions 'Music expressionsexpressions'; how can 
that be fixed?
Should smallcaps really be small caps?
ascii=ASCII; What file is the license documented at to change it?
Are there any times that backend and frontend should not be hyphenated 
(excluding within scheme)?