On 10-Nov-05, at 5:14 AM, Gilles wrote:
There should be a way for lilypond to accept Unicode escape
sequences.
There is, albeit a bit verbose:
#(ly:export (ly:wide-char->utf-8 #x2014))
Thanks; I was looking for this in the manual but couldn't find it.
Is it there?
I've just added this
Hi.
> > There should be a way for lilypond to accept Unicode escape sequences.
>
>
> There is, albeit a bit verbose:
>
> #(ly:export (ly:wide-char->utf-8 #x2014))
>
Thanks; I was looking for this in the manual but couldn't find it.
Is it there?
Also, do you know why the space after the colo
On 10 Nov 2005 06:47:34 GMT, Raphael Manfredi <[EMAIL PROTECTED]> wrote:
Quoting Gilles <[EMAIL PROTECTED]> from ml.lilypond.users::For Linux: "gucharmap"Yes, but since lilypond does not understand the Unicode escape syntax
(e.g. \u2014 for EM DASH) produced by gucharmap, this is rather useless.The
Quoting Gilles <[EMAIL PROTECTED]> from ml.lilypond.users:
:For Linux: "gucharmap"
Yes, but since lilypond does not understand the Unicode escape syntax
(e.g. \u2014 for EM DASH) produced by gucharmap, this is rather useless.
There should be a way for lilypond to accept Unicode escape sequences.
On Friday 04 November 2005 09:54, Mats Bengtsson wrote:
> >2.) The other problem concerns the width of the braces at the
> >beginning of the piano staff.
> Do you mean that they are too high or are you talking about the
> horizontal width?
They are too high - sorry for being unclear. The ends of th
Windows XP: Start Menu -> Programs -> accessories -> System Tools ->
Character Map.
/Mats
Gilles wrote:
[...] But I know that OSX and windows have built-in software
character map, and I'm certain that many exist for linux and windows.
For Linux: "gucharmap"
Best,
Gilles
__
>
> [...] But I know that OSX and windows have built-in software
> character map, and I'm certain that many exist for linux and windows.
>
For Linux: "gucharmap"
Best,
Gilles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.o
Thomas Ruedas wrote:
Hi,
...
2.) The other problem concerns the width of the braces at the
beginning of the piano staff. While these were just perfect in the
old version, they are too wide in the new one, although I didn't
change anything in the source. How is that possible, and how do I f
On 3-Nov-05, at 8:17 PM, [EMAIL PROTECTED] wrote:
Graham Percival wrote:
Insert the symbol directly into the lilypond file, just like accents
and non-latin characters. See the docs for utf-8.
The docs for utf-8? Are there documents that specify how to enter a
specific symbol in a text fil
Graham Percival wrote:
> Insert the symbol directly into the lilypond file, just like accents
> and non-latin characters. See the docs for utf-8.
The docs for utf-8? Are there documents that specify how to enter a
specific symbol in a text file if I have neither a built-in software
character ma
On 3-Nov-05, at 9:08 AM, Thomas Ruedas wrote:
understand at all what is meant by it - I can only say that I don't
see where I depart from the manual with respect to the beams. This is
the error message:
"Applying conversion: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.12, 2.5.13,
2.5.17, 2.5.18, 2.5.21,
No
Hi,
I am trying to convert some lilypond sources from 2.4.6 to 2.6.3 (as
delivered with SUSE 10.0) and encounter two problems:
1.) convert-ly aborts when invoked as "convert-ly PianoSonataB_2.ly"
on the command line, although this file compiled without problems
under 2.4.6, and 2.6.3 also handle
12 matches
Mail list logo
