Tickets :: [#1826] Charset problem in Google search block

6.0.0-alpha12

6/7/25

Summary	Charset problem in Google search block
Queue	Horde Base
Queue Version	3.0.4
Type	Bug
State	Resolved
Priority	2. Medium
Owners
Requester	alex (at) vc (dot) bks (dot) by
Created	04/19/2005 (7354 days ago)
Due
Updated	05/13/2005 (7330 days ago)
Assigned
Resolved	05/13/2005 (7330 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

05/13/2005 09:24:54 PM	Jan Schneider	Comment #4 State ⇒ Resolved	Reply to this comment
Fixed.

04/21/2005 12:13:17 PM	alex (at) vc (dot) bks (dot) by	Comment #3	Reply to this comment
Maybe, but ~~ticket 1323~~ din't explain who is wrong and what we can do to resolve this problem. For example, I see that google receive that url after Horde query: ...le.com/search?ie=UTF-8&oe=UTF-8&hl=en&q=%u0442%u0435%u0441%u0442 and that url after direct quemy from google: ...le.com/search?hl=en&lr=&q=%D1%82%D0%B5%D1%81%D1%82 Maybe it query encoding problem?

04/20/2005 08:35:36 AM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
Duplicate of ~~bug 1329~~.

04/19/2005 11:39:30 PM	alex (at) vc (dot) bks (dot) by	Comment #1 State ⇒ Unconfirmed Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ Charset problem in Google search block Queue ⇒ Horde Base	Reply to this comment
Query to Google from block works fine with using latin characters only. If using international characters, in google searchtab we see something like that: %u0442%u0435%u0441%u0442 (I type 'test' with cyrillic)