Le mardi 15 décembre 2009 à 00:32 +0100, jema...@gnu.org a écrit :
That would make it difficult to decouple the manuals after they get
installed. Having gnupdf-arch.texi looking into gnupdf-arch-figures/
and gnupdf-hg.texi looking into gnupdf-hg-figures/ makes it possible
to
/, which is a symlink to the subdirectory of
isntalled HTML docs tree which contains the images.
Best
--
John Mandereau
signature.asc
Description: Ceci est une partie de message numériquement signée
Hi Karl,
On 2008/10/28 17:03 -0500, Karl Berry wrote:
Maybe we could make ` and ' active all the time, like and other
characters are now.
I changed texinfo.tex (in CVS and gnulib and
ftp://tug.org/tex/texinfo.tex) to do this, so your backticks should show
up universally now.
Hi Karl,
On 2008/10/22 13:40 -0500, Karl Berry wrote:
Follow @ref{NewFile} for information on the template processing.
And the preceeding `see' was appearing.
Please send your actual input, makeinfo invocation, and resulting output.
I do not get any see with @ref.
There is
On 2008/10/13 06:05 +0200, Werner LEMBERG wrote:
the CVS version of texinfo now supports non-English hyphenation!
As far as I can see in 2.1.62 French, German and Spanish Learning
Manuals, it already partially did before I updated texinfo.tex
yesterday, although I'm not sure how some words are
On 2008/07/10 18:32 -0500, Karl Berry wrote:
John, I know you expressed concern about speed, but I guess I just find
it hard to believe that it would matter that much.
I agree speed is not an important criterion with today's computers, as
text formatting doesn't require so much memory and
On 2008/07/11 02:28 +0200, Patrice Dumas wrote:
If you want to go down this road, I would certainly need lots of help on
the info backend since I don't know the format. If you are interested in
using texi2html as a makeinfo replacement I could certainly commit to
implement the docbook and xml
On 2008/07/11 10:46 +0200, Patrice Dumas wrote:
I think it is worth mentionning the weaknesses of texi2html. I think
that the most problematic one is the home made parser. It is not that
complicated for the 2 first passes. But in the last pass, it gets very
complicated. There is a stack
On 2008/07/08 09:32 +0200, Patrice Dumas wrote:
On Sat, Jul 05, 2008 at 10:35:42AM +0200, John Mandereau wrote:
1) clearly separating parsing from formatting,
2) using GUILE to store parsed Texinfo input, so one can write Scheme
code to play with this input,
3) making HTML output
On 2008/07/07 19:58 -0500, Karl Berry wrote:
On the other hand, my experience with makeinfo is showing me that
without some consideration of backward compatibility as you go along, it
is too hard to just tack on later. You end up with what makeinfo is
now -- a collection of warts. Anyway.
On 2008/07/05 18:50 -0500, Karl Berry wrote:
Indeed. It is not an easy problem, though. Every space in the input is
potentially significant. Macros complicate things enormously. Backward
compatibility has to be 100%. The current code fundamentally intermixes
reading and writing (it was
Karl Berry wrote:
I hoped it would be possible to make texinfo.tex interpret accents as
math accents in math mode
It's hard for me to imagine how to make a pre-accented 8-bit character
into a math accent, though I suppose anything could be done with enough work.
Does it even work that
Oleg Katsitadze wrote:
On Sat, Apr 05, 2008 at 07:14:08PM -0500, Karl Berry wrote:
blablabla @math{\hbox{\it alteracin} 0} blablabla
Does @[EMAIL PROTECTED] 0}} work?
That's the intended usage. (Or maybe some other similar Texinfo cmd.)
@var doesn't work -- it _does_ switch
Hi Texinfo hackers,
Spanish translation of LilyPond manual doesn't compile with current
texinfo.tex, although output looks fine. Here's a small example which
reproduces the bug, with the log I get from texi2pdf. A very similar
error message in the log appears when I replace the UTF-8 character
Karl Berry wrote:
Thanks for the report (again), and sorry for the trouble.
Please try the texinfo.tex in CVS now ...
Thanks, it works!
Best,
John
Hello,
I have tried to compile LilyPond manuals with latest texinfo.tex from
CVS (2008-02-15.11); pdfetex complained with stopping compilation,
saying 'Undefined control sequence'. I tried to cut the Texinfo sources
down to a minimal example reproducing the problem, with two files
=== test.texi
Le samedi 28 juillet 2007 à 18:24 -0500, Karl Berry a écrit :
Hi John,
@documentencoding UTF-8
as
META HTTP-EQUIV=Content-Type CONTENT=text/html; charset=UTF-8
That is what is supposed to happen. And when I run a test document with
@documentencoding UTF-8, that's what I get
Le jeudi 26 juillet 2007 à 20:32 +0300, Oleg Katsitadze a écrit :
On Thu, Jul 26, 2007 at 09:21:04AM +0200, John Mandereau wrote:
A related improvement would be adding a command like
@thinspace to insert a thin unbreakable space.
This should be easy to add. This will make @dmn
Le jeudi 05 juillet 2007 à 12:16 -0500, Karl Berry a écrit :
By the way, do you use makeinfo with the lilypond manual?
Yes, we build the HTML manual in all languages and the Info manual in
English.
If so, could
you see if version in the 4.9.90 pretest (alpha.gnu.org/gnu/texinfo) has
any
Since there are only a few quotes in section titles in LilyPond manual
-- IIRC there is only one title in French with quotes -- support for
non-English quotes in normal text will be an important improvement.
Sorry for the possible top-posting, but my current email client
doesn't allow anything
Thanks for the fix. Unfortunately, I'm not at home and have no
computer access to build LilyPond. I'll be back on July 25th.
If testing this bugfix is urgent, I can ask somebody on lilypond-devel to do it.
We use makeinfo to build HTML and Info manuals, so I'll test 4.9.90.
Cheers,
John
Dear Texinfo hackers,
We LilyPond translators have found a serious layout problem in LilyPond
PDF manual, with Texinfo 4.9. pdfetex/texinfo.tex seems to be sometimes
confused when formatting text with quotes: much space is often left
around the quoted text, leading to overfull hboxes and a
Le mercredi 27 juin 2007 à 19:26 -0500, Karl Berry a écrit :
IMHO quotedblbase is a bit more difficult to remember,
I meant those for the German quotes (on the baseline), since those are
the Adobe glyph list name. I'm not sure if baseline quotes are used in
any other language, but it
2007/6/27, Oleg Katsitadze [EMAIL PROTECTED]:
On Tue, Jun 26, 2007 at 04:12:55PM -0500, Karl Berry wrote:
If it works for John, feel free to commit it and let's give it a try.
Ok. John, can you please try the patch and see if the German manual
(and others, too) compile without errors? If
Le dimanche 24 juin 2007 à 23:15 +0300, Oleg Katsitadze a écrit :
On Sun, Jun 24, 2007 at 01:18:12AM +0200, John Mandereau wrote:
the crash happened with German manual
I'm glad it worked out for the other languages, but I still don't
understand why should German fail, there shouldn't be any
Le dimanche 24 juin 2007 à 13:22 -0500, Karl Berry a écrit :
Additionnally, I have a related feature request: I'd like to be able to
use French and German simple and double quotes in Texinfo TeX output.
I guess we could define new commands. What should the commands be named?
Le samedi 23 juin 2007 à 14:36 +0300, Oleg Katsitadze a écrit :
On Fri, Jun 22, 2007 at 06:11:44PM -0500, Karl Berry wrote:
Oleg, can you see if you can make UTF-8 work in node names per John's
sample document?
I might be missing something, but I understand that the sample
document _does_
Hi Karl,
Karl Berry wrote:
That is strange, as the attached sample.texi contains node
names and section titles with accents,
What's happening is that a UTF-8 e-aigu or whatever is turned into the
regular Texinfo equivalent (@'e) in the aux files. This isn't ideal,
but was a first
Oleg Katsitadze wrote:
This is so strange that I looked again at you first letter and noticed
something. The log you provided contains:
./lilypond.aux:1: Missing @endcsname inserted.
to be read again
@accent
@'#1-[EMAIL PROTECTED]
19 #1}
argument Pr@'e
you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
Greetings
--
John Mandereau [EMAIL PROTECTED]
\input texinfo @c -*-texinfo-*-
@documentlanguage fr
@documentencoding UTF-8
@c
@c
30 matches
Mail list logo
