On Fri, 2004-11-19 at 07:38, Han-Wen Nienhuys wrote:
> * I suppose that this is still too difficult for "normal" users, and
> that we should also have an option
>
> a. to override fret diagrams for once, eg.
>
> \chordmode { d:add9 \frets "abc9312" }
>
> b. to override a fret diagram
On Wed, 2004-11-24 at 16:27, Matthias Neeracher wrote:
> On Nov 24, 2004, at 1:28 PM, Han-Wen Nienhuys wrote:
>
> >
> > What is the proper fix? Should we be using
> >
> > using std;
> >
> > somewhere?
>
> Yes, I think a declaration
>
> using namespace std;
>
> would solve the issue. C++ pu
Alle 01:32, giovedì 25 novembre 2004, Han-Wen Nienhuys ha scritto:
> [EMAIL PROTECTED] writes:
> > For this reason I went for just a "change" of the names. In fact it is
> > theoretically possible to use the german system with italian names (I
> > suppose this can be done write down german ancient
[EMAIL PROTECTED] writes:
> For this reason I went for just a "change" of the names. In fact it is
> theoretically possible to use the german system with italian names (I suppose
> this can be done write down german ancient music); so I wouldn't mix the
> concept of "chord system" (german/jazz/
Alle 01:17, giovedì 25 novembre 2004, Han-Wen Nienhuys ha scritto:
> [EMAIL PROTECTED] writes:
> > Hello; this is a first try for the support of internationalized chord
> > names for "popular music"; actually this is quite a *vital* feature for
> > italian (and I suppose european) users, so somethi
[EMAIL PROTECTED] writes:
> Hello; this is a first try for the support of internationalized chord names
> for "popular music"; actually this is quite a *vital* feature for italian
> (and I suppose european) users, so something about it MUST be done.
>
> The patch works with current CVS; however
On Nov 24, 2004, at 1:28 PM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
One of the changes in 2.5.1 seems to be that all includes of
got changed to . Unfortunately, on MacOS X, this means that all
references to isinf() are no longer found (presumably cmath wraps this
as std::isinf, although
i was able to workaround that by commenting out (by "@c") the two
ifdocbook and end ifdocbook lines. but i would be interested in the clean
solution, too...
Arno
On Wed, 24 Nov 2004 19:35:15 +0100, Giancarlo Niccolai <[EMAIL PROTECTED]>
wrote:
Hello;
I am trying to compile my first try with
Hello; this is a first try for the support of internationalized chord names
for "popular music"; actually this is quite a *vital* feature for italian
(and I suppose european) users, so something about it MUST be done.
The patch works with current CVS; however it's not very elegant. But as its
d
Alle 19:35, mercoledì 24 novembre 2004, Giancarlo Niccolai ha scritto:
> Hello;
> ./out/macros.texi:89: Unknown command `ifdocbook'.
> ./out/macros.texi:106: Unmatched [EMAIL PROTECTED]'.
> ./out/macros.texi:115: warning: macro `internalsref' previously defined.
> ./out/macros.texi:93: warning: he
May I ask you to apply these patches and backport it to 2.4.x? They
enable mkexpk to find the ec-fonts-mftraced fonts. It is needed for DVI
viewers that need PK fonts. Other distributions may have also to be
patched, but I couldn't find the postinstalls for them.
Patch summary: 'updmap --enable
[EMAIL PROTECTED] writes:
> One of the changes in 2.5.1 seems to be that all includes of
> got changed to . Unfortunately, on MacOS X, this means that all
> references to isinf() are no longer found (presumably cmath wraps this
> as std::isinf, although I haven't tested that.
What is the prope
[EMAIL PROTECTED] writes:
> Hi,
>
> There have been some questions on page breaks between score.
> I seem to recall that Han-Wen sent an answer to a similar question
> a number of months ago, indicating that you should use separate
> \book{...} blocks. However, when when I try to use two \book{...
[EMAIL PROTECTED] writes:
> Hi,
>
> I have added a file convert-ly.txt to the bug cvs, containing comments about
> known limitations/bugs in convert-ly. Perhaps it could be a good idea to be
this should just be part of the documentation. Graham?
--
Han-Wen Nienhuys | [EMAIL PROTECTED]
Hello;
I am trying to compile my first try with lily, but when the make system
reaches the info making point I have got a long sequence of errors:
make[2]: Leaving directory `/home/gian/Progetti/lilypond/stepmake/stepmake'
make[1]: Leaving directory `/home/gian/Progetti/lilypond/stepmake'
make[1
Hello;
I am trying to compile my first try with lily, but when the make system
reaches the info making point I have got a long sequence of errors:
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> "Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes:
Mats> The question is rather what "eats" means. In version 2.4, I think the
Mats> author meant to say that figured bass requests and rest requests are
Mats> taken into account, i.e. "eat"="use", not "eat"="discard".
Mats> M
The question is rather what "eats" means. In version 2.4, I think the
author meant to say that figured bass requests and rest requests are
taken into account, i.e. "eat"="use", not "eat"="discard".
Maybe we have some nutritionist on the list who can help clarify the
situation? ;-)
Seriously, the co
It looks from Mat's and Han-Wen's investigations that it's the documentation of
figured bass that's gone backwards since 1.6, not the actual
implementation.
The 1.6 version of input/test/figured-base.ly said:
1.6> Figured bass is created by the FiguredBass context which eats
1.6> note-re
Hi,
I have added a file convert-ly.txt to the bug cvs, containing comments about
known limitations/bugs in convert-ly. Perhaps it could be a good idea to be
able to access this file in some easier way? E.g., it could be part of the
documentation somehow, or there could at least be a link to web
Thanks, I added this comment to bugs/convert-ly.txt
On Wednesday 24 November 2004 10.51, Mats Bengtsson wrote:
> Now I understand how your file is supposed to work!
> I attach a version modified to version 2.2. To be able to run convert-ly
> on it, I first replaced all occurencies of '{<' to some
Hi,
There have been some questions on page breaks between score.
I seem to recall that Han-Wen sent an answer to a similar question
a number of months ago, indicating that you should use separate
\book{...} blocks. However, when when I try to use two \book{...}
sections in the same file, the result
Now I understand how your file is supposed to work!
I attach a version modified to version 2.2. To be able to run convert-ly
on it, I first replaced all occurencies of '{<' to some dummy like '{#'
and similarly I replaced '>}' with '&}'. After the conversion, I could
then change back from '{ #' to
23 matches
Mail list logo
