Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-31 Thread Werner LEMBERG
>> Or am I still missing the one place where that explanation is >> provided? > > It's here: > > https://lilypond.org/doc/v2.24/Documentation/usage/other-programs I've added links. https://gitlab.com/lilypond/lilypond/-/merge_requests/1901 Werner

Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-31 Thread Jean Abou Samra
Le jeudi 30 mars 2023 à 23:09 -0600, Jeff Olson a écrit : > Both are properly cropped, as opposed to whole (tall?) pages. The name "-dtall-page" could perhaps be clearer. It means that all normal pages are taken and squashed together vertically. If you also specify -dno-use-paper-size-for-page,

Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-31 Thread Werner LEMBERG
> Going back to the manuals didn't help explain tall-page-formats: > [...] > > Maybe the documentation of separate- and tall-page-formats > should elaborate more. This is very likely. May I invite you to provide improvements to the text? You have first-hand experience :-) Werner

Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-30 Thread Jeff Olson
On 3/30/2023 7:05 PM, Jean Abou Samra wrote: I don't understand the problem you're having. Is my suggestion of using -dtall-page-formats not sufficient for your use case? If you expect a 1-to-1 mapping between SVG files and MIDI files, you can just put each piece into its own \book, with the \bo

Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-30 Thread Jeff Olson
On 3/30/2023 10:11 AM, David Wright wrote:    32 -rwxrwxrwx+ 1 J None   32199 Mar 29 22:25  Foo-1.svg*    32 -rwxrwxrwx+ 1 J None   32190 Mar 29 22:25  Abc-1.svg*    32 -rwxrwxrwx+ 1 J None   32231 Mar 29 22:25  Bar-1.svg* That looks like a linux platform. But it's Windows 10 running the cyg

Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-30 Thread Jean Abou Samra
Le jeudi 30 mars 2023 à 18:31 -0600, Jeff Olson a écrit : > Understood, but, like midi, the first file could (should) still have > been un-suffixed. > And the current mismatch between layout files and midi files is a > good reason for the opposite: > Consider this MWE named MidiMismatch.ly that ge

Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-30 Thread Jeff Olson
On 3/29/2023 11:57 PM, Jean Abou Samra wrote: These "-1" suffices are messing with my URLs for the SVG files, so I'd appreciate any ideas on how to get rid of them.  Thx. They are there for good reason. If any of your |\book|s got output on multiple pages, there would indeed be multiple files

Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-30 Thread David Wright
On Thu 30 Mar 2023 at 07:57:23 (+0200), Jean Abou Samra wrote: > Le mercredi 29 mars 2023 à 22:56 -0600, Jeff Olson a écrit : > > I've got to generate a thousand+ cropped SVG files with specified file > > names > > from one lilypond compilation, so I'm wrapping each score in a \book with > > i

Re: bookOutputName still gets "-1" suffix added to SVG file names

2023-03-29 Thread Jean Abou Samra
Le mercredi 29 mars 2023 à 22:56 -0600, Jeff Olson a écrit : > I've got to generate a thousand+ cropped SVG files with specified file names > from one lilypond compilation, so I'm wrapping each score in a \book with > its own \bookOutputName as in this MWE: > > \version "2.24.1" > #(ly:set-o

bookOutputName still gets "-1" suffix added to SVG file names

2023-03-29 Thread Jeff Olson
I've got to generate a thousand+ cropped SVG files with specified file names from one lilypond compilation, so I'm wrapping each score in a \book with its own \bookOutputName as in this MWE: \version "2.24.1" #(ly:set-option 'backend 'cairo) #(ly:set-option 'separate-page-formats 'svg) #(ly:set-o