href="http://books.google.com/books?id=tIQ4CqmJ9e0C& ;pg=PA75&lpg=PA75&dq=sql+%22multiple+inherit ance%22&source=bl&ots=IFRtMaansm&sig =7YbSvCHDUjsAX_InmLki1wmwVrs&hl=de&ei=_QnWSt iiGs7-_Aaiq4jZAg&sa=X&oi=book_result& ;ct=result&resnum=10&ved=0CDIQ6AEwCQ#v=onepa ge&q=sql%20%22multiple20inheritance%22&f=fal se "
As you can see they contain many "&" 's (to get past the XHTML validator). However, when Ctrl-clicking the links from the web editor, the google books page isn't shown, just some fallback page to the book in general.
This seems to happen because the "&"s aren't decoded. I can see the "&"s in my URL line in the browser (Firefox 3). When clicking the link inside a browser, the link is OK, because it gets decoded.
I do not think the problem is with the & separators in your URI, but instead with the # found in the value for parameter ved. In particular, # is used as a delimiter for fragment identifiers as stated in the URI RFC [1]. If needed, you can work around this by changing # to %23.
I think our hyperlink detector might be able to do a better job at making sure that it's not trying to send you to a location based on a URI fragment. So please feel free to open a bug.
Hmmm I don't think the # is the problem: when you replace all
&
with
&
in Eclipse and Ctrl-click the link, it works perfectly.
Eclipse just doesn't seem do decode the "&" to just "&" before passing it to the external browser. (I also tested the internal browser, they are equal.)
Dave Carver wrote:
> I believe this is a bug, it should be decoding those URL's so they are
> valid. Please open a bug if it's a duplicate somebody will mark it as
> such.
I've always encoded & as "&" in our New and Noteworthy pages
where the link represents a Bugzilla query. Looking at the
in-browser source for http://www.eclipse.org/webtools/releases/3.1.0/newandnotewor thy/index.php,
the & are encoded there and the link works fine. And I routinely
test those queries by activating the link directly within the XML
Editor, where it also works fine.
--
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational
Nitin, I don't think you'll see this problem in the XML editor because I think it's the Anchor hyperlink detector causing the problem since it specifically looks for references with # in them to try and locate an id/name in a file with the fragment after the #.