> Date: Thu, 18 May 2000 18:35:45 +0100
> From: Dave Love <[EMAIL PROTECTED]>
>
> 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
Me neither. I just wasn't sure what attributes of <link> do you want
to use; some of them aren't available on most browsers.
> makeinfo now seems to assume HTML 4.0
Actually, it doesn't. Makeinfo does use a small number of 4.0
features, but only where they were tested not to do any harm on
browsers which don't support HTML 4.0.
> 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.
Then we need to discuss the possible ways of solving the problems I
described. I don't see how makeinfo could support splitting without a
reasonable solution.
> I implemented splitting by node name, implicitly into a
> per-document directory.
How would this solve the problem of finding the right file name to use
in a reference from another document? It will know the directory, but
what about the actual file name where the node being referenced lives?
> Perhaps you should talk to Bill Perry about this stuff.
Sorry, I'm not sure I follow. What did Bill do that is related to
these issues?
