[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cross manual references in html manuals

From: Karl Berry
Subject: Re: cross manual references in html manuals
Date: Tue, 27 May 2003 08:52:24 -0400

    characters instead of %. For example %7e%22%23 becomes _7e_22_23 

Sorry, but I'm confused.  Are we talking about what goes inside the href
in <a href="foo">?  If so, then why aren't we doing standard html
escaping with %'s?  Why are you escaping the %'s into _'s?  For XHTML?

    > > Yes, it cannot be valid xhtml. In xhtml, only [A-Za-z0-9-_] are 
    > > acceptable as text for the name= or id= attributes.

Do you have any idea why the xhtml committee created such a horrible
backwards incompatibility?  (They created others as well, I know from
our previous attempts to output xhtml that was compatible with html, but
this is a new one.)  I guess to be XML "compliant".  What a crock.

So in that case, to support xhtml, I guess we have to do what you
suggest, and escape everything with _'s, as in _7e_22_23.  It is ugly
and silly, but the alternatives I see are to not support XHTML (probably
not realistic, long term), or to have different xref rules for HTML and
XHTML (sounds even uglier).

    > It would be "nice" to fully support @ commands in node names.  I just
    > don't think there's any practical way to do it.

    Do you mean in makeinfo or for html manuals cross references ?

Mostly I mean in texinfo.tex.  In makeinfo, I think the difficulties can
be overcome.  And if @-command expansion is supported, than supporting
them in xrefs doesn't pose any particular problem (exactly as in your

In principle, if makeinfo supported it, it could filter out the
@-commands in node names so that TeX wouldn't have to, as can be done
for @macros with texi2dvi -e.

In practice, I feel sure there will be *many* complications.  I don't
intend to work on this any time soon.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]