Sadly, Alcor is not able to actively develop QS right now. However, you can email him and ask for access to the source code for the plugin.
On Aug 30, 9:34 pm, mason k <[EMAIL PROTECTED]> wrote: > The web search plugin module should parse out newline characters and > replace them with space characters instead. Some web search engines > will chomp at the newline character and only search the first line of > a string. I can't think of a usage case where a user will have > included multiple lines in a search string but only want the first > line to be searched. I also can't think of a search that behaves > differently when it receives a multi line search than when it receives > an all-spaces search (except when it is chomping at the newline). > > I'll give an example of where this could be a problem. I set up a > google maps web search bookmark. I think it would be really nifty if > I could drill into contacts from my Address Book and get their address > -> Find With... -> Google Maps Quicksearch Bookmark and see their > address. However when I do this, it only maps the first line of the > address which is not enough to get a pin on the map. Similarly I > might want to cmd-esc a two line address from a website into a google > maps web search, but I can't, because google maps chomps at the > newline. Amazon.com's search also chomps at the newline, as do most > other searches that I tried. The only two I found that can handle > newlines in their searches are Google and Wikipedia. > > Eh, where do I send this bug? I couldn't find a bug tracker on > blacktree.
