Hi Ralf, Den 2010-10-31 10:13 skrev Ralf Wildenhues: >>> This should have a cross reference to just that documentation. >> >> ...if I write: >> >> With contemporary GNU tools, auto-import often saves the day, but see >> the GNU ld documentation and its @code{--enable-auto-import} option >> for some corner cases when it does not >> (@pxref{Options, , --enable-auto-import, ld, The GNU linker}) >> >> that renders as: >> >> With contemporary GNU tools, auto-import often saves the day, but see >> the GNU ld documentation and its `--enable-auto-import' option for some >> corner cases when it does not (*note -enable-auto-import: (ld)Options.) >> >> with my info reader. Why is one dash eaten? Can I stop that from >> happening? Should I care? (i.e. the link works, at least for me) And... > > Have you tried using @option{--enable-auto-import} here? Please check > for all render forms (info, PDF, DVI, HTML) for whether they cope with > this correctly. The point is that '--' means a longer dash; see info > texinfo Conventions.
It seems to work (but I don't know if the link "works" in the PDF version) but both the PDF and DVI versions have what looks like a triple quote: With contemporary GNU tools, auto-import often saves the day, but see the GNU ld documentation and its ‘--enable-auto-import’ option for some corner cases when it does not (see Section “‘--enable-auto-import’” in The GNU linker) But a triple quote is better than one missing dash, agreed? But maybe the section “‘--enable-auto-import’” is a bad reference? I would have liked it to (also) mention the “Options” section. Also, the info rendering is "(*note ... (ld)Options.)" with an included ending period, but not so in the other renderings. How do I handle that? >> ...what's up with the extra "@/" in your version? (just curious) > > It allows an optional line break at this point: > info texinfo --index / Ok, thanks for the info! >> Regarding line breaking, both versions render similar to: >> >> It should be noted that there are various projects that attempt to >> relax these requirements by various low level tricks, but they are not >> discussed here. Examples are FlexDLL >> (http://alain.frisch.fr/flexdll.html) and edll >> (http://edll.sourceforge.net/). >> >> in my 80 column info reader. Which is not optimal IMVHO. :-/ Oh well. > > One way around that is to simply reword the sentence. Surprisingly > often that works quite well without making things sound too stupid. > E.g.: > The interested reader may refer to the @uref{...} and ... projects > for more details. > > Feel free to go ahead as you prefer. Let's not try to outsmart TeX in the line breaking department, that feels like a losing game. Cheers, Peter