Re: [rfc] Implementation of qXfer

[Eli Zaretskii <eliz at gnu dot org>]

> Date: Wed, 21 Jun 2006 23:32:47 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> Eli, I had to do something mildly surprising with texinfo xrefs: you can
> reference an anchor which contains colons, but you have to use at least a
> two-argument form of @xref.  If you use the one-argument form, the "info"
> browser will choke trying to parse it.  I wanted to keep the anchor named
> after the packet description it was attached to.  Do the docs look OK?

They are OK, except for this issue with anchors whose names contain a
colon: this is against the Texinfo language rules.  You might be lucky
with a particular Info reader, but there are others out there, and
each one of them uses a different method of searching for
cross-reference names (some use fixed strings, others use various
regular expressions).  Using a colon makes them fail in different
situations and in different interesting ways.

So please let's remove the colons and use some other mnemonic methods
to make the xref reflect the packet descriptor.

> [I realize they may be a bit tricky to review; the qXfer docs are large,
> and they replace the qPart docs but sit somewhere else in the alphabetical
> list of packets.

AFAICS, you just moved the text elsewhere and replaced qPart with
qXfer, right?  If there are new portions of text, please tell where
they are.