John Mandereau wrote:
IMHO it's useful to translate the whole user manual, because:
- it is the part of the documentation where there is most explanation
blurb, and so it is the part of the documentation where translation is
most useful and (technically speaking) doable (unlike the program
refere
Juergen Reuter wrote:
I am not sure about capitalization in English language, but shouldn't
* all words in the headline except "than" start with a capital letter and
Actually, at least in the US, headlines are commonly (though not always)
set in sentence case, with the first letter and any
> > Why do we have -Werror?
>
> Because we are anal retentive.
Hehe :-) Even we from FreeType (who try to fix all warning messages
for all compilers) don't do that.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.
Werner LEMBERG escreveu:
I get this strange warning which consequently leads to an error:
rm -f ./out/parser.dep;
DEPENDENCIES_OUTPUT="./out/parser.dep ./out/parser.o" \
g++ -c -Woverloaded-virtual \
-DHAVE_CONFIG_H -DNDEBUG \
-I./include -I./out -I../flower/include \
This is getting a bit off topic, but...On 11/1/06, Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote:
Actually, in German, as is well known, all nouns get capitalized. Everycountry has its own rules. There is nothing "international" about usingsentence-case for titles...FYI (from Wikipedia):
"The con
On Wed, Nov 01, 2006 at 08:44:13PM +0100, Han-Wen Nienhuys wrote:
> Cameron Horsburgh escreveu:
> >Hmm, I'm still not happy with the first sentence! How about:
> >
> >***
> >
> >The initial inspiration for LilyPond came ten years ago when two
> >musician friends grew disappointed with the bland and
> a draft of the 2.10 release announcement is at
>
>http://lilypond.org/web/announce-v2.10.html
>
> please comment.
Some typographical issues:
. `--' should be replaced with — (since you use it without a
space before and after it).
. The link to the NEWS file looks ugly because it u
I get this strange warning which consequently leads to an error:
rm -f ./out/parser.dep;
DEPENDENCIES_OUTPUT="./out/parser.dep ./out/parser.o" \
g++ -c -Woverloaded-virtual \
-DHAVE_CONFIG_H -DNDEBUG \
-I./include -I./out -I../flower/include \
-I../flower/./out -I
On Wed, 2006-11-01 at 11:37 -0600, Trevor Bača wrote:
>
> The rule still taught in US classrooms for capitalizing titles is that
> the "important" words all get capitals (which comes down to something
> like prepositions and articles being lowercase, with everything else
> in uppercase). This is o
Cameron Horsburgh escreveu:
Hmm, I'm still not happy with the first sentence! How about:
***
The initial inspiration for LilyPond came ten years ago when two
musician friends grew disappointed with the bland and boring look of
computer generated scores.
***
I used formatted iso. generated. G
On Tue, Oct 31, 2006 at 01:31:26AM +0100, Han-Wen Nienhuys wrote:
>
> Hi guys,
>
> a draft of the 2.10 release announcement is at
>
> http://lilypond.org/web/announce-v2.10.html
>
> please comment.
>
> thanks,
>
Hmm, I'm still not happy with the first sentence! How about:
***
The initial
On 10/31/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Jan Nieuwenhuizen escreveu:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
>> The practice is silly today.
>
> I think so too, but it is still what people expect?
only in the US, I think.
And not even all the time even here, FWIW. (See
On Wednesday 01 November 2006 17:23, Han-Wen Nienhuys wrote:
> Erik Sandberg escreveu:
> > However, while I wrote this, I have been thinking about an alternative
> > solution to the same problem, which is cleaner but less efficient: We
> > could let context_def simply be a music expression which is
Cameron Horsburgh escreveu:
a draft of the 2.10 release announcement is at
http://lilypond.org/web/announce-v2.10.html
please comment.
thanks,
A couple of things:
Is there going to be a 2.10.0?
Yes, of course, but 2.10.[123...] will mostly be bugfix releases, and
hardly worth mention
Erik Sandberg escreveu:
However, while I wrote this, I have been thinking about an alternative
solution to the same problem, which is cleaner but less efficient: We could
let context_def simply be a music expression which is inserted before any
music in the context. So e.g., \context Staff { c4
On Monday 16 October 2006 23:41, Erik Sandberg wrote:
>
> I have a clearer plan for context defs now: We could represent each context
> def as a Context object, which is used as a template for new contexts.
> E.g., the Voice context_def in engraver-init.ly defines a Context object
> with various en
Han-Wen Nienhuys wrote:
Mats Bengtsson escreveu:
Hi,
This problem still remains with todays CVS version. Regarding the gcc
version,
the relevant information is of course that my "g++4" is:
gcc version 4.1.0
/Mats
I don't understand, your log shows
/usr/include/c++/3.4.3/bits/basic_str
17 matches
Mail list logo
