Re: WANTED: Design for documentation (Photoshop power users!)

On 02.10.2008 (07:18), Werner LEMBERG wrote: > > Not only is texinfo the worst beast I've ever worked > > with, > > You are exaggerating. The LaTeX kernel stuff is worse IMHO. bibtex also comes to mind. But luckily, I've never had to work in any of those directly. Eyolf -- "Why are we impo

Re: Lyric tie glyph not found (directory separator problem?)

Quoting the manual: "The lyric tie is implemented with the Unicode character U+203F, so be sure to have a font (Like DejaVuLGC) installed that includes this glyph." Note that Pango (the font handling library used in LilyPond) may pick different symbols from different fonts, so even if the rest

Re: Lyric tie glyph not found (directory separator problem?)

Hi Mats, 2008/10/2 Mats Bengtsson <[EMAIL PROTECTED]>: > Have you read the warning about the font you need, in > http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Entering-lyrics#Entering-lyrics Yes, I have seen it. I'm using the standard Century Schoolbook font from LP distribution and b

Re: WANTED: Design for documentation (Photoshop power users!)

> > Mhmm. texinfo.tex is quite complex. Nothing for the > > fainthearted. > > Not only is texinfo the worst beast I've ever worked > with, You are exaggerating. The LaTeX kernel stuff is worse IMHO. > it's badly documented too, at least once one moves past the basics It's getting better. U

Re: png cropping

