On 21-Sep-04, at 1:10 PM, Juergen Reuter wrote:
In section 5.3.8 of the manual ("Bar lines"), the last \mark in the
second
figure (lily-1457749936.ly) does not show up: there should be a ":"
printed above the rightmost dotted bar line.
Fixed in CVS, although I uncovered a different bug in doing so
On 21-Sep-04, at 10:38 AM, Juergen Reuter wrote:
Section 7.1.5 ("Changing context default settings") contains twice the
line:
\override Stem #'thickness
Thanks. Since those are in @example sections, it doesn't produce any
lilypond warnings, but they could confuse newbies. :)
Fixed in CVS
On 25-Sep-04, at 11:07 AM, Juergen Reuter wrote:
On a third vein, I just recognized that \once does not appear in the
unified index. It should, I guess (and maybe there should also be a
short
section in the manual that introduces \once).
Thanks. I've added a cindex entry for it, but it only had
> BTW, it is better not to name the file tex/texinfo.cnf but, say,
> Documentation/user/latin1.itexi, and it then is included in all
> texinfo files
Urgh:
BTW, it is better not to name the file tex/texinfo.cnf but, say,
Documentation/user/latin1.itexi, and include this file in all
texinfo
> I think the most practical solution is not to use accented letters
> in the documentation at all.
But this is a lame solution... With my attached stuff latin-1 is
supported quite well.
BTW, it is better not to name the file tex/texinfo.cnf but, say,
Documentation/user/latin1.itexi, and it the
> it's not such a big problem if in texinfo encoding doesn't work
> well.
IMHO it is nice if it works, isn't it? A similar solution to the one
I've sent to bug-lilypond will probably be included in texinfo also.
Werner
___
lilypond-devel mailin
[EMAIL PROTECTED] writes:
> texinfo files are very limited w.r.t. input encodings. Currently,
> latin1 is the best choice -- in reality, even this is not handled
I think the most practical solution is not to use accented letters in
the documentation at all. For the longer term, we need to
* ha
At least, it should work in the examples showing that LilyPond
can handle these characters.
/Mats
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
./lily-2048517126.tex:138: Undefined control sequence
This is temporarily fixed now. I have to add a *lot* of macros to
make it really work -- fo
[EMAIL PROTECTED] writes:
> > ./lily-2048517126.tex:138: Undefined control sequence
>
> This is temporarily fixed now. I have to add a *lot* of macros to
> make it really work -- for texinfo mode, we have to handle T1 font
> encoding by ourselves...
it's not such a big problem if in texinfo
