> So the question: is it possible to use arbitrary (I mean fonts in a
> format that I can buy from fontmakers) fonts in LilyPond scores or
> not.
If you use the PS backend, yes (at least theoretically; I haven't
tested it yet). Currently only with latin-1.
> My other problem is that using 2.3.2
Hi,
I found an evil slur bug (slur collided with beams) today. Apparently my bug
reporting now works by telepathy: While trying to isolate the bug, I did a
cvs update;make, and the bug just disappeared! well done!
erik
___
lilypond-devel mailing lis
On Monday 25 October 2004 00.14, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > The vertical spacing sets distances between Y axis groups,
> > ie. horizontal lines such as Lyrics and Staff contexts. Apparently,
> > this distance must be shortened when the extremes are lyrics or chord
> > n
On Sunday 24 October 2004 12.45, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > On Saturday 23 October 2004 13.31, Han-Wen Nienhuys wrote:
> > > 2.3.23 has bugfixes in the documentation, lilypond-book and
> > > --preview output. This release can be considered as a release
> > > candidate
[EMAIL PROTECTED] writes:
> The vertical spacing sets distances between Y axis groups,
> ie. horizontal lines such as Lyrics and Staff contexts. Apparently,
> this distance must be shortened when the extremes are lyrics or chord
> names.
>
> The workaround is to decrease betweensystemspace
>
> I
I'm trying to approach the problem from my point of view: as a user who
needs latin-2 or unicode encoding with a Garamond font that is shipped
with my Windows system. I'd like to use it in a book created in a DTP
software and the book is to be written with Garamond, and it is needed
to have the
[EMAIL PROTECTED] writes:
> http://www.lilypond.org/doc/v2.3/Documentation/user/out-www/lilypond/
> Dynamics.html
>
> \ppp and \pp are overwritten
> \ff and \fff just look like f.
>
> I could artificially space out this example (adding invisible 16ths),
> but IMO this bug should be fixed b
On 24-Oct-04, at 6:58 AM, Han-Wen Nienhuys wrote:
these recommendations do make for a terse, formal and technical style
of writing. It could be that we should relax these conventions a
little, but maybe you could review the Chapter using these guidelines
again?
I agree that the recommendations make
http://www.lilypond.org/doc/v2.3/Documentation/user/out-www/lilypond/
Dynamics.html
\ppp and \pp are overwritten
\ff and \fff just look like f.
I could artificially space out this example (adding invisible 16ths),
but IMO this bug should be fixed before 2.24.
http://www.lilypond.org/doc/v2
On Sun, 2004-10-24 at 04:49, Han-Wen Nienhuys wrote:
>
> note that the real docs for fret diagrams should also be linked in
> (they are in the Markup section)
>
>
Links to both the real docs in the Markup section and to the markup
properties were included in the notation manual.
Carl
__
> Sorry if I don't understand everything but I think adding support
> for OpenType fonts would be by far better than hacking with all
> those TeX font stuff. Is it practically possible?
This is a completely different issue. We have first to solve the
problem how to access glyphs in an easy way w
> I just realized that there might be an easy answer out of the
> font-encoding troubles. [...]
Hopefully, we'll discuss this `in personam' soon. Whatever we find,
this is something for the 2.5 series. Don't haste.
> * dump all text string using glyphshow. Instead of doing
>
> (hi) show
>
[EMAIL PROTECTED] writes:
> Sorry if I don't understand everything but I think adding support for
> OpenType fonts would be by far better than hacking with all those TeX
> font stuff. Is it practically possible?
I am not aware of any free OpenType font that we could ship with
lily. Do you know a
Sorry if I don't understand everything but I think adding support for
OpenType fonts would be by far better than hacking with all those TeX
font stuff. Is it practically possible?
Bert
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.
[EMAIL PROTECTED] writes:
> Ok, now that the silly gender issues have their own thread, let's
> discuss real issues.
I have some more style issues. The lilypond.tely files lists some
guidelines for writing the docuemntation. I noticed that the new
chapter on templates does not follow these recom
Han-Wen Nienhuys writes:
> I thought that we had agreed that hangs/resource overuse are
> out-of-scope for --safe?
Yes, you're right. Is this documented?
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
hi there,
I just realized that there might be an easy answer out of the
font-encoding troubles. We could use the current setup (setting
encodings with \encoding), and solve the problem on the backend by a
two-step process:
* dump all text string using glyphshow. Instead of doing
(hi) show
we
[EMAIL PROTECTED] writes:
> { c'4 \glissando c'' }
>
> spark:~/tmp gperciva$ lilypond -e "(ly:set-option
> 'internal-type-checking #t)" foo.ly
>
> Now processing `foo.ly'
> Parsing...
> Interpreting music... [1]
> Preprocessing graphical objects...
> Calculating line breaks... [2]
> programming
[EMAIL PROTECTED] writes:
> foo.ly: { c4 }
>
> Lilypond fails to create pdf, but if I create a ps first, (lilypond
> --ps foo.ly), it works. Should lilypond --pdf call lilypond --ps (or
> --dvi) first?
>
> OSX, recent CVS.
fixed.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://w
[EMAIL PROTECTED] writes:
> Han-Wen Nienhuys writes:
>
> >> hangs-quote-grace is still there - it's really critical. Stable programs
> >> shouldn't hang.
> >
> > I'm not gonna fix this before 2.4. The old adage "then don't do
> > that" applies here, sorry.
>
> In that case we must disallow \quot
Han-Wen Nienhuys writes:
>> hangs-quote-grace is still there - it's really critical. Stable programs
>> shouldn't hang.
>
> I'm not gonna fix this before 2.4. The old adage "then don't do
> that" applies here, sorry.
In that case we must disallow \quote in --safe-mode.
Jan.
--
Jan Nieuwenhuiz
[EMAIL PROTECTED] writes:
> Hi,
>
> lilypond --preview doesn't crop the .ps output to a small size. I consider
> this a release-critical bug; it did work in 2.2.
should be fixed in .23
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
[EMAIL PROTECTED] writes:
> Hi,
>
> The vertical distance between staves is much much bigger if chords and lyrics
> are used, even if I reduce all minimumVerticalExtents. Is this a bug or
> intentional? And if it's intentional, why??
The vertical spacing sets distances between Y axis groups,
ie
[EMAIL PROTECTED] writes:
> On Sun, 2004-10-17 at 17:26, Juergen Reuter wrote:
> > Hi!
> >
> > In input/test/fret-diagram.ly, we have a nice fret diagram, but I can not
> > find any section in the manual about it (or did I miss something?). Since
> > the NEWS file advertises fret diagrams for t
[EMAIL PROTECTED] writes:
> On Saturday 23 October 2004 13.31, Han-Wen Nienhuys wrote:
> > 2.3.23 has bugfixes in the documentation, lilypond-book and
> > --preview output. This release can be considered as a release
> > candidate for LilyPond 2.4.
> >
> > Go and grab it at http://lilypond.org/dow
25 matches
Mail list logo