After much revision, addition, and general fussing about with it, I'm happy to post the official version of what we're calling "lily2image," a script for converting lilypond source files to cropped image files in many different formats suitable for insertion into documents (theses, research pa

Re: WANTED: Design for documentation (Photoshop power users!)

Kurt Kroon wrote: And while I'm thinking about it, you could deal with the line-height issue by setting it to 1.125, without any units. Thanks! I'd read the section on this in the spec, (and just re-read it), and it doesn't point out how much better it is for inheritance, and I didn't get i

Re: WANTED: Design for documentation (Photoshop power users!)

On 2008/10/01 8:30 AM, "Patrick McCarty" <[EMAIL PROTECTED]> wrote: > On Tue, Sep 30, 2008 at 11:53 PM, Kurt Kroon <[EMAIL PROTECTED]> wrote: >> >> -1, but I've got mad enough skillz to make a user style sheet. That way, I >> can make it look however I please. >> >> I have attached my current u

Re: WANTED: Design for documentation (Photoshop power users!)

On Wed, Oct 1, 2008 at 8:53 AM, Patrick Horgan <[EMAIL PROTECTED]> wrote: > Patrick, if you add a line-height: 1.125em; to the .settitle section it > fixes the strange overlap on small windows. The one it inherits from the > body section uses a different em, and although you specify it in ems, it'

Re: WANTED: Design for documentation (Photoshop power users!)

On 01.10.2008 (21:24), Werner LEMBERG wrote: > > > The only possibility to customize the look of the PDF is to modify > > > texinfo.tex. > > > > Ah, I see. Well, there *is* good news for Eyolf: any modifications > > he makes can be added to the official docs instantly. > > Mhmm. texinfo.tex is

Re: Lyric tie glyph not found (directory separator problem?)

Have you read the warning about the font you need, in http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Entering-lyrics#Entering-lyrics /Mats Risto Vääräniemi wrote: Hi, Something strange just happened. I tried to use the lyric tie (~) in one song and LP complained that it couldn't f

Re: questions about horizontal spacing (correct msg)

A good starting point is to read about "scaling durations" http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Scaling-durations#Scaling-durations in the manual. For the first request, you could then use something along the lines of {c c c c | s4. c4*1/4 c c c s4. | c c c c |} which spaces

Re: WANTED: Design for documentation (Photoshop power users!)

> > The only possibility to customize the look of the PDF is to modify > > texinfo.tex. > > Ah, I see. Well, there *is* good news for Eyolf: any modifications > he makes can be added to the official docs instantly. Mhmm. texinfo.tex is quite complex. Nothing for the fainthearted. Werner

Re: WANTED: Design for documentation (Photoshop power users!)

On Wed, 01 Oct 2008 20:06:14 +0200 (CEST) Werner LEMBERG <[EMAIL PROTECTED]> wrote: > > If the built-in customization doesn't do what you want, then your > > only option is to hack texi2pdf directly. That involves C > > programming, > > Not at all. texi2pdf is a simple wrapper for the texi2dvi

questions about horizontal spacing (correct msg)

Hi . (I'm sorry if I send again this message but some errors occurred while sending the previous one) Given these three bars: {c c c c | c c c c | c c c c} with the following output: o    o    o    o    | o    o    o    o    |    o    o    o    o --meas

Re: [solved] Re: todays git segfaults [backtrace]

2008/10/1 Wilbert Berendsen <[EMAIL PROTECTED]>: > Now I rebuilt LilyPond with --disable-optimising and it does not segfault > anymore. I remember having had other issues with the default optimisation on > my GCC 4.1.2 (from Gentoo), that cause strange formatting problems. I've just recompiled fr

horizontal spacing questions

Hi. Given these three bars: {c c c c | c c c c | c c c c} with the following output: o    o    o    o    | o    o    o    o    |    o    o    o    o --measureLength--- 1) I would like to change the notes' spacing inside the second bar in  this way: o    o    o

Re: [solved] Re: todays git segfaults [backtrace]

On Wed, Oct 1, 2008 at 11:07 AM, Wilbert Berendsen <[EMAIL PROTECTED]> wrote: > Op woensdag 1 oktober 2008, schreef Wilbert Berendsen: >> Now I removed the merge-rests function and include, but even then LilyPond >> (git as of today) segfaults (signal 11, with the same backtrace). > > Now I rebuilt

[solved] Re: todays git segfaults [backtrace]

Op woensdag 1 oktober 2008, schreef Wilbert Berendsen: > Now I removed the merge-rests function and include, but even then LilyPond > (git as of today) segfaults (signal 11, with the same backtrace). Now I rebuilt LilyPond with --disable-optimising and it does not segfault anymore. I remember hav

Re: WANTED: Design for documentation (Photoshop power users!)

> Take a look at texinfo's texi2pdf. That's how we build it; the > program converts texinfo to tex (or maybe latex; I can't > remember), and from that to pdf. No, the document gets directly processed by tex. > If the built-in customization doesn't do what you want, then your > only option is to

Re: WANTED: Design for documentation (Photoshop power users!)

> But what about the pdf version? I suggest to ignore it for the time being. It hurts myself, but there are so many things necessary to fix so that it becomes a well looking document. > I guess, sine it's so much raw tex, changing it may be more > troublesome (at least the attempts I made fai

[no subject]

Hi. Given these three bars: {c c c c | c c c c | c c c c} with the following output: 1) I would like to change the spacing of the second bar in ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lil

Re: todays git segfaults [backtrace]

Op woensdag 1 oktober 2008, schreef Patrick McCarty: > Same here, with the latest git.  I removed the function you mentioned > and the included file, and it compiled fine for me. Now I removed the merge-rests function and include, but even then LilyPond (git as of today) segfaults (signal 11, wit

Re: WANTED: Design for documentation (Photoshop power users!)

On Wed, 1 Oct 2008 19:06:53 +0200 Eyolf __strem <[EMAIL PROTECTED]> wrote: > But what about the pdf version? I guess, sine it's so much raw tex, Take a look at texinfo's texi2pdf. That's how we build it; the program converts texinfo to tex (or maybe latex; I can't remember), and from that to pdf

Re: WANTED: Design for documentation (Photoshop power users!)

The recent changes to the html/css are really a significant improvement to the web-based documentation. Kudos to all! But what about the pdf version? I guess, sine it's so much raw tex, changing it may be more troublesome (at least the attempts I made failed), but it would really be good, either

Re: WANTED: Design for documentation (Photoshop power users!)

Am Mittwoch, 1. Oktober 2008 schrieb Kurt Kroon: > I have attached my current user style sheet, to be applied in lieu of > Patrick's styles (in case anyone's interested). I've now added your CSS as another alternative style sheet so that everyone can have a look at it and judge the different styl

Re: WANTED: Design for documentation (Photoshop power users!)

2008/9/30 Reinhold Kainhofer <[EMAIL PROTECTED]>: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Mittwoch, 1. Oktober 2008 schrieb Neil Puttock: >> I don't know whether it's something that's broken at my end (I've been >> getting some weird docs breakages recently), but I've just compiled

Re: WANTED: Design for documentation (Photoshop power users!)

Patrick McCarty wrote: I like your stylesheet, in general. But I think some of the font sizes you are using will render parts of the documentation illegible on certain platforms (such as in the TOC). I like your choice of color especially. I know that most of this is personal, but I looked a

Re: WANTED: Design for documentation (Photoshop power users!)

Patrick, if you add a line-height: 1.125em; to the .settitle section it fixes the strange overlap on small windows.  The one it inherits from the body section uses a different em, and although you specify it in ems, it's inherited in pixels.  Or in CSS speak, you don't inherit the specified val

Re: todays git segfaults [backtrace]

