there has been an backwards incompatible change within
texinfo.tex (to follow the documentation)
I don't recall for sure, but I think it's far more likely that I
wrote a new item in the documentation to describe the behavior.
No. The documentation snippet you've quoted in a
Patrice, can you check how TP behaves with @funindex \\q?
Currently it leaves \\q. As I can see in the code, if the macro
takes te line as argument, no processing of the line is done at
all. If takes an argument in brace (even if it is only one
argument), the 2 backslashes lead to one,
Hi, Texinfo.
I'm running on a newish, up to date Gentoo Gnu/Linux system. I type:
$ texi2dvi -V --tidy cc-mode.texi
and it fails to produce output or give an error message. The file
/cc-mode.t2d/version_test/txiversion.log ends with:
! Font \circle=lcircle10 not loadable: Metric
Hi Reinhold,
However, it seems that an image needs to be smaller than the actual text
width.
I don't think so. I see a discrepancy only because of PDF/PostScript
points vs. TeX points. Adobe points (big points = bp in TeX) are
72/inch. TeX points are 72.27/inch (= pt in TeX, the
Hi Alan,
! Font \circle=lcircle10 not loadable: Metric (TFM) file not found.
Your distro should provide this font, which has been a standard part of
(La)TeX for a couple of decades. I suggest you complain. (Or you can
install the native TeX Live to avoid leaving yourself at the mercy
Werner and all,
Regarding macros in general. I've been trying, and I have become
skeptical that there is any way to devise a new Texinfo macro command
that does not run afoul of many of the same issues. In particular, TeX
cannot precisely control behavior at newlines, and newline-delimited
