Bug#291889: characters not correctly passed to google search

["Jean Darcoux" <bouloumag@hotmail.com>]

Here are the reqested information about my system.

I just noticed that a similar search bar into firerfox encode the '+' as %2B 
(like I suggest). I think this is another good reason to fix this bug.

Best Regards,

Jean

-- System Information:
Debian Release: 3.1
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.28
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)

Versions of packages konqueror depends on:
ii  kcontrol                 4:3.3.1-4       KDE Control Center
ii  kdebase-kio-plugins      4:3.3.1-4       KDE I/O Slaves
ii  kdelibs4                 4:3.3.1-4       KDE core libraries
ii  kdesktop                 4:3.3.1-4       KDE Desktop
ii  kfind                    4:3.3.1-4       KDE File Find Utility
ii  libart-2.0-2             2.3.16-6        Library of functions for 2D 
graphi
ii  libc6                    2.3.2.ds1-20    GNU C Library: Shared libraries 
an
ii  libfam0c102              2.7.0-6         client library to control the 
FAM
ii  libgcc1                  1:3.4.3-6       GCC support library
ii  libice6                  4.3.0.dfsg.1-10 Inter-Client Exchange library
ii  libidn11                 0.5.2-3         GNU libidn library, 
implementation
ii  libjpeg62                6b-9            The Independent JPEG Group's 
JPEG
ii  libkonq4                 4:3.3.1-4       Core libraries for KDE's file 
mana
ii  libpcre3                 4.5-1.1         Perl 5 Compatible Regular 
Expressi
ii  libpng12-0               1.2.8rel-1      PNG library - runtime
ii  libqt3c102-mt            3:3.3.3-7       Qt GUI Library (Threaded 
runtime v
ii  libsm6                   4.3.0.dfsg.1-10 X Window System Session 
Management
ii  libstdc++5               1:3.3.5-5       The GNU Standard C++ Library v3
ii  libx11-6                 4.3.0.dfsg.1-10 X Window System protocol client 
li
ii  libxext6                 4.3.0.dfsg.1-10 X Window System miscellaneous 
exte
ii  libxrender1              0.8.3-7         X Rendering Extension client 
libra
ii  xlibs                    4.3.0.dfsg.1-10 X Keyboard Extension (XKB) 
configu
ii  zlib1g                   1:1.2.2-3       compression library - runtime



> From: Matías Costa <mcc3@alu.um.es>
> Reply-To: mcc3@alu.um.es
> To: Alejandro Exojo <suy@badopi.org>, 291889@bugs.debian.org, "Jean 
> Darcoux" <bouloumag@hotmail.com>
> Subject: Re: Bug#291889: characters not correctly passed to google search
> Date: Mon, 24 Jan 2005 00:39:51 +0100
>
> El Domingo 23 Enero 2005 21:42, Alejandro Exojo escribió:
> > El Domingo, 23 de Enero de 2005 20:53, Jean Darcoux escribió:
> > > As a solution, I recommand to replace characters like '+' by there
> > > corresponding code (like %2B in the case of '+'). The later example
> > > should then display the URL
> > > http://www.google.com/search?q=C%2B%2B&ie=UTF-8&oe=UTF-8
> >
> > The problem, is not that characters are badly encoded, is that google 
> uses
> > "+" and "-" as metacharacters for saying some things, like this:
>
> Do not confuse the string with the enconding used to transfer the string. 
> In
> URL arguments the + character is used as space, and the + is encoded as %2B
> (as Jean Darcoux states)
>
> > http://www.google.com/search?q=c+-news&ie=UTF-8&oe=UTF-8
>
> With that google understand "c -news".
>
> > Since there is no way of guessing what the user wants to search, he 
> should
> > use quotes when a literal "+" wants to be included in the search.
>
> Also, do not confuse urls with bash :) (bad joke, I know, sorry)
>
> Konqueror works correctly in unstable respect this bug. Please, provide 
> more
> info about your version. BTW, you may use reportbug, witch takes this info
> for you, and more.