Re: Typos in English manual

2010-07-31 Thread Carl Sorensen
On 7/31/10 5:51 PM, "Wols Lists" wrote: > On 31/07/10 22:50, Michael S. Morales wrote: >> On 7/31/2010 10:31 AM, Neil Puttock wrote: >>> >>> I had a vague recollection that this was part of the doc policy, and >>> it's certainly listed here: >>> >>> http://lists.gnu.org/archive/html/lilypon

Re: T1055: Avoid using deprecated %module-public-interface in guile initialisation. (issue1160044)

2010-07-31 Thread Ian Hulin
Hi Patrick, Neil and all, On 29/07/10 20:24, n.putt...@gmail.com wrote: On 2010/07/29 00:55:35, Patrick McCarty wrote: With your patchset, I am getting a compile failure with the regression test `profile-property-access.ly': Same here. How did you guys track it down to this module? I on

Re: Typos in English manual

2010-07-31 Thread Wols Lists
On 31/07/10 22:50, Michael S. Morales wrote: > On 7/31/2010 10:31 AM, Neil Puttock wrote: >> >> I had a vague recollection that this was part of the doc policy, and >> it's certainly listed here: >> >> http://lists.gnu.org/archive/html/lilypond-user/2007-09/msg00486.html >> >> * Do not use abbrevi

Re: Typos in English manual

2010-07-31 Thread Michael S. Morales
On 7/31/2010 10:31 AM, Neil Puttock wrote: I had a vague recollection that this was part of the doc policy, and it's certainly listed here: http://lists.gnu.org/archive/html/lilypond-user/2007-09/msg00486.html * Do not use abbreviations (don't, won't, etc.). If you do, use a comma after it

Re: Typos in English manual

2010-07-31 Thread Neil Puttock
On 31 July 2010 14:15, Werner LEMBERG wrote: > Well, `i.e.' is a shorthand for the Latin `id est' which translates to > `that is', and for the latter, you always need a comma after the `is' > if you continue with a sentence, right?  So I think `i.e.' needs a > comma. I had a vague recollection t

Re: Typos in English manual

2010-07-31 Thread Trevor Daniels
Ralf Wildenhues wrote Saturday, July 31, 2010 4:25 PM * James Lowe wrote on Sat, Jul 31, 2010 at 02:19:41PM CEST: >> - Do you prefer 'e.g.' over 'eg.' and 'i.e.' over 'ie.', and >> what >> about 'with respect to' over 'wrt.' or 'w.r.t.' or 'wrt'? >> FWIW, I >> prefer the first alternative

Re: Optimizations for pure-height approximations. (issue1817045)

2010-07-31 Thread n . puttock
On 2010/07/31 10:59:28, arnonokia6230 wrote: Hm, i am seeing huge memory problems here. What is the trick finally? I don't know; following my initial `make check' run which swallowed all the memory, I haven't had any problems, even with large files. Can you post a test file which still shows

Re: Typos in English manual

2010-07-31 Thread Ralf Wildenhues
* James Lowe wrote on Sat, Jul 31, 2010 at 02:19:41PM CEST: > >> - Do you prefer 'e.g.' over 'eg.' and 'i.e.' over 'ie.', and what > >> about 'with respect to' over 'wrt.' or 'w.r.t.' or 'wrt'? FWIW, I > >> prefer the first alternative in each case, but can adjust as > >> requested. > > > Alway

Re: Typos in English manual

2010-07-31 Thread Werner LEMBERG
> Actually I am not sure that 'i.e.,' is necessary. 'i.e,' is not > correct, so 'i.e.' without a comma is fine as far as I know. Well, `i.e.' is a shorthand for the Latin `id est' which translates to `that is', and for the latter, you always need a comma after the `is' if you continue with a sent

RE: tempo commands not in learning manual

2010-07-31 Thread James Lowe
Hello, Commits fc1946c290e5f253769a306efff1b0224178aaa5 and 9e1b534c81e101c449acfa176f923be57cbcaea5 have added a patch in to the Learning Manual. The NR still needs to be done. Tracker opened http://code.google.com/p/lilypond/issues/detail?id=1197 (thanks Phil) James -Original Message

Typos in English manual

2010-07-31 Thread Ralf Wildenhues
Hello LilyPonders! (or is it ponderers? ;-) I was just introduced to your nice piece of software art, so thanks! I don't like typos, so find attached a patch (against git master) to fix them in the English manual. Tried to omit all controversial bits, but just in case, I'd be happy to redo the

RE: Typos in English manual

2010-07-31 Thread James Lowe
Hello, -Original Message- From: lilypond-devel-bounces+james.lowe=datacore@gnu.org on behalf of Werner LEMBERG Sent: Sat 31/07/2010 12:52 To: ralf.wildenh...@gmx.de Cc: lilypond-devel@gnu.org Subject: Re: Typos in English manual >> >> - Do you prefer 'e.g.' over 'eg.' and 'i.e.' ove

Re: Typos in English manual

2010-07-31 Thread Werner LEMBERG
> > Additionally, we want two spaces after a full stop in the source > > documentation files. > > Ah, well, lemme see what I can do. :-) We have a style guide; say `info lilypond-contributor' (I just see that there isn't a proper menu entry for it in the `dir' file) and go to the `Text formatting

Re: Optimizations for pure-height approximations. (issue1817045)

2010-07-31 Thread arnonokia6230
On 2010/07/23 21:49:50, Neil Puttock wrote: Hi Joe, I haven't been able to replicate the problems I had running `make check', even with the hash table default set to 1000; I guess that means LGTM. :) Cheers, Neil http://codereview.appspot.com/1817045/diff/10001/11001 File lily/axis-gro

Re: Typos in English manual

2010-07-31 Thread Ralf Wildenhues
* Werner LEMBERG wrote on Sat, Jul 31, 2010 at 11:34:25AM CEST: > > > I don't like typos, so find attached a patch (against git master) to > > fix them in the English manual. > Applied, thanks! Hi Werner, and wow, quick feedback! > > If you are interested in more: There are typos in the English

Re: Typos in English manual

2010-07-31 Thread Werner LEMBERG
> I don't like typos, so find attached a patch (against git master) to > fix them in the English manual. Tried to omit all controversial > bits, but just in case, I'd be happy to redo. Applied, thanks! > If you are interested in more: There are typos in the English part > of translated manuals;

Typos in English manual

2010-07-31 Thread Ralf Wildenhues
> I'm not top-posting. Hello LilyPonders! (or is it ponderers? ;-) I was just introduced to your nice piece of software art, so thanks! I don't like typos, so find attached a patch (against git master) to fix them in the English manual. Tried to omit all controversial bits, but just in case, I