why the % cruft?

Vadim Plessky lucy-ples at mtu-net.ru
Tue Jul 9 09:56:21 BST 2002


On Monday 08 July 2002 11:33 pm, Waldo Bastian wrote:
|  I don't know. The web-page is in ISO-8859-1 so we send in that encoding.
| We can send in utf-8 but I doubt that will work if the webserver expects
| iso-8859-1. Since google adds "ie=ISO-8859-1" itself I strongly suspect
| that it expects to receive iso-8859-1. We can't send utf-16 because HTTP is
| a 8-bit protocol, not 16-bit.

ok, what about IMAP folder names than?

|
|  Cheers,
|  Waldo
|
|  On Monday 08 July 2002 12:04 pm, Hetz Ben Hamo wrote:
|  > The question is - why only ISO 8859-1 and not in UTF (8 or 16)?
|  >
|  > Hetz
|  >
|  > On Monday 08 July 2002 20:28, Waldo Bastian wrote:
|  > > On Monday 08 July 2002 09:12 am, Vadim Plessky wrote:
|  > > > There was similar bug report about Google, Konq wrongly encodes URL
|  > > > from Google search if you search for non-Latin word.
|  > > > Again, open Google and type "������" in Search box. Than hit Search.
|  > > > You will get:
|  > > > http://www.google.com/search?hl=en&ie=ISO-8859-1&q=%3F%3F%3F%3F%3F%3
|  > > >F&b tn G= Google+Search
|  > >
|  > > How do you propose to express such query in ISO-8859-1?
|  > >
|  > > Cheers,
|  > > Waldo

-- 

Vadim Plessky
http://kde2.newmail.ru  (English)
33 Window Decorations and 6 Widget Styles for KDE
http://kde2.newmail.ru/kde_themes.html
KDE mini-Themes
http://kde2.newmail.ru/themes/





More information about the kfm-devel mailing list