On Wed, Oct 1, 2008 at 8:20 AM, Valentin Villenave <[EMAIL PROTECTED]> wrote: > > This file compiles successfully on Linux64 with a 5-days-old git. > > I removed the rest-merging function, by the way. Same here, with the latest git. I removed the function you mentioned and the included file, and

Re: WANTED: Design for documentation (Photoshop power users!)

On Tue, Sep 30, 2008 at 11:53 PM, Kurt Kroon <[EMAIL PROTECTED]> wrote: > > -1, but I've got mad enough skillz to make a user style sheet. That way, I > can make it look however I please. > > I have attached my current user style sheet, to be applied in lieu of > Patrick's styles (in case anyone's

Re: todays git segfaults [backtrace]

2008/10/1 Jonathan Kulp <[EMAIL PROTECTED]>: > I ran your file with the same results (built Lilypond yesterday from git > source). I'm on Ubuntu Linux 8.04 if that makes a difference. This file compiles successfully on Linux64 with a 5-days-old git. I removed the rest-merging function, by the wa

Lyric tie glyph not found (directory separator problem?)

Hi, Something strange just happened. I tried to use the lyric tie (~) in one song and LP complained that it couldn't find the glyph. These kind on messages usually appeared when the file wasn't saved as UTF but this time the same file works on my work computer (don't tell my boss). The directory

Re: todays git segfaults [backtrace]

Op woensdag 1 oktober 2008, schreef Wilbert Berendsen: > I upgraded from 2.11.58, so the regression might be somewhere in 2.11.59. I investigated somewhat further: The crash in today's git occurs when I use (as in the file I sent): \score { \new ChoirStaff \with { \consists "Instrument_nam

Re: todays git segfaults [backtrace]

Op woensdag 1 oktober 2008, schreef Jonathan Kulp: > I ran the same file on two other machines, and it failed the same way > with 2.11.59 but ran successfully on 2.11.57. I upgraded from 2.11.58, so the regression might be somewhere in 2.11.59. best regards, Wilbert Berendsen -- LilyKDE, LilyPo

Re: todays git segfaults [backtrace]

I ran the same file on two other machines, and it failed the same way with 2.11.59 but ran successfully on 2.11.57. Jon Wilbert Berendsen wrote: Hi, I updated my LilyPond today, it built fine but it segfaults on some file (while working perfect on others). I attach the file and here is the ba

Re: todays git segfaults [backtrace]

I ran your file with the same results (built Lilypond yesterday from git source). I'm on Ubuntu Linux 8.04 if that makes a difference. Jon Wilbert Berendsen wrote: Hi, I updated my LilyPond today, it built fine but it segfaults on some file (while working perfect on others). I attach the file

todays git segfaults [backtrace]

Hi, I updated my LilyPond today, it built fine but it segfaults on some file (while working perfect on others). I attach the file and here is the backtrace. The crash is in the instrument name code. When I comment line 189 in the ly file, to remove the instrument name engraver from the choirsta

Re: scheme music function going backwards in time (or "better mp dolce")

Hi Graham, I have a scheme function for nicely-spaced dynamic+text marks (ie mp dolce), but it adds the dynamic to the note *after* it appears in the score -- to add "f legato" to the E, I need to write c \flegato e d c instead of c e\flegato d c Can anybody see a nice solution to this? Om

Re: could you point me to doc about first time bar, second time bar, dal capo etc?

Hy Daryna, Within the notation manual, could you please give me the link to pages discussing about commands for first time bar, second time bar da capo and da signo a fine?

Re: WANTED: Design for documentation (Photoshop power users!)

On 2008/09/30 3:45 PM, "Reinhold Kainhofer" <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Mittwoch, 1. Oktober 2008 schrieb John Mandereau: >> On 2008/09/30 14:04 -0700, Patrick Horgan wrote: >>> Well done:) I still prefer Patrick's style and wish it were th

could you point me to doc about first time bar, second time bar, dal capo etc?

Hi, Within the notation manual, could you please give me the link to pages discussing about commands for first time bar, second time bar, da capo and da signo a fine? THanks! Daryna ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.o

Re: WANTED: Design for documentation (Photoshop power users!)

On Tue, Sep 30, 2008 at 3:07 PM, Neil Puttock <[EMAIL PROTECTED]> wrote: > > I don't know whether it's something that's broken at my end (I've been > getting some weird docs breakages recently), but I've just compiled > following your latest changes and the navigation's disappeared. Strange... The

Re: scheme music function going backwards in time (or "better mp dolce")

2008/10/1 Graham Percival <[EMAIL PROTECTED]>: > Is this possible now? I'm running into this problem. Yes, me too. But since I use music functions everywhere, I'm getting used to typing commands before the affected music. Cheers, Valentin ___ lilypo