Bob> THis brings up another point which I havn't solved.... I use
Bob> within page references to the latest post within a thread
Bob> using the # ...#0002Tp It turns out that # references are
Bob> case insensitive and occasionally messages like 0002Tp get
Bob> confused with 0002tP etc...
Co-incidentally I hit this same issue in a completely different
context today (not involving ACS at all) so I set off to check
out what the situation is supposed to be. The HTML (4.01) spec
is completely clear: both the name and id attributes are
specified as being case sensitive - so any browser which confused
them in the way you indicate above is *broken*. Not that that is
necessarily much comfort, but if does mean that if you invest
effort working around such a problem it could be undermined at
any moment when the browser developer fixes the bug...
Now for what it is worth, my problem was precisely opposite: I
had a page where the internal links *failed* to work precisely
because they had case differences and my browser (Netscape 4.x on
Linux) *correctly* regarded them as distinct. But this strongly
suggests that the author of the page has a browser which behaves
in the opposite way (case insensitive). The obvious suspect
would be Internet Explorer - can anyone check this one way or
the other?
- B.
