Hi.
>
> Here's a 2.4.6 result.
>
Thanks, but this is related to the character encoding (version 2.4
only supported iso-8859-1) not representing the Hebrew letters.
As of 2.6, this will come out fine. Finally, the problem was not
with lilypond, but with the library it uses to lay out the text:
Gilles -
Here's a 2.4.6 result.
- Bruce
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Gilles
Sent: Thursday, January 12, 2006 4:27 PM
To: bug-lilypond@gnu.org
Subject: Re: Inputting special symbols
[The list moderator rejec
Hi.
> If you want to concatenate two strings, one method is to
> set the word-space property to zero:
> \markup{\override #'(word-space . 0) \line {1\super st } clarinet }
>
Fine! It was the "\line" which I was missing...
Thanks,
Gilles
___
bug-lil
>
> >I wonder whether we talk about the same thing... What do you mean by
> >"render differently"? The postscript output from gedit is fine, while
> >in the postscript output from lilypond, there is a sort of superposition
> >of the string between parentheses onto the other string (so that the
Gilles wrote:
I wonder whether we talk about the same thing... What do you mean by
"render differently"? The postscript output from gedit is fine, while
in the postscript output from lilypond, there is a sort of superposition
of the string between parentheses onto the other string (so that the
> >
> > But you do obtain an illegible subtitle, right? If yes, then there is a
> > problem with the line layout. When you look at the sentence in "gedit",
> > it is displayed correctly, and "gedit" also prints it correctly.
>
> Apparently gedit and lilypond renders the string differently, but s
On Friday 13 January 2006 17.25, Gilles wrote:
> Hello.
>
> > > While in the second case, lilypond seems to be confused by the mixing
> > > of right-to-left (parentheses) and left-to-right (Hebrew) characters,
> > > so that the text line is "scrambled" (see attached "pdf" [1]).
> >
> > I don't know
On Friday 13 January 2006 21.34, Mats Bengtsson wrote:
> If you want to concatenate two strings, one method is to
> set the word-space property to zero:
> \markup{\override #'(word-space . 0) \line {1\super st } clarinet }
>
> Of course, it's more convenient to hack together a \concatenate
> markup
If you want to concatenate two strings, one method is to
set the word-space property to zero:
\markup{\override #'(word-space . 0) \line {1\super st } clarinet }
Of course, it's more convenient to hack together a \concatenate
markup command.
/Mats
Hello.
>
> > While in the second case, lilypond seems to be confused by the mixing
> > of right-to-left (parentheses) and left-to-right (Hebrew) characters,
> > so that the text line is "scrambled" (see attached "pdf" [1]).
>
> I don't know how mixing of right-to-left and left-to-right is normal
On Thursday 12 January 2006 23.27, Gilles wrote:
> [The list moderator rejected a previous post with this message;
> so I had to remove the "pdf" attachment. Hopefully someone will
> be kind enough to try and compile the attached lily file, and tell
> me whether he gets the same result as I.]
>
>
[The list moderator rejected a previous post with this message;
so I had to remove the "pdf" attachment. Hopefully someone will
be kind enough to try and compile the attached lily file, and tell
me whether he gets the same result as I.]
> >
> >Wouldn't it be more logical to do that by default, i
Gilles wrote:
Hi.
because Lilypond inserts a space between any two markup components.
I noticed that too, and I'd tend to consider this as a bug.
no, it's the intended behaviour of markup.
It could be possible to write a markup function that concatenates markup
words,
On Wednesday 11 January 2006 15.39, Gilles wrote:
> Hi.
>
> > > > because Lilypond inserts a space between any two markup components.
> > >
> > > I noticed that too, and I'd tend to consider this as a bug.
> >
> > no, it's the intended behaviour of markup.
> >
> > It could be possible to write a ma
Gilles wrote:
Then, maybe could you explain the rationale behind the intention?
I.e for outputting the opposite of the user's input:
1. Add a space where there was none
If you have a suggestion how to improve this, I will gladly take
patches. The relevant code is in scm/markup.scm.
2.
Hi.
> > > because Lilypond inserts a space between any two markup components.
> >
> > I noticed that too, and I'd tend to consider this as a bug.
>
> no, it's the intended behaviour of markup.
>
> It could be possible to write a markup function that concatenates markup
> words, something like \
On Thursday 05 January 2006 12.25, Gilles wrote:
> Hello.
>
> > The problem I've had with that is that when I define
> >
> > eaigu = ""
> >
> > and then (later) say
> >
> > \markup "sym" \eaigu "trique"
> >
> > what I get in the PDF file is
> >
> > sym é trique
> >
> > because Lilypo
Hello.
>
> The problem I've had with that is that when I define
>
> eaigu = ""
>
> and then (later) say
>
> \markup "sym" \eaigu "trique"
>
> what I get in the PDF file is
>
> sym é trique
>
> because Lilypond inserts a space between any two markup components.
>
I noticed t
18 matches
Mail list logo
