> From: Norman Walsh <[EMAIL PROTECTED]>
>
> / Bob Stayton <[EMAIL PROTECTED]> was heard to say:
> | This is why I think it is not yet practical to let
> | <para> or other higher constructs be simple xlinks. The
> | current delivery mechanisms can't express that very well.
> | And if it can't be expressed, I doubt it will be used much.
>
> Yes, that's one of the factors that motivates me as well. We'll have
> enough trouble with nested inlines. (And, btw, my gut reaction is to
> generate broken HTML. The browser ought to handle nested links, gosh
> darn it. Oh, I know I'll get talked out of it, but that's still my gut
> reaction.)
Just for fun I tested nesting <A> elements:
<A href=foo>Starting <A href=bar>a link</A> and ending</A>
Netscape and IE5 actually handle this up to first
closing </A>. "Starting" goes to foo, and "a link"
goes to bar. But the first </A> closes both
and so "and ending" is not hot text at all.
Given that the SGML content model of <A> in DocBook 4.0
explicitly excludes <A>, this isn't too surprising.
bobs
Bob Stayton 400 Encinal Street
Publications Architect Santa Cruz, CA 95060
Technical Publications voice: (831) 427-7796
Caldera International, Inc. fax: (831) 429-1887
email: [EMAIL PROTECTED]
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
