Sorry to ask this basic question.
How I can move a bit on the left the rehearsal mark "A" to make it taking
less vertical space?
\version "2.21.0"
{
\ottava 1 a'''1 1 1 1 \break
\mark A 1 1 1 1^3 \break
}
Thank you, g.
___
lilypond-user mailing
Hi Jan Peter,
I tested the newly merged refactor-override branch a little bit. As far as
I could tell it seems to be working fine and the problem I described in my
original post (where there was an error when a grob-property-path consisted
of a list) is solved.
A minor issue I find is that the
On 5/4/19, 2:51 PM, "mu...@gmx.ch" wrote:
Thanks, I'm perfectly fine with the english documentation. I just have
to tune the language preferences of one of my browsers.
If you'd be willing to help us by translating the german documentation, that
would be a great help!
Thanks,
Carl
Hello again
I'm having problems with ties over the repeat bar lines when adding lyrics.
First let's look at the melody alone - without lyrics:
The tie over the repeat bar line between the two volta spanners is wrong.
When we add the lyrics, somehow unpredictable things happen:
* repeat barlines
Hello everbody
The following example produces 2 compile warnings (cannot end slur,
unterminated slur). I'm missing the slur between dis in bar 3 and d in
bar 4, both in an additional temporary voice context.
It's a snippet from a SATB arrangement with 2 alto voices put in one
staff. In order to
Thanks, I'm perfectly fine with the english documentation. I just have
to tune the language preferences of one of my browsers.
Regards
Stephan
Am 04.05.2019 um 17:14 schrieb David Kastrup:
> "mu...@gmx.ch" writes:
>
>> Thanks for the hint; works as expected.
>>
>> The second part you pasted
Thanks for your response, Andrew. I really hoped that somehow I could create
the snaking columns in my book just using lilypond. It was the very last
thing I needed to create a nice book and to finish my typesetting work.
I know LaTeX, I wrote some things in it. I will check out lyluatex.
--
Hi Jan Peter, I'll update and let you know if I find any problems with the
updated refactor-override branch.
Thank you for all your work in the Edition Engraver!
El vie., 3 may. 2019 a las 3:37, Jan-Peter Voigt ()
escribió:
> Hi Stefano,
>
> a lot of lilypond-unrelated business prevented me
Thanks for your encouragement to use 2.19. Having this answer I'm ready
to go for it :-)
Am 04.05.2019 um 16:30 schrieb Urs Liska:
> Hello Steff,
>
> Am 04.05.19 um 15:48 schrieb mu...@gmx.ch:
>> Hello everybody
>>
>> I'm working with Lilypond for several months now, and my experiments get
>>
"mu...@gmx.ch" writes:
> Thanks for the hint; works as expected.
>
> The second part you pasted from the documentation containing the crucial
> part "a6landscape" is missing in the german version of
> http://lilypond.org/doc/v2.19/Documentation/notation/paper-size-and-automatic-scaling.
> And my
Thanks for the hint; works as expected.
The second part you pasted from the documentation containing the crucial
part "a6landscape" is missing in the german version of
http://lilypond.org/doc/v2.19/Documentation/notation/paper-size-and-automatic-scaling.
And my default browser settings are german
Hello Steff,
Am 04.05.19 um 15:48 schrieb mu...@gmx.ch:
Hello everybody
I'm working with Lilypond for several months now, and my experiments get
more and more realistic and interesting ;-)
Great! Welcome to LilyPond.
So I will follow up with
specific questions soon and hope someone may
"mu...@gmx.ch" writes:
> Hello everybody
>
> I'm working with Lilypond for several months now, and my experiments get
> more and more realistic and interesting ;-) So I will follow up with
> specific questions soon and hope someone may be able to give me advice.
>
> As I'm new to this list, I
On Sat 04 May 2019 at 15:48:04 (+0200), mu...@gmx.ch wrote:
> When I render this code with Lilypond v2.18.2, the PDF appears in
> landscape view as expected - be it in Adobe Reader or in the Frescobaldi
> score view.
>
> When I render this code with Lilypnd v2.19.83, the PDF is rendered in
>
Am 04.05.19 um 16:08 schrieb Thomas Morley:
Am Sa., 4. Mai 2019 um 15:40 Uhr schrieb Urs Liska :
You *did* read this guide=
https://github.com/frescobaldi/frescobaldi/wiki/Run-Frescobaldi-3-on-Linux ?
No.
On
https://github.com/frescobaldi/frescobaldi
I couldn't find anything helpful.
Hello everybody
I'm working with Lilypond for several months now, and my experiments get
more and more realistic and interesting ;-) So I will follow up with
specific questions soon and hope someone may be able to give me advice.
As I'm new to this list, I would like to ask how I should handle
Am Sa., 4. Mai 2019 um 15:40 Uhr schrieb Urs Liska :
> You *did* read this guide=
> https://github.com/frescobaldi/frescobaldi/wiki/Run-Frescobaldi-3-on-Linux ?
No.
On
https://github.com/frescobaldi/frescobaldi
I couldn't find anything helpful.
Now that you provided the link, I _searched_ the
Am Sa., 4. Mai 2019 um 14:50 Uhr schrieb Thomas Morley
:
>
> Hi,
>
> I just tried to get frescobaldi from git work.
> No success.
>
> I've read and reread all the READMEs and INSTALLs, now I'm heavily confused.
> Could someone write (or point me to) a installation-guide for dummies?
> Probably
Am 04.05.19 um 14:50 schrieb Thomas Morley:
Hi,
I just tried to get frescobaldi from git work.
No success.
I've read and reread all the READMEs and INSTALLs, now I'm heavily confused.
Could someone write (or point me to) a installation-guide for dummies?
Probably starting here
Hi,
I just tried to get frescobaldi from git work.
No success.
I've read and reread all the READMEs and INSTALLs, now I'm heavily confused.
Could someone write (or point me to) a installation-guide for dummies?
Probably starting here
https://github.com/frescobaldi
I'm on Ubuntu-18.04 64-bit
Am Sa., 4. Mai 2019 um 11:49 Uhr schrieb Thomas Morley
:
> [*]
> Please attach images, or link to them. My local settings will filter out any
> inline images. And I may not be the only one.
> Looking in the archives is more tedious and probably one reason why this is
> unanswered up to now.
Am Do., 2. Mai 2019 um 23:10 Uhr schrieb Alex Jones <
akjonesjeff...@gmail.com>:
Normally when I make cues I use the << {} \\ {} >> structure such that I
> might have code like the following, but it breaks up the multi measure
> rest, any suggestions?
>
> \version "2.18.2"
>
Hi,
don't give
22 matches
Mail list logo