headers
Guido Amoruso | 1 Feb 2003 20:48
Picon
Favicon

fonts and lisense

Hi,

I've been reading some discussion on the Xemo mailing-list
(http://www.xemo.org) about fonts. They are interested in creating
and/or modifying free music fonts, in order to use them in their open
source platform: I don't know details about that, but they'd like to
make it possible to build both proprietary and free applications around
it.

The questions are:

1. which is Lilypond font lisense? I looked for the lisense in the *.mf
files, but did't found it: is it GPL, LGPL or another one?
2. in the last months I've seen interest in music [free] fonts is
increasing: maybe it would be most safe to add some lisensig terms in
Lilypond fonts' sources.
3. do you think it is possible to use GPL fonts in a proprietary
product? I mean, any modification to the fonts should be GPLed, but
perhaps that would not regard the whole application.

Cheers,
Guido
Permalink | Reply | 2 comments |
headers
Han-Wen Nienhuys | 4 Feb 2003 23:35
Picon

fonts and lisense

guidonte <at> libero.it writes:
> Hi,
> 
> I've been reading some discussion on the Xemo mailing-list
> (http://www.xemo.org) about fonts. They are interested in creating
> and/or modifying free music fonts, in order to use them in their open
> source platform: I don't know details about that, but they'd like to
> make it possible to build both proprietary and free applications around
> it.

AFAIK, Xemo is dead. The last "news" on their website dates from
March, 2002.

> 1. which is Lilypond font lisense? I looked for the lisense in the *.mf
> files, but did't found it: is it GPL, LGPL or another one?

Feta is GPL.

> 3. do you think it is possible to use GPL fonts in a proprietary
> product? I mean, any modification to the fonts should be GPLed, but
> perhaps that would not regard the whole application.

Yes, using fonts is allowed, as long as changes to the font are
redistributed in source form.

--

-- 

Han-Wen Nienhuys   |   hanwen <at> cs.uu.nl   |   http://www.cs.uu.nl/~hanwen
Permalink | Reply | 1 comment |
headers
Han-Wen Nienhuys | 4 Feb 2003 23:48
Picon

Braille output strategy


ralph.little <at> tribaldata.co.uk writes:
> My scheme isn't really up to much and the kind of code required to add
> Braille output will be more comfortable in C++ in my view.
> Modifying the grammar is trivial to add a \braille block. Where I take it
> from this is a bit of a mystery...

There are two options:

	* To write a third translator type (we now have Engravers for
	normal typesetting, and Performers), by making a derived class
	from Translator. This new type (let's call it "Embosser"), can
	setup data structures to print braille dots in any way that
	you see fit. A lot of work, advantage: but you will not be
	burdened by any constraints of the printed
	output backend.

	Disadvantage: you have to redo all formatting.  If you go this
	route, it might be easier to make a generic (musicxml)
	outputter in lily, and write a separate application to convert
	from the generic output to dots

	* Write alternative engravers, that produces graphical objects
	printing dots. This allows you to reuse spacing, line breaking
	etc, and makes it easier to test if the dots are printed
	correctly.

	Once all the dots are printed correctly, make a separate
	"printing backend" (next to the PostScript, TeX, and SVG one)
	to drive a braille printer.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Guido Amoruso | 5 Feb 2003 08:24
Picon
Favicon

Re: fonts and lisense

On Tue, 2003-02-04 at 23:35, Han-Wen Nienhuys wrote:

> > I've been reading some discussion on the Xemo mailing-list
> > (http://www.xemo.org) about fonts. They are interested in creating
> > and/or modifying free music fonts, in order to use them in their
open
> > source platform: I don't know details about that, but they'd like to
> > make it possible to build both proprietary and free applications
around
> > it.
> 
> AFAIK, Xemo is dead. The last "news" on their website dates from
> March, 2002

No, they have restarted activies some weeks ago. At present there is
some discussion about fonts: even if this does not reguards Lilypond
directly,
it can be useful to have more free music fonts (as far as different
applications
can use them in different ways).
About the future of Xemo, I hope it will gain some real achievement: I
don't know whether it will, but such effort can give useful results as
well. 

> > 1. which is Lilypond font lisense? I looked for the lisense in the
*.mf
> > files, but did't found it: is it GPL, LGPL or another one?
> 
> Feta is GPL.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Graham Percival | 6 Feb 2003 07:03
Picon
Favicon

Re: markup text

On Wed, 05 Feb 2003 17:46:38 +0000
Alan Lakin <ajlakin <at> blueyonder.co.uk> wrote:
> I have installed the Mandrake Cooker rpm - version 1.7.9
> 
> When entering markup text of more than one word then I find the first
> word is missing and the rest of the words are concatenated together
> into one string. The only way I can get around this is to hyphenate
> the sentence so that the text string is seen as one word.
> 
> I have tried running the examples in the manual with no look. Is this
> a bug in the version I am using?

If an example doesn't work, then I think it's safe to call it a bug (if
only a bug in the example/documentation).  That said, Lilypond 1.7.x is
the unstable branch -- I suggest you either update to the CVS version
and compile from source (if you're that kind of a guy), or get lilypond
1.6.6 (or is it 1.6.7 ?), the latest stable version.

(to the developers)
We've had a few people with problems with the Mandrke Cooker 1.7.9
rpm... I wonder if the Mandrake guys know that the 1.7.x version is
a development version, rather than a stable version.  Do you think it
might be worth asking them if they know about the stable/unstable thing,
and perhaps suggesting that Mandrake should include Lily 1.6.x rather
than 1.7.x?

Cheers,
- Graham
Permalink | Reply | 2 comments |
headers
Heikki Johannes Junes | 6 Feb 2003 11:21
Picon
Picon

Stable releases of LilyPond to Mandrake-cooker!

> We've had a few people with problems with the Mandrke Cooker 1.7.9
> rpm... I wonder if the Mandrake guys know that the 1.7.x version is
> a development version, rather than a stable version.  Do you think it
> might be worth asking them if they know about the stable/unstable thing,
> and perhaps suggesting that Mandrake should include Lily 1.6.x rather
> than 1.7.x?
>
> Cheers,
> - Graham

I compiled once the developement version for fun. And the cooker
applications are not always included to the official distributions.

One should make a sufficient amount of patches from 1.7-branch to
1.6-branch. First, there are patches for spec/lilypond.mandrake.spec.in,
and second, patches to get command "make rpm-mandrake" work.

Then it will be possible to make rpms for 1.6-branch, the similar manner
as there are now rpms for 1.7-branch, see

  http://rpm.nyvalls.se/sound9.0.html.

If somebody could downgrade (from 1.7 to 1.6) these mandrake-patches,
I could try compiling it and send it to Tobbe. People have continued the
development of Rosegarden .. it needs LilyPond.

I have never touched the stable branch, so far. However, at some point
in life people start gradually prefer more stability than dynamity,
i.e., state of developement. That means .. getting older. Maybe it is time
for me also to grow up and matter about stability. But, do I have access
(Continue reading)

Permalink | Reply | 0 comments |
headers
rerdavies | 7 Feb 2003 01:38
Favicon

Re: fonts and lisense

> > 3. do you think it is possible to use GPL fonts in a proprietary
> > product? I mean, any modification to the fonts should be GPLed, but
> > perhaps that would not regard the whole application.
>
> Yes, using fonts is allowed, as long as changes to the font are
> redistributed in source form.
>

Clause 10 of the GPL prevents distribution of GPL products within a larger
product that is not also distributed under GPL.  This prevent your intended
use, unless you can obtain written permission from the authors (yes, all of
them) of the feta font to distribute it with a non-GPL product.

Fonts fall into a peculiar gray area in copyright law. The "programs" (e.g.
the .mf  or a Postcript used to generate a Postscript font) are protected by
copyright laws. However, the output of those programs (the actual shapes)
are not protected by copyright, except in Germany (where both are covered by
copyright). If you can render the fonts to bitmap format, and then convert
those bitmaps to Postcript fonts, then, the result of that process would
*not* be covered by copyright (except in Germany). Strange but true. I used
to make a living, once upon a time, converting scanned typefaces to type-1
fonts for a plain-paper proofing system for high-end industrial typesetters,
so I know whereof I speak.

I believe the conversion from Metafont to postscript has already been done
before using freely available tools, although I don't know what the quality
is like. If you were to do the same thing, you would have a postscript font
that could be used for whatever purpose you like.

Regards,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Heikki Johannes Junes | 7 Feb 2003 03:13
Picon
Picon

lilypond-book in emacs


Has anybody used the command "Book" in Emacs? What is its intended use
in Emacs? Are '.tely'-files sometimes generated from '.ly'? I cannot
figure out situation in which the command "Book" is used.

      Heikki Junes
Permalink | Reply | 0 comments |
headers
Heikki Johannes Junes | 11 Feb 2003 02:43
Picon
Picon

Marking inverse articulations


I found once, that the current notation system is not complete it does
not have some marks which are essential in expressed music.

Suppose the following:

  |         |\   |          |\   |
  |         |    |          |    |
  |         |    |          |    |
 O         O    O          O    O
 cresc.... X contin.cresc. X  continue cresc.

One would need in the place of 'X' an anti-accent or deaccent or
whatever .. Anti-accent happens in the middle of increasing intensity.
I would like to introduce as the following mark, if there is not any mark
already. It is mixture of '<'-accent and a '/'-line over it:

         /
       _//
    __//
 __/  /
<__  /
   \/_
   /  \__
  /      \
 /

It the similar manner one could introduce other inverse articulations.
There is certainly place for more complete set of expressional marks.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Shann | 14 Feb 2003 20:08
Favicon

Figured Bass support

hi,

The example given in the manual for a figured bass seems to be missing a
\notes directive - if I put it inside a \score {} thus

\score {
<
 \context FiguredBass
   \figures {
    <_! 3+ 5- >4
    < [4 6] 8 >
   }
 \context Voice { c4 g8 }
 >
 \paper {
 }
}

then I get an error
warning: Junking request: `Lyric_req': \context Voice { c4 etc...

When I put in the missing \notes directive I get a message
programming error: No StaffSpacing wishes found (Continuing; cross thumbs)

This doesn't always happen depending on the relative lengths of the 
parts I think. Any suggestions for eliminating this would be welcome, 
meanwhile here is a revised example with the \notes and that is more 
realistic
<
 \context Voice \notes { \clef bass dis4  c d ais}
(Continue reading)

Permalink | Reply | 1 comment |

Gmane