Hi,
Did LilyPond use to use the G Clef found on the About page of
www.lilypond.org? If so, is it possible to have it reinstated in future
LilyPond versions under anoter name? I would quite like to use that from
time to time.
Aligorith
Hi Han-Wen,
hm, i am not sure whether i understood correctly what you mean/want,
but for me it looks now very similar to the original ">" sign already
being in that feta...
Hope it helps...
Arno
On Sun, 28 Nov 2004 12:20:44 +0100, Han-Wen Nienhuys <[EMAIL PROTECTED]>
wrote:
[EMAIL PROTECTED]
On Sunday 04 July 2004 17.20, Jan Nieuwenhuizen wrote:
> Pedro Kroger writes:
> > Now it seems to be 'working' (i.e. found the modules), but I got
> >
> > /home/kroger/lilypond/install//share/lilypond/2.3.5/scm/framework-gnome.s
> >cm:129:5: While evaluating arguments to map in expression (map
> >
I wouldn't mind of demanding that users write
\line
explicitly inside \column to go to horizontal mode again, ie.
\markup { \column { a b \bold { c d } e f }
=>
\markup { \column { a b \bold c \bold d e f } }
I think this is more consistent. Of course, \markup should implicitly
enclose
Hi,
On Sun, 28 Nov 2004, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > If not, what is the motivation for continuing to invest time into both
> > TeX and PostScript backends?
>
> Practically: TeX has more formatting capabilities. Personally, I want
> to minimize the amount of time I si
On Sunday 28 November 2004 16:25, Christian Hitz wrote:
> I got lilypond 2.5.2 to compile by doing the following things:
>
> - set _GLIBCPP_USE_C99 before #include in the files that use
> isinf/isnan
> - replace each occurrence of isinf/isnan with std::isinf/std::isnan
>
> I don't know if this bre
[EMAIL PROTECTED] writes:
> Ok, I think I got it. This is not very straightforward.
>
no, that's why we need a guru like you to do it :-)
>
>
> make web runs OK, except in input/regression where it fails on
> ancient-fonts.ly -- I guess this is not related.
ancient-font also fails over here.
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>> There is one thing I have not done yet: adding a rule in convert-ly.
>
> I'm not sure that it will be feasible to add convert-ly rules, since
> you have to deal with correctly nesting { }
I've added a rule that should c
> > IMHO it should be included too. We have plenty of space available...
>
> Hmmm. We should expand the size of a single brace subfont,
> otherwise, we need too many feta-braces-[a-z]-[0-9]*.mf files.
Well, it has to look fine :-)
> Hmm. I tried to google for sfnt, but without avail. Is SFNT ju
[EMAIL PROTECTED] writes:
>
> Some minor clarifications and additions.
>
> > - dynamics, numbers, modern notes, ancient notes should be merged
> > into an OpenType font.
> >
> > [What about the brace font?]
>
> IMHO it should be included too. We have plenty of space available...
Hmmm. We
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>>
>> Ah.. I didn't think this was allowed (or at least not recommended). Using
>> \include at anything else than top level is a kind of substitute for macros,
>> and macros is something we don't want..
>
> I guess that cr
[EMAIL PROTECTED] writes:
>
> Ah.. I didn't think this was allowed (or at least not recommended). Using
> \include at anything else than top level is a kind of substitute for macros,
> and macros is something we don't want..
I guess that creating macros with \include is sufficiently painful to
[EMAIL PROTECTED] writes:
>
> Consider the following situation:
>
> Allegro molto
>staff 1 |... | . |
>
>staff 2 |...
>
> It happens quite often that text strings like `Allegro molto' stick
> out to the right. Can you pr
[EMAIL PROTECTED] writes:
> [...]
> > * good support for non-western lyrics,
> >
> > * usable PostScript output
> >
> > * better support for TeX's text formatting features.
> >
> > * A cleaner system for reading and processing fonts.
>
> Please don't answer the following questions if yo
Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
[...]
> As you might know, the support for languages that use non-ASCII glyphs
> (both european characters with accents and non-european characters) is
> flaky: choices for glyphs are dependent on the -rather limited- TeX EC
> font of the. The problem of
[EMAIL PROTECTED] writes:
> Okay, i hope the second attempt includes your suggestions...
Better, but the anti-blobbing at the junction is still not
perfect. The outside outline should be a straight line ; check what
happens with > if you change its value for diminish to 1.0
--
Han-Wen Nienhuy
Hello list,
I have tried to analyze the "isinf issue", resulting from my "#include
cleanup" patch for LilyPond 2.5, and want to submit the following results,
created with gcc/g++/libc/libstdc++ 3.3.4 on SuSE Linux 9.2.
If you look at the LilyPond C++ sources you find that the issue with "isinf"
[EMAIL PROTECTED] writes:
> Hi,
>
> As a maintainer of the Mutopia site I volunteered to convert old lilypond
> files to later versions (currently I am converting to version 2.2.5 on
> cygwin). Lately I ran into aproblem that you can perhaps help me with.
> Mutopia's TownerDB's 'Trust and Obey' co
Okay, i hope the second attempt includes your suggestions...
On Sun, 28 Nov 2004 00:07:28 +0100, Han-Wen Nienhuys <[EMAIL PROTECTED]>
wrote:
[EMAIL PROTECTED] writes:
> If I understand you correctly, you want to add a new articulation
script
> (rather than patching the code for dynamic marks).
Some minor clarifications and additions.
> - dynamics, numbers, modern notes, ancient notes should be merged
> into an OpenType font.
>
> [What about the brace font?]
IMHO it should be included too. We have plenty of space available...
> - font parameters (staff-space, line thickness,
20 matches
Mail list logo
