Writing HTML with URLs containing ampersands

[Ken Case]

> How comes that this works in Netscape? Is it because Netscape knows
> less &...; combinations and so is less likely to hit the problem?

That is precisely the reason.

> As this works in Netscape, it seems a bit strange to me to turn
> off a Netscape compatibility to get it to work like in Netscape...

If you edit OmniWeb.app/entities.dictionary and remove all of the  
entities not recognized by Netscape, you should get precisely Netscape's  
behavior.

If I had realized how big a problem this was going to turn out to be, I  
would have added a switch to disable those entities which Netscape  
doesn't recognize.

				Ken