Hi Han-Wen - neither fmt generation nor any other runtime generation has
ever been parallel-safe. Even if I added locking to mktexfmt (I guess
you are making use of the dynamic fmt creation), something I am not at
all anxious to do, the failed simultaneous runs that would result
doesn't sound like
it already partially
It used English hyphenation patterns in all cases (and still does, if
the real patterns aren't there).
I didn't notice any hyphenation difference after updating texinfo.tex,
but I guess TeXlive 2008 is needed to see improvements
More precisely, what you need (be
chance for @documentencoding utf-8 to be implemented in texinfo
soonish?
Not by me. Sorry. Patches would be more than welcome, of course.
(Doing the fonts in TeX is an especially large piece of the problem,
although even having support in makeinfo alone would be terrific. I
don't think
Node: Staff notation<0x7f>182205
Hmm. I don't see any change for this in the ChangeLog, but when I run the
current cvs makeinfo -o foo.info lilypond.nexi, I get
Node: Staff notation<0x7f>81023
and that is indeed where the Staff notation node starts.
The (wrong) .info files in the archive
install-info: menu item `mup2ly' already exists, for file `lilypond/lilypond'
The patch below will fix the problem for mup2ly and the other lilypond
entries, hopefully.
However, the problem still exists for
* Glossary: (lilypond/music-glossary). Glossary of music terms.
Th
install-info: menu item `mup2ly' already exists, for file `lilypond/lilypond'
Well, the error message is misleading (I'll look into that), but
install-info sorts entries within sections. I think that's why nothing
is happening?
k
P.S. Thanks for reporting the offset bug. I'm going to be
Yes that's maybe the best option, I'll do that. It's just that we
list all program names at top level, and `lilypond' is the name of a
program too...
Right. So, the rule in my mind is not "all programs", it's "all
programs that are not also manual names" :).
As you probably know, th
> * lilypond: (lilypond/lilypond)Invoking LilyPond. Titling LilyPond scores.
How about simply not including that entry, and just have the top-level
entry? After all, there's no point in having it if it goes to the wrong
place.
I removed the "dvips" entry leading to "dvips invocation" fr
> /home/sx0005/lilypond//Documentation/user/out/introduction.texi:95:
> @image file `lily-212977279.txt' (for text) unreadable:
As Alper says, that message is now a warning. The infinite "Too many
errors" is obviously a problem, but I can't reproduce, with CVS texinfo
anyway.
I di
So when do we have the next version of texinfo?
Well, I thought I'd fix a few more bugs. Maybe a few weeks.
Is it really that urgent?
In HTML output, @example ... @end example isn't indented, contrary to
the documentation. Why not? Looks like a bug.
Yes, as you noted, I just in
@quotation
@example
foo
@end example
@end quotation
Why is @example inside @quotation in the first place?
(Although I don't think this causes the problem, it seems wrong, like a
kludge to get examples indented maybe?)
What's the reason for the `'?
It seems that
11 matches
Mail list logo
