On Sun, Aug 01, 2010 at 05:34:24AM -0400, James Lowe wrote:
> -Original Message-
> From: lilypond-devel-bounces+james.lowe=datacore@gnu.org on behalf of
> Carl Sorensen
>
>
> Of course, we might want to consider (for the sake of non-native english
> speakers) actually deprecating bot
> Here we go with spacing after end of sentence.
Thanks a lot! Applied to git. It's really great that you have
obviously far too much time for providing such patches :-)
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists
* Werner LEMBERG wrote on Sat, Jul 31, 2010 at 01:52:23PM CEST:
>
> > > 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 is
Carl Sorensen wrote Sunday, August 01, 2010 1:54 AM
On 7/31/10 5:51 PM, "Wols Lists" wrote:
Do you put a comma after "that is"? Either way, it feels right.
I'd be
inclined to say "don't stick a comma after a full stop", and yes
I know
that the dot isn't really a full stop at this point but
Hello,
-Original Message-
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org on behalf of Carl
Sorensen
Of course, we might want to consider (for the sake of non-native english
speakers) actually deprecating both i.e. and e.g., and replacing them with
"that is" and "for exampl
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
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
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
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
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
* 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
> 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
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
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.
> > 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
* 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
> 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;
> 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
18 matches
Mail list logo
