search

latos / wave-protocol

Automatically exported from code.google.com/p/wave-protocol
0 stars 0 forks source link

Encoding problem (cyrillic) #186

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create new wave
2. add message "Привет Мир"
3. log off
4. log in
5. look at message entered at step 2

What is the expected output?
"Привет Мир"
What do you see instead?
"?????? ???"

What changeset or version are you using? On what operating system?

Please provide any additional information below.
looks like problem in metadata of gwt`s html page or something like that  (user 
input accepting in wrong encoding on server side.)

Original issue reported on code.google.com by kislo.metal on 20 Dec 2010 at 3:25

GoogleCodeExporter commented 8 years ago 
Perhaps it could be the same problem as issue 32 O_o.

Original comment by jaosorior on 22 Dec 2010 at 10:35

GoogleCodeExporter commented 8 years ago 
They have same roots, but it is different bug.

Original comment by kislo.metal on 23 Dec 2010 at 7:48

GoogleCodeExporter commented 8 years ago 
Did you use firefox? it seems to work in Chromium

Original comment by jaosorior on 6 Jan 2011 at 11:34

GoogleCodeExporter commented 8 years ago 
Works for me in chromium:
"abcdef ñakslda, lalalalaláéieçñæ@ł€¶đæßðđ@"
but not in firefox:
"abcdef �akslda, lalalalal��ie���@??�?���?@"

Seems like in firefox the characters are encoded twice.

Original comment by vruiz.ju...@gmail.com on 21 Jan 2011 at 4:07

GoogleCodeExporter commented 8 years ago 
Now I see this fixed in the wave list (chrome & ff) , but now (and this is new) 
it's broken in the wave panel (only in ff) in a similar way.

Original comment by vruiz.ju...@gmail.com on 11 Feb 2011 at 1:05

GoogleCodeExporter commented 8 years ago 
(sorry, more info: I'm testing with tip)

Original comment by vruiz.ju...@gmail.com on 11 Feb 2011 at 1:06

GoogleCodeExporter commented 8 years ago 
Browsers: ff 3.6, chromium 9.0.597.94 (at ubuntu 11.04)

While I typing client sent bad unicode data: {\"2\":\"Я\"}. But right char 
is Я. Cause from server '???' strings return in search query and reopened 
waves. Original google wave does not have this bug, in console {"2":"Я"}.

Original comment by step2back@gmail.com on 12 Feb 2011 at 4:49

GoogleCodeExporter commented 8 years ago 
updated to changeset:   903:e857a432cab5, same behave on mac (Safari 5.0.3 & 
Firefox(3) ) and on windows (Chrome).

Original comment by kislo.metal on 2 Mar 2011 at 11:47

GoogleCodeExporter commented 8 years ago 
It isn't specific to cyrillic, actually. Typing "é" will result in those 
question marks, even in Chrome (on Windows).

I remember Google Wave had this same issue on the developer preview for a few 
weeks and then it got fixed, so this is probably a regression with regards to 
that code.

I do confirm that the character displays correctly on the wave list, but not on 
the blips.

Original comment by sevenjp on 15 Mar 2011 at 6:02