>>>>> "EZ" == Eli Zaretskii <[EMAIL PROTECTED]> writes:
EZ> Do you know any browser that supports <link>?
Lynx and W3, at least. I assume anything that supports the DOM or
similar can do, but I don't know much about that.
EZ> From what I could gather, the more advanced features of <link>
EZ> are not uniformly available.
Indeed, but I'm not very interested in proprietary user agents which
never implemented HTML 2.0 and I wanted to do the job properly and it
clearly does no harm. (The GNU webserver guidelines actually specify
<link rev=made>.) Features of HTML 4.0 are definitely not uniformly
available, but makeinfo now seems to assume HTML 4.0 despite the GNU
guidelines.
EZ> How exactly do you intend to use <link> to solve the problems I
EZ> mentioned?
I don't, though you could in principle use it to provide directory
information relating URLs to node names.
EZ> So it seems like you do want the `emacs_Files.html' method.
Not exactly. I implemented splitting by node name, implicitly into a
per-document directory. That seems to have been dropped, though some
of the support routines are there.
EZ> That doesn't seem like a good idea for some annoying practical
EZ> purposes. For example, what do you do with punctuation (even NT
EZ> doesn't allow `?' and `*' in file names)?
At least in RFC1738 (now superseded?), * isn't a safe character in
URLs, and ? must be encoded if it's not a field separator.
I checked what I did against the Texinfo, Info, G77 and GCC manuals
IIRC. Doubtless it was buggy because I did it in a hurry for a
release it was supposed to catch, but I had something that basically
worked.
Perhaps you should talk to Bill Perry about this stuff. I thought I
was roughly following his line and what rms would want.
