Re: alternative for @U{} for older texinfo
() Assaf Gordon () Mon, 5 Jun 2017 18:48:24 + I would like to avoid requiring a new texinfo to build sed Why? Personally, i was very happy to move to Texinfo 6.x, primarily for the performance improvement. -- Thien-Thi Nguyen --- (defun responsep (query) (pcase (context query) (`(technical ,ml) (correctp ml)) ...)) 748E A0E8 1CB8 A748 9BFA --- 6CE4 6703 2224 4C80 7502 signature.asc Description: PGP signature
Re: Feature request - a plain @ref command
() Eli Zaretskii () Sat, 04 Mar 2017 16:29:43 +0200 Cross-references are not only for symbols in the index. True, generally. The suggestion is oriented towards OP's specific use-case, a high-density listing of symbols, all of which appear to be API elements. Here's a more general version (w/ more general name): (defun Info-index-topic-at-point () "Do ‘Info-index’ on the topic at point. If the region is active, use its text as the topic. Otherwise, use the symbol at point as the topic." (interactive) (Info-index (if (region-active-p) ;; TODO: strip leading/trailing whitespace ;; TODO: normalize internal whitespace (buffer-substring-no-properties (region-beginning) (region-end)) (thing-at-point 'symbol Thanks for the inspiration! :-D I've just skimmed the ‘interactive’ form of ‘Info-index’ and suppose another approach (instead of adding a command) is to extend ‘Info-index’ to be region-aware. That would allow an opportunity to further refine TOPIC. Personally, i like the immediacy (w/o further interaction) of grabbing the topic at point. Perhaps ‘Info-index-jump-to-topic’ would be a better name, especially as "j" is still unbound in ‘Info-mode-map’. Anyway, this is probably only marginally on-topic for Texinfo. I'll continue Emacs-side discussion elsewhere. -- Thien-Thi Nguyen --- (defun responsep (query) (pcase (context query) (`(technical ,ml) (correctp ml)) ...)) 748E A0E8 1CB8 A748 9BFA --- 6CE4 6703 2224 4C80 7502 signature.asc Description: PGP signature
Re: Feature request - a plain @ref command
() Ralph Schleicher
() Fri, 03 Mar 2017 20:33:31 +0100
It should rather look like this:
*Class Precedence List*
'cie-rgb-color', 'rgb-color-object', 'color-object', ...
The hidden comma seems to be an Emacs bug, but this is a
different issue.
Another approach is to make sure all THINGs are properly added
to the function or variable index, and forego hyperlinks (which
tend to overwhelm the user experience when used in such density,
IMHO), falling back to simply ‘@code{THING}’; and add to Emacs
something like:
(defun Info-index-symbol-at-point ()
"Do ‘Info-index’ on the symbol at point."
(interactive)
(Info-index (thing-at-point 'symbol)))
(define-key Info-mode-map "j" 'Info-index-symbol-at-point)
These two efforts are independent, of course. Light testing w/
‘Info-index-symbol-at-point’ shows promise (needs error handling
and "symbol" syntax customization, for starters). WDYT?
--
Thien-Thi Nguyen ---
(defun responsep (query)
(pcase (context query)
(`(technical ,ml) (correctp ml))
...)) 748E A0E8 1CB8 A748 9BFA
--- 6CE4 6703 2224 4C80 7502
signature.asc
Description: PGP signature
doc fix: typo in @noindent description
Here's a patch that fixes a typo in the @noindent description:
Index: texinfo.texi
===
--- texinfo.texi (revision 6170)
+++ texinfo.texi (working copy)
@@ -9034,7 +9034,7 @@
line that follows after it.
@end display
-The standard usage of @code{@@indent} is just as above: at the
+The standard usage of @code{@@noindent} is just as above: at the
beginning of what would otherwise be a paragraph, to eliminate the
indentation that normally happens there. It can either be followed by
text or be on a line by itself. There is no reason to use it
Here's a suitable ChangeLog entry for it:
2017-03-03 Thien-Thi Nguyen(tiny change)
* doc/texinfo.texi (@noindent): Spell "@noindent" correctly.
--
Thien-Thi Nguyen ---
(defun responsep (query)
(pcase (context query)
(`(technical ,ml) (correctp ml))
...)) 748E A0E8 1CB8 A748 9BFA
--- 6CE4 6703 2224 4C80 7502
signature.asc
Description: PGP signature
Re: Compressed info files
() Eli Zaretskii () Wed, 11 Mar 2015 19:59:44 +0200 > Back to square one: it should be clearer, somewhere rather > easily reachable, that compressed files are supported :) But that's not user-level information, is it? That's something system administrators and people who package software should be interested in. Well, i think GNU aims to at least not hide this kind of information from the user. It's part of the "make install" flow, which is part of the user experience (should they choose to build Free Documentation from its Texinfo source). IMHO, the best place to put it would be in the GNU Coding Standards: The way to install Info files is to copy them into '$(infodir)' with '$(INSTALL_DATA)' (*note Command Variables::), and then run the 'install-info' program if it is present. (info "(standards) Standard Targets") so that it looks like: The way to install Info files is to copy them---optionally gzipped---into '$(infodir)' with '$(INSTALL_DATA)' [...] This way the prescriptive wording fits w/ the prescription. Since this is The GCS, it follows that conforming Info format readers must be able to handle .info.gz as well as .info files. (Of course, that can be described explicitly, too, but i think adding those two words only is sufficient.) [to reset, cc dropped] -- Thien-Thi Nguyen GPG key: 4C807502 (if you're human and you know it) read my lisp: (responsep (questions 'technical) (not (via 'mailing-list))) => nil signature.asc Description: PGP signature
Re: DTD version confusion
() Karl Berry () Sun, 01 Mar 2015 16:43:15 -0700 Got it. I'll add it to the release list in README-hacking. I see README-hacking has "update DTD and web pages" w/ instructions that use $ver instead of $TEXINFO_DTD_VERSION. Should those instructions be changed, too? -- Thien-Thi Nguyen GPG key: 4C807502 (if you're human and you know it) read my lisp: (responsep (questions 'technical) (not (via 'mailing-list))) => nil signature.asc Description: PGP signature
DTD version confusion
Looks like Texinfo 5.0 shipped w/ texinfo.dtd 5.0 -- that's fine. Even Texinfo 5.1, / DTD 5.0 is acceptable as the DTD did not have any substantial (non-comment) changes. The problem, then, arises for Texinfo 5.2 / DTD 5.0, as DTD 5.2 shows some substantial changes: diff -ubw /home/ttn/build/ixin/dtd/5.1.dtd /home/ttn/build/ixin/dtd/5.2.dtd --- /home/ttn/build/ixin/dtd/5.1.dtd 2015-03-01 13:01:14.0 +0100 +++ /home/ttn/build/ixin/dtd/5.2.dtd 2015-03-01 13:01:45.0 +0100 @@ -1,8 +1,8 @@ - + @@ -1054,6 +1056,34 @@ + + + + + + + + + + + + + + + + + + + + + + TeX"> LaTeX"> @@ -1252,6 +1283,8 @@ +"> + ."> ."> ?"> Diff finished. Sun Mar 1 13:02:42 2015 Here is the relevant excerpt from configure.ac which assigns the variable that holds the eventual DTD version number: # version for the dtd. It is manually set to the next version number # rather than $PACKAGE_VERSION as soon as the DTD is modified. There # are 3 reasons for that: # 1. to avoid using a DTD from internet that wouldn't be in sync; # 2. to avoid unnnecessary changes in XML output file headers, in #test results for instance. Otherwise after a release the #devel version and the pretest versions would be used; # 3. it may be kept as is in case there were no change in the DTD #between releases. This is highly improbable, but who knows. # TEXINFO_DTD_VERSION=$PACKAGE_VERSION TEXINFO_DTD_VERSION=5.0 AC_SUBST([TEXINFO_DTD_VERSION]) Obviously 3. has been proven invalid; there were indeed changes. For 2., probably we can fix the testing infrastructure to paper over that kind of difference. Perhaps we can even reify such fixes by publishing official changes to tp/maintain/catalog.xml and relying on the inherent redirection "technology" (i don't know for sure; i dread digging too deep into all things XML). For 1., well, that's the exact situation we are in now: makeinfo 5.2 produces XML that calls for DTD 5.0. I don't know (yet -- still poking around) if that is acceptable, but it certainly is confusing, especially after noting that DTD 5.2, ignored as it is, is anyway online in its canonical location (www.gnu.org). So, for next release, i think there needs to be first, a more rational (or realistic) policy on how ‘TEXINFO_DTD_VERSION’ is to be updated, and second, that policy should be applied and the change (in policy and deed) noted in NEWS as a bugfix. Personally, i think synching it w/ ‘PACKAGE_VERSION’ is TRT, but i am new to Texinfo hacking so maybe i'm missing something. -- Thien-Thi Nguyen GPG key: 4C807502 (if you're human and you know it) read my lisp: (responsep (questions 'technical) (not (via 'mailing-list))) => nil signature.asc Description: PGP signature
Re: gavin -> new maintainer
() k...@freefriends.org (Karl Berry) () Wed, 17 Dec 2014 22:59:15 GMT Please welcome and support [Gavin Smith]! Welcome! And, a big thanks to Karl Berry. -- Thien-Thi Nguyen GPG key: 4C807502 (if you're human and you know it) read my lisp: (responsep (questions 'technical) (not (via 'mailing-list))) => nil signature.asc Description: PGP signature
Re: texinfo 5.2 dist creates directories that are 777
() Norbert Preining () Sun, 17 Nov 2013 08:44:43 +0900 > So -p is more than just "preserve modification time"?!? At least on my GNU tar ... -p, --preserve-permissions, --same-permissions extract information about file permissions (default for superuser) ;-) > That's a new one on me. One never stops learning. Indeed! Perhaps OP got confused by ‘cp -p’, which has similar but not identical meaning. I use that sometimes for hand-rolled (Automake-less) "make dist" target (prep phase). I was ignorant of ‘tar -p’ until just now. -- Thien-Thi Nguyen GPG key: 4C807502 (if you're human and you know it) read my lisp: (responsep (questions 'technical) (not (via 'mailing-list))) => nil pgpmaR7v7n7qC.pgp Description: PGP signature
Re: texi2pdf (Texinfo 4.13.97) problem: missing footer
() k...@freefriends.org (Karl Berry) () Tue, 20 Aug 2013 18:08:28 GMT Committed a new texinfo.tex that (I hope) fixes this. [...] Thanks. I confirm that w/ texi2pdf from Texinfo 5.2, i now see the right footer in that test case, as expected. -- Thien-Thi Nguyen GPG key: 4C807502 (if you're human and you know it) read my lisp: (responsep (questions 'technical) (not (via 'mailing-list))) => nil pgpuaZlj4tq6h.pgp Description: PGP signature
Re: install-info failure under LANG=it_IT.UTF-8
() k...@freefriends.org (Karl Berry) () Thu, 15 Aug 2013 16:07:14 GMT I changed the string so that the C-_ isn't translated. Unfortunately that will cause some makework for all the other translators who got it right, but it seems more logical, just as we don't want to translate the other "keywords". Thanks. Yes, i agree, the ‘C-_’ is syntax. Better late than never. -- Thien-Thi Nguyen GPG key: 4C807502 (if you're human and you know it) read my lisp: (responsep (questions 'technical) (not (via 'mailing-list))) => nil pgpQexCecAs8O.pgp Description: PGP signature
Re: Warn about invalid node names
() Patrice Dumas () Tue, 13 Aug 2013 11:07:31 +0200 It is always possible to add warnings specific of converters, but I would like to avoid that as much as possible, as I think that it is confusing to have different warning messages for different output formats. I think if you are explicit about the warning CATEGORY, as in: FILENAME:LINE:COL: WARNING (CATEGORY): BLURB it will not be so confusing. Some ideas for CATEGORY are: - texinfo the input language - info - pdf - ... the output format (converter) - format compute one of ‘info’, ‘pdf’, ‘...’ from the args - style migration support, etc Then the warnings facility could accept these symbols, comma-separated, w/ ‘all’ to mean "enable all warnings", and "no-" prefixing to toggle. Personally, i would most likely do: makeinfo -o foo.info --warn=all,no-style foo.texi and invest significant effort to eliminate the reported problems. -- Thien-Thi Nguyen GPG key: 4C807502 (if you're human and you know it) read my lisp: (responsep (questions 'technical) (not (via 'mailing-list))) => nil pgpRMIc97LMuV.pgp Description: PGP signature
install-info failure under LANG=it_IT.UTF-8
Please find attached a tarball that demonstrates the failure of install-info under LANG=it_IT.UTF-8 to write a proper dir file. install-info-bug.tar.gz Description: Binary data It looks like there are three problems: the newly created dir file is missing the 0x1F byte; the foo.info entry is missing; these failures are undetected and install-info exits successfully anyway. This install-info is from GNU Texinfo 5.1. -- Thien-Thi Nguyen GPG key: 4C807502 pgpO2LXJrJRI8.pgp Description: PGP signature
Re: texinfo-5.0.90 pretest available
() k...@freefriends.org (Karl Berry) () Sun, 3 Mar 2013 23:03:54 GMT There's only one previous *implementation* in the usual meaning of the word, but sure, I'll explicitly mention pre-5.0. Well, that's the thing. What is "usual"? I am never surprised by the flexibility of language, and how easy it is to create misunderstandings (even among native speakers of a language). Anyway, thanks. -- Thien-Thi Nguyen GPG key: 4C807502 pgpCU8H8pZcv9.pgp Description: PGP signature
Re: texinfo-5.0.90 pretest available
() k...@freefriends.org (Karl Berry) () Sun, 3 Mar 2013 00:56:29 GMT . The previous makeinfo implementation [...] I would add an explicit version number here, as "previous" depends on the reader's pov. I.e., if this is the first exposure to Texinfo, all implementations, including 5.0, are "previous". -- Thien-Thi Nguyen GPG key: 4C807502 pgpyzGWjitF3C.pgp Description: PGP signature
Re: inter-@deftypefun spacing discrepancy
() k...@freefriends.org (Karl Berry) () Fri, 1 Mar 2013 23:08:21 GMT Perhaps it could be added to NEWS as a "deliberate discrepancy"? Yes, I will. Thanks. I imagine there are many generated documents I doubt it is all that "many", since the manual always more or less implicitly recommended putting in blank lines in the source document where you wanted them, and in practice, from what I've seen, that's what people have done. Yeah, i'm foolishly extrapolating from my own experiences. No worries. -- Thien-Thi Nguyen GPG key: 4C807502 pgpMLZWGkJe9t.pgp Description: PGP signature
Re: inter-@deftypefun spacing discrepancy
() Patrice Dumas () Thu, 28 Feb 2013 18:48:12 +0100 Indeed, makeinfo do not add blank lines anymore anywhere, letting the user do what he prefers with blank lines. Sounds reasonable. Perhaps it could be added to NEWS as a "deliberate discrepancy"? I imagine there are many generated documents (like the one foo.texi was derived from) that rely on the 4.13 automagic bahavior. > If so, is there any way to get makeinfo 5.0 to add back the missing > blank line, like makeinfo 4.13? No, but if you add a line in your document it will give you the same result with both versions. Yes, of course. I was (lazily) hoping for some way to avoid having to modify the document... -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpzDGt8qxqF2.pgp Description: PGP signature
inter-@deftypefun spacing discrepancy
With this input (.texi) file: foo.texi Description: TeXInfo document makeinfo 4.13 produces output with a blank line between all function definitions, whereas makeinfo 5.0 omits the one between ‘f2’ and ‘f3’: foo.info-4.13 Description: Binary data foo.info-5.0 Description: Binary data Is this change of behavior intentional? If so, is there any way to get makeinfo 5.0 to add back the missing blank line, like makeinfo 4.13? -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpboP8PKDumN.pgp Description: PGP signature
Re: texinfo sources now in svn
() k...@freefriends.org (Karl Berry) () Thu, 21 Feb 2013 22:39:42 GMT now developing texinfo in subversion rather than cvs Thank you! I had delayed looking at the new generated-by-Perl IXIN stuff because of CVS antipathy. Now theres no more excuse. :-D -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpbLOix7Kn2K.pgp Description: PGP signature
Re: 4.13.96: incorrect error message
Perhaps the bug is w/ Perl itself? I found <https://rt.perl.org/rt3//Public/Bug/Display.html?id=80190>, which includes a small test program. On my computer it outputs: $ ./zow.pl 1..8 ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 not ok 7 # Failed test at ./zow.pl line 15. # got: '4' # expected: '2' ok 8 # Looks like you failed 1 test of 8. and exits failurefully. What does that program do on your computer? -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpOmlNxjjDdT.pgp Description: PGP signature
Re: 4.13.96: incorrect error message
() Patrice Dumas () Tue, 12 Feb 2013 01:01:40 +0100 I cannot reproduce that. Using fr_FR.UTF-8 I get something correct. I attach the result. > which looks funny and is incorrect -- i don't know what the "proper" Looks like something doubly encoded. Hmm, maybe my locales are misconfigured. Which ones do you have enabled on your computer? Here is what i see: $ sed '/^#/d' /etc/locale.gen fr_FR.UTF-8 UTF-8 it_IT.UTF-8 UTF-8 I just added ‘fr_FR.UTF-8’ and it also shows "doubly encoded" output: BAD-fr_FR.UTF-8 Description: Binary data > [...] env var ‘PATH’ I don't really get that part... I installed Texinfo 4.13.96 under "non-standard" prefix and thought that might be part of the problem (perhaps Perl cannot find a certain module that it expects to be in a "standard" location, and becomes confused). Is there any way to trace the encoding steps used for the error message? I suppose next step is to install under /usr/local and see what happens. -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpLjkJksxLcc.pgp Description: PGP signature
4.13.96: incorrect error message
With an input file ixin.texi that has the (incorrect) line 545: @fonttextsize 42 and env var ‘LANG’ having the value ‘it_IT.UTF-8’, the command: $ /tmp/a/b/c/bin/makeinfo -o ixin.xml --xml --no-split ixin.texi > BAD-$LANG 2>&1 produces the file BAD-it_IT.UTF-8, attached here: BAD-it_IT.UTF-8 Description: Binary data which looks funny and is incorrect -- i don't know what the "proper" quotes (around 42) should be, but certainly the first part of the message should read something like: Solo @fonttextsize "10" o "11" è supportata ^ (The indicated word/character is U+E8, LATIN SMALL LETTER E WITH GRAVE.) In contrast, the output when env var ‘LANG’ has value ‘C’ is: BAD-C Description: Binary data NB: I also tried both of the above commands w/ dir /tmp/a/b/c/bin appearing in env var ‘PATH’. It doesn't change anything. Is this a bug? -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpXY0ypysKvb.pgp Description: PGP signature
small correction
Please find attached here a small patch:
*** texinfo.txi~ 2013-01-01 20:31:56.0 +0100
--- texinfo.txi 2013-01-02 10:33:26.0 +0100
***
*** 10262,10268
* syncodeindex::How to merge two indices, using @code{@@code}
font for the merged-from index.
* synindex::How to merge two indices, using the
! default font of the merged-to index.
@end menu
--- 10262,10268
* syncodeindex::How to merge two indices, using @code{@@code}
font for the merged-from index.
* synindex::How to merge two indices, using the
! roman font for the merged-from index.
@end menu
that corrects a confusing menu entry description. Perhaps it used to be
correct but is no longer? Anyway, here is a suitable ChangeLog entry:
2013-01-02 Thien-Thi Nguyen(tiny change)
* doc/texinfo.txi (Combining Indices):
Fix typo: Say "roman font for merged-from".
--
Thien-Thi Nguyen . GPG key: 4C807502
. NB: ttn at glug dot org is not me .
. (and has not been since 2007 or so) .
.ACCEPT NO SUBSTITUTES .
... please send technical questions to mailing lists ...
pgpxIB_KNqDhk.pgp
Description: PGP signature
Re: XML/Info discrepancy for @deffn CATEGORY
() Patrice Dumas
() Mon, 31 Dec 2012 18:58:28 +0100
> I tried to put curly braces in the
> macro definition, but that produces an error:
>
> ./guile-api.texi:567: Misplaced { (possibly involving @PROC)
> ./guile-api.texi:567: Misplaced }
That's weird. I don't see such an error with
@macro PROC
{Scheme Procedure}
@end macro
@deffn @PROC{} global-init servertype
@end deffn
Sorry, i was in a hurry and mixed up the test cases. That particular
error occurs with makeinfo 4.13, not 4.13.92.
> Lastly, i searched NEWS for something that fits this new behavior,
> but did not find anything. Am i missing something?
[...] fact that @PROC{} is considered as a token is considered to be
inconsistent for the @macro implementation, hence this is not kept in
texi2any. It is possible that it is more consistent with what TeX
does, though.
Thanks for the explanation. OK, so i surmise:
A. Braces in macro definition (as above) is OK for upcoming makeinfo,
both Info and XML.
B. Braces at call site is OK for all (4.13 and upcoming) makeinfo,
both Info and XML.
If i care about makeinfo 4.13, i should do B. until which time i don't
care anymore, and can switch to A. But anyway, the current source (no
braces anywhere) needs to be changed; the problem is on my side.
--
Thien-Thi Nguyen . GPG key: 4C807502
. NB: ttn at glug dot org is not me .
. (and has not been since 2007 or so) .
.ACCEPT NO SUBSTITUTES .
... please send technical questions to mailing lists ...
pgppNZcpRq82B.pgp
Description: PGP signature
XML/Info discrepancy for @deffn CATEGORY
I just noticed in the latest IXIN 1.5 tarball file d/serveez.xml,
generated by makeinfo 4.13.92, that the input line:
@macro PROC
Scheme Procedure
@end macro
@deffn @PROC{} global-init servertype
shows up as:
Procedure
Scheme
Procedure
global-init
servertype
That is, the category is "Procedure" instead of "Scheme Procedure", and
everything else is shifted by one. I tried to put curly braces in the
macro definition, but that produces an error:
./guile-api.texi:567: Misplaced { (possibly involving @PROC)
./guile-api.texi:567: Misplaced }
The weird thing is that Info output is fine (including indexing).
Another data point: Curly braces at the "call site":
@deffn {@PROC{}} global-init servertype
work fine for both Info and XML output. Also, w/ or w/o curly braces at
the call site work fine for both Info and XML output for makeinfo 4.13
(in IXIN 1.4 d/serveez.xml, for example).
Lastly, i searched NEWS for something that fits this new behavior, but
did not find anything. Am i missing something?
--
Thien-Thi Nguyen . GPG key: 4C807502
. NB: ttn at glug dot org is not me .
. (and has not been since 2007 or so) .
.ACCEPT NO SUBSTITUTES .
... please send technical questions to mailing lists ...
pgpAlMeRS_qJI.pgp
Description: PGP signature
4.13.92 catalog out of sync w/ generated doctype
In 4.13.92 dist, texinfo.cat says: PUBLIC "-//GNU//DTD TexinfoML V4.13.92//EN" "texinfo.dtd" but the XML produced by "makeinfo --xml" says: "-//GNU//DTD TexinfoML V5.00//EN" Is this discrepency a bug? -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpVbxNraMCLb.pgp Description: PGP signature
[PATCH] Doc fix: Index '@xrefautomaticsectiontitle'.
Preparing for next IXIN release, i found this necessary for research. From 3ae1ee92aed280bffec6dd6e93cf3c2a40462dda Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 11 Dec 2012 10:28:53 +0100 Subject: [PATCH] Doc fix: Index '@xrefautomaticsectiontitle'. * doc/texinfo.txi (Three Arguments): Add @findex xrefautomaticsectiontitle. --- ChangeLog |5 + doc/texinfo.txi |1 + 2 files changed, 6 insertions(+), 0 deletions(-) diff --git a/ChangeLog b/ChangeLog index 0d9a718..c766f9c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2012-12-11 Thien-Thi Nguyen(tiny change) + + * doc/texinfo.txi (Three Arguments): + Add @findex xrefautomaticsectiontitle. + 2012-11-26 Karl Berry * configure.ac: invoke gl_REGEX, after diff --git a/doc/texinfo.txi b/doc/texinfo.txi index 0032490..4fe47b7 100644 --- a/doc/texinfo.txi +++ b/doc/texinfo.txi @@ -6300,6 +6300,7 @@ just the first argument if the node name and the section title are the same (or nearly so), and with the first and third arguments only if the node name and title are different. +@findex xrefautomaticsectiontitle If you want the section title to be used by default instead of node names in cross references (an explicitly specified third argument still takes precedence), Texinfo can do this automatically: -- 1.7.2.5 This patch is against the 4.13.91 tarball. -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpEenGF0Buw1.pgp Description: PGP signature
Re: texinfo-4.13.91 pretest available
() k...@freefriends.org (Karl Berry) () Tue, 27 Nov 2012 01:13:31 GMT ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz I generated XML (in doc/ after "make all check" => OK) w/ GNUmakefile: include Makefile xml: $(MAKEINFO) --xml --no-split -o texinfo.xml texinfo.txi and invocation "make xml" and see that the DOCTYPE line refers to 4.12: http://www.gnu.org/software/texinfo/dtd/4.12/texinfo.dtd";> ... Is that a bug? -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgp9bTnVuPHxu.pgp Description: PGP signature
Re: a fix in HTML output
() Patrice Dumas () Sun, 5 Aug 2012 16:39:41 +0200 You can now have float names in references by setting FLOAT_NAME_IN_XREF, for instance, with --set FLOAT_NAME_IN_XREF=1 Any comment on the customization variable name? I prefer names with hyphen (-) instead of underscore (_), and understand that C/Perl doesn't support hyphens in names. For command-line parsing, however, IWBN if ‘--set float-name-in-xref=1’ could be used in place of (or maybe in addition to) the above example. Is this already supported? -- Thien-Thi Nguyen . GPG key: 4C807502 . NB: ttn at glug dot org is not me . . (and has not been since 2007 or so) . .ACCEPT NO SUBSTITUTES . ... please send technical questions to mailing lists ... pgpxDXkqG3ERL.pgp Description: PGP signature
Re: Texinfo macros and m4
() k...@freefriends.org (Karl Berry) () Sat, 3 Sep 2011 22:44:22 GMT I really want an external solution, for all the reasons that have been discussed. I am not attached to m4 specifically, but I don't see any better candidate. Introducing ability to call out to m4 (or whatever) also introduces the desire to customize the call out: when (and how often), with what scope (environment, restrictions), other parameters, etc. This is messy. Maybe better would be to drop @macro entirely. This forces the external solution, but people can make do with the tools most comfortable to them. There is no real requirement for makeinfo to own the top-level.
[PATCH] doc/texinfo.txi (leq geq): Remove spurious sentence frag.
Here is a suitable ChangeLog entry:
2010-03-15 Thien-Thi Nguyen(tiny change)
* doc/texinfo.txi (leq geq): Remove spurious sentence frag.
*** texinfo.txi.~1.241.~2009-03-27 22:24:59.0 +0100
--- texinfo.txi 2010-03-15 04:00:22.0 +0100
***
*** 11080,11086
Use the @code{@@g...@{@}} and @code{@@g...@{@}} commands to generate
greater-than-or-equal and less-than-equal-signs, `...@geq{}' and
`...@leq{}'. In plain text and Info output, these are the ASCII
! sequences @samp{>=} and @samp{<=}. The
@node math
--- 11080,11086
Use the @code{@@g...@{@}} and @code{@@g...@{@}} commands to generate
greater-than-or-equal and less-than-equal-signs, `...@geq{}' and
`...@leq{}'. In plain text and Info output, these are the ASCII
! sequences @samp{>=} and @samp{<=}.
@node math
[patch] util/defs.in
2007-10-04 Thien-Thi Nguyen <[EMAIL PROTECTED]> (tiny change)
* util/defs.in (TEXI2DVI_run): Use $TEXI2DVI.
we go to the trouble of computing the name of the program under test,
so might as well use that value to actually test it (instead of, say,
/home/ttn/local/bin/texi2dvi or something else on PATH).
applying this patch allows "make check" to finish successfully for
texinfo-4.11, w/ texinfo-4.8 previously installed (prefix /home/ttn/local).
thi
--- defs.in 18 Sep 2007 00:49:25 - 1.12
+++ defs.in 4 Oct 2007 13:25:02 -
@@ -198,8 +198,7 @@
set x --debug --verbose ${1+"$@"}
shift
fi
- type texi2dvi
- texi2dvi ${1+"$@"} 2>stderr >stdout || exitcode=$?
+ $TEXI2DVI ${1+"$@"} 2>stderr >stdout || exitcode=$?
cat stderr
cat stdout
test $exitcode = $expected_exitcode || exit 1
Re: makeinfo --xml output not well-formed
() Oleg Katsitadze <[EMAIL PROTECTED]> () Sat, 14 Jul 2007 12:40:17 +0300 it's fine as it is now, if only README.dev is clearer on the possibly necessary gnulib update. i agree. a little more clarity in README.dev would help me, too. thi
Re: makeinfo --xml output not well-formed
() [EMAIL PROTECTED] (Karl Berry) () Wed, 13 Jun 2007 13:56:41 -0500 I made the following patch to makeinfo, which apparently fixed the detailmenu problem in the case you reported and the others I could find. If you run across more, please let me know. i just now did a cvs update and tried to rebuild (starting w/ autogen.sh). unfortunately, now i see this error message: ./configure: line 6123: syntax error near unexpected token `sys/time.h' ./configure: line 6123: ` gl_CHECK_NEXT_HEADERS(sys/time.h)' so i was not able to confirm that the fix worked. am i missing something? thi
makeinfo --xml output not well-formed
greetings, please find attached three (one input and two output) files. they were processed like so: common="--xml e2.texi" makeinfo -o e2a.xml $common /home/ttn/build/GNU/texinfo/makeinfo/makeinfo -o e2.xml $common the first makeinfo says: "makeinfo (GNU texinfo) 4.8" and the second: "makeinfo (GNU texinfo) 4.8.90" version 4.8.90 was built from a cvs checkout today, a few hours ago. using emacs from cvs, file lisp/xml.el (cvs 1.56 dated 2007-03-17), the commands: (xml-parse-file "e2a.xml") (xml-parse-file "e2.xml") both result in an error: XML: (Not Well-Formed) Invalid end tag (expecting detailmenu) inspection of the xml files does indeed reveal (even to my untrained eye) what appears to be improper nesting of the `detailmenu' element. thi e2.texi Description: input e2a.xml Description: output from makeinfo 4.8 e2.xml Description: output from makeinfo 4.8.90
