Document add-on suggestion for 13.1.1 Command line options

[Frédéric Chiasson]

Hi,

I'd like to change a little the page 13.1.1-Command Line Options to make the
syntax clearer for newbies. I didn't understand myself the syntax of these, I
had to give some time to test different options and to leave some messages to
the users' group because of that.

>From the line beginning with -f, --format=format, I'd put :

-f[format], --format=[format]
  which formats should be written. Choices for [format] are svg, ps,
pdf, png, tex, dvi.

  Ex.: lilypond -fpng filename.ly
 lilypond --format=png filename.ly


-b[format], --backend= [format]
  the output format to use for the back-end. Choices for [format] are

  (... the choices for format)

  Ex.: lilypond -bsvg filename.ly
 lilypond --backend=svg filename.ly



I don't know the syntax for the other functions enough to change the help texts
for them, but it would surely help to use this kind-of standard for those. It
would be clearer (and reduce a little the messages sent to the users' group
about this topic!)

Tell me if it helps,

Frédéric




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Backporting doc changes to stable/2.10 [was: Re: Docs check-translation]

[Han-Wen Nienhuys]

Graham Percival escreveu:
> Jean-Charles wrote:
>> All the documents that I have read about typography and "good use"
>> show examples introduced with a colon (:) throughout their content. 
>> So I think it is normal French typography to do like this.
> 
> To be honest, I'm not certain where the no-colon rule came from.  I just
> checked a few technical books lying around (I'm in a lab) and they
> sometimes used colons.
> 
> Not that I consider blogs to be authoritative, but this article makes
> sense to me:
> http://www.megginson.com/blogs/quoderat/2005/12/23/mind-your-colons/

FWIW, I learned the 'avoid colons' rule both from an editor at GNU press
and the famous mathematician Paul Halmos. 

Rules may be different in other languages, of course.

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Backporting doc changes to stable/2.10 [was: Re: Docs check-translation]

[Graham Percival]

Jean-Charles wrote:
All the documents that I have read about typography and "good use" show 
examples introduced with a colon (:) throughout their content.  So I 
think it is normal French typography to do like this.


To be honest, I'm not certain where the no-colon rule came from.  I just 
checked a few technical books lying around (I'm in a lab) and they 
sometimes used colons.


Not that I consider blogs to be authoritative, but this article makes 
sense to me:

http://www.megginson.com/blogs/quoderat/2005/12/23/mind-your-colons/

(err, no pun intended by using a colon there.  :)


I propose that we use the guidelines in the link -- use a colon to 
introduce material if the sentence is a complete sentence.


Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: skyline vertical spacing

[Joe Neeman]

On 1/6/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:


Joe Neeman escreveu:
>
> Hi,
>
> I have added scripts for profiling, see buildscripts/build-
profile.sh.
>
> It turns out that the skyline related routines have replaced
> Grob::get_property() as the top-contender in the profile.  Can you
> have a look to see if this can be  optimized?
>
>
> I'll take a look. How important is the optimisation? (I was thinking of
> trying to turn 2-pass spacing into 1-pass spacing -- which should I do
> first?)

I don't know, take a look at the profile and see if you can come up with
some
simple shortcuts. I already did a few. (Couldn't sleep last night).

A few simple optimizations put Page_spacer::calc_subproblem at the top.



Some further optimisations give
 time   seconds   secondscalls  ms/call  ms/call  name
 7.48  0.62 0.62   564933 0.00 0.00
Page_spacer::calc_subproblem(unsigned int, unsigned int)
 3.38  0.90 0.28  1103679 0.00 0.00
Building::conceals_beginning(Building const&) const
 3.02  1.15 0.25  1467008 0.00 0.00  Building::precompute()
 2.90  1.39 0.2473951 0.00 0.01
Skyline::internal_merge_skyline(std::list

*, std::list >*, std::list
std::allocator >*)
 2.83  1.63 0.24  8807932 0.00 0.00
Grob::internal_get_property_data(scm_unused_struct*) const
 2.77  1.86 0.23  2063603 0.00 0.00
Building::conceals(Building const&) const
 2.53  2.07 0.21  1739992 0.00 0.00  Grob::extent(Grob*,
Axis) const
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Styles [Was Re: Barline scans]

[Graham Percival]

Karl Hammar wrote:

[moving this from bug-lilypond]

[EMAIL PROTECTED]:

Karl Hammar wrote:

Maybe we should have a "my style" section in the doc.

Like section 4.3 Style sheets ?


There you tell us how to do it. But perhaps more like the snippet
respository, examples of different styles. Right now we "only" have
one style, the default one. Plus "tweaks", where the tweaks are more
something you do when lilypond don't cope with it, not a different 
style.


I have no objection to this; see
http://lilypond.org/web/devel/participating/documentation-adding

Cheers,
- Graham


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Styles [Was Re: Barline scans]

[Karl Hammar]

[moving this from bug-lilypond]

[EMAIL PROTECTED]:
> Karl Hammar wrote:
> > Maybe we should have a "my style" section in the doc.
> 
> Like section 4.3 Style sheets ?

There you tell us how to do it. But perhaps more like the snippet
respository, examples of different styles. Right now we "only" have
one style, the default one. Plus "tweaks", where the tweaks are more
something you do when lilypond don't cope with it, not a different 
style.

Regards,
/Karl




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: test coverage

[Joe Neeman]

On 1/2/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:



Hi,

I've been running coverage tests of the input/regression/ suite, to
see which parts of the code are not excercised.  This has already
turned up some bugs.

You can get a full overview by running buildscripts/build-coverage.sh,
but here are some interesting offenders


cov % ( lines): file
--
5.04 (   238): vaticana-ligature-engraver.cc
52.49 (   341): lookup.cc
0.00 (   132): page-turn-page-breaking.cc
3.10 (   129): vaticana-ligature.cc
7.27 (   110): gregorian-ligature-engraver.cc
61.33 (   225): page-spacing.cc
64.14 (   145): page-turn-engraver.cc



Joe - can you look into writing a couple of tests for the
page-breaking stuff?



I have all the page-breaking files with coverage around 90% now, but I'll
try to improve it a bit more (btw, the reason page-turn-page-breaking.cc was
so low is that I forgot to put a \book around the regression tests so the
lilypond-book output skipped the page-breaking stuff. Oops).
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Backporting doc changes to stable/2.10 [was: Re: Docs check-translation]

[Jean-Charles]

Le 08.01.2007 01:45, John Mandereau disait :
Graham Percival wrote: 
Thanks, these look good.  However, there are some problems with your 
other updates:


1.  Wrapping paragraphs in texinfo is pointless, because texinfo ignores 
whitespace.  Lines that are too long are annoying for people using 
80-character terminals, but other than that, there's no point in 
spending time fussing over linewidths.


Well, I haven't spent much time on this: with Emacs, it's only a matter
of doing M-Q on odd-looking paragraphs.  Moreover, it's easier to read
short and well formatted lines, for both Info readers and docs editors.

2.  Don't use colons: to introduce examples.  See the README.txt in 
Documentation/user/


You are right.  I wonder if the same rules should apply to French
translations; in French, I feel well introducing many examples with a
colon.  I should check good French style somewhere; Jean-Charles, what
do you know about this?




All the documents that I have read about typography and "good use" show 
examples introduced with a colon (:) throughout their content.  So I 
think it is normal French typography to do like this.


May I advice all translators to have a look at it.  I made some research 
last year as we were starting the French version of lilypond.org, and 
found some good books or URL, one of them dealing with localization of 
the Sun products (regularly updated).




Jean-Charles



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: makeinfo with utf-8 support

[Karl Hammar]

> [EMAIL PROTECTED]:
> > Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit :
> > > Hmm, when building I get:
> > > 
> > >  out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'.
> ...
> > > Does anybody know where the makeinfo with utf-8 support is, a patch ?
> > 
> > AFAIK Texinfo does no character encoding conversion for the Info and
> > HTML output, so the LilyPond devels have decided to use the modern
> > character set UTF-8, not Latin1. This will really become a problem for
> > the PDF (outputted by Texinfo/TeX) when we decide to make PDF of Lily
> > docs translation.
> > 
> > Well, you can safely ignore these warnings.
> > 
> > See also 
> > http://lists.gnu.org/archive/html/lilypond-devel/2007-01/msg00047.html
> 
> Tried cvs version [1] of texinfo/makeinfo
> 
>   $ makeinfo --version
>   makeinfo (GNU texinfo) 4.8.90
> 
> But the warning persist. Well, never mind.
> 
> Regards
> /Karl
> 
> [1] http://savannah.gnu.org/cvs/?group=texinfo

This is fixed in latest texinfo cvs:

Karl Berry:
> I just added UTF-8 to the list of encoding names recognized by makeinfo
> (from CVS).  It just passes through the bytes as they are received,
> which hopefully will be better than nothing.  I can't undertake to
> actually parse UTF-8 at this point (I added it to the TODO file :).
>
> Thanks,
> Karl

Regards
/Karl




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

assertion failure in mozart-hrn-3

[Joe Neeman]

With latest git, make web fails on mozart-hrn-3.ly:

$ ./out/bin/lilypond input/mutopia/W.A.Mozart/mozart-hrn-3.ly
GNU LilyPond 2.11.10
Processing `input/mutopia/W.A.Mozart/mozart-hrn-3.ly'
Parsing...
Interpreting music... [8][16][24][32][40][48][56][64][72][80][88][96]
warning: cannot find start of (de)crescendo[104][112][120][124]
Preprocessing graphical objects...
Interpreting music...
Interpreting music... lilypond: audio-item.cc:97: virtual void
Audio_span_dynamic::render(): Assertion `dynamics_.back ()->volume_ < 0'
failed.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Updated spanish translation

[Daniel Tonda Castillo]

Three things:

First: I attach the patch for the latest updated spanish translation in 
bzipped format.



Second: There's a typo in site/about/automated-engraving/input-format.html .

Where it says:

The above is another expression, and therefore, it many combined
again with a simultaneous expression (in this case, a half note).

Probably should read:

The above is another expression, and therefore, it may be combined
again with a simultaneous expression (in this case, a half note).

Third and last but not least:

After reading: site/sponsor/options.html, I am very much impressed and 
wish for both Han-Wen and Jan, the greatest of successes in their 
endeavours in Google and Atos, and even if it's a short period of time 
involved in LilyPond from now on, I'm sure it will still be great.


I too am returning to teaching (back from holidays) and school, so my 
involvement will be less, but I'm still participating in translations 
and lists.


Have a good day!



0006-Update-spanish-translation.txt.bz2
Description: application/bzip
begin:vcard
fn:Daniel Tonda Castillo
n:Tonda Castillo;Daniel
email;internet:[EMAIL PROTECTED]
version:2.1
end:vcard

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: adding installation for windows in German

[Han-Wen Nienhuys]

Mats Bengtsson escreveu:
> 
> 
> Han-Wen Nienhuys wrote:
>>
>> see btw,
>>   lilypond.org/~hanwen/annotated-demo.pdf
>>
>> maybe this should get a place somewhere on the website?   
> Nice!

I've added it to the website (including SVG source), but would
appreciate it someone would do the work of making an HTML page of it
and/or integrating it into an existing page.

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: adding installation for windows in German

[Mats Bengtsson]

Han-Wen Nienhuys wrote:


see btw, 


  lilypond.org/~hanwen/annotated-demo.pdf

maybe this should get a place somewhere on the website? 
  

Nice!

  /Mats


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: segfault on input/regression/lyric-extender-no-heads.ly

[Han-Wen Nienhuys]

Joe Neeman escreveu:
> This is with latest git:
> 
> $ ./out/bin/lilypond input/regression/lyric-extender-no-heads.ly
> 
> GNU LilyPond 2.11.10
> Processing `input/regression/lyric- extender-no-heads.ly
> '
> Parsing...
> Interpreting music... [1]
> Preprocessing graphical objects...Segmentation fault (core dumped)
> 

Sorry about this. I should probably push more often to the hwn and not to
master.
 

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: `:' vs `.' in doc files

[Werner LEMBERG]

> > you've changed a lot of `.' at the end of paragraphs into `:' if
> > the text is followed by an example.  I think this is wrong.  IIRC,
> > it is better style in English to close with a full stop.
>
> Sorry, I don't know good English style, I'd better changed nothing.

Similar to you I'm no expert in English style, but I remember that
I've done the same as you (this is, replacing full stops with colons)
and others told me that it's better to not do this.


Werner


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel