Open GoogleCodeExporter opened 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
They have same roots, but it is different bug.
Original comment by kislo.metal
on 23 Dec 2010 at 7:48
Did you use firefox? it seems to work in Chromium
Original comment by jaosorior
on 6 Jan 2011 at 11:34
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
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
(sorry, more info: I'm testing with tip)
Original comment by vruiz.ju...@gmail.com
on 11 Feb 2011 at 1:06
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
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
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
Original issue reported on code.google.com by
kislo.metal
on 20 Dec 2010 at 3:25