search

dintorf / gdata-javascript-client

Automatically exported from code.google.com/p/gdata-javascript-client
0 stars 0 forks source link

Data is double-encoded UTF-8 -> UTF-8, which gives strings like R��mi instead of Rémi when using js library #15

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Steps to reproduce this issue:

1. Create new contact in your Gmail with unicode character in its Name 
(containing ěščřžýáíé or other czech or russian characters eg. Jiří 
Hunka).

2. Go to Google interactive samples page:
http://code.google.com/apis/contacts/docs/1.0/developers_guide_js.html#Inte
ractive_Samples or http://code.google.com/intl/cs-
CZ/apis/contacts/docs/1.0/developers_guide_js.html#Interactive_Samples

3. Click on "Retrieving contacts using query parameters".

4. Run the code by clicking Run.

5. You will see name = Ji���� Hunka instead of Jiří Hunka.

Problem is with erroneously transmitted symbols from Google Contacts trough 
Google data API (JavaScript). Display of any non ASCII characters in 
Unicode (UTF8) does not work properly: for example ěščřžýáíé.

Yet last week all was fine, but now it shows double question mark in a 
lozenge instead of these special characters (ěščřžýáíé etc.) This 
problem 
is reflected in all JavaScript applications that retrieves data from Google 
contacts. The issue arose last week out of nowhere (probably by some change 
on Google's side, this is not a application specific bug, but now a bug in 
all applications written in JavaScript and using the Google data API. Java 
and C and other language has special chars correctly.

Code of the wrong transmitted character is 65533.

Links on people whom I have found have the same problem:
http://www.google.com/support/forum/p/apps-apis/thread?
tid=57c56de74f6c8ace&hl=en
http://www.google.com/support/forum/p/apps-apis/thread?
tid=55bdefc63be4bb0e&hl=en
http://www.google.com/support/forum/p/apps-apis/thread?
tid=4288d18fff0f1271&hl=en

Can anyone help? Or does anyone know when the bug will be fixed?

Thanks

Original issue reported on code.google.com by jag...@gmail.com on 28 Apr 2010 at 7:45

GoogleCodeExporter commented 8 years ago 
I confirm.

It seems like all these accentuated characters end up as two #65533 unicode 
chars.

Original comment by api.nico...@gtempaccount.com on 29 Apr 2010 at 12:21

GoogleCodeExporter commented 8 years ago 
Does anyone know when the bug will be fixed?

Original comment by jag...@gmail.com on 6 May 2010 at 8:33

GoogleCodeExporter commented 8 years ago 
I don't understand that such a severe bug takes such a long time to be 
corrected!

Original comment by efat...@gmail.com on 6 May 2010 at 8:37

GoogleCodeExporter commented 8 years ago 
I also do not understand. 15 days ago all was fine.

Original comment by jag...@gmail.com on 6 May 2010 at 11:22

GoogleCodeExporter commented 8 years ago 
Can anyone answer please?

Original comment by efat...@gmail.com on 20 May 2010 at 10:15

GoogleCodeExporter commented 8 years ago 
:-((

Original comment by jag...@gmail.com on 26 May 2010 at 11:07

GoogleCodeExporter commented 8 years ago 
Same for me... :-(

Original comment by efat...@gmail.com on 26 May 2010 at 11:35

GoogleCodeExporter commented 8 years ago 
C'mon, it's trivial, +1 for fixing this

Original comment by dusan.ma...@gmail.com on 28 May 2010 at 6:48

GoogleCodeExporter commented 8 years ago 
It is a fatal error when it all except the English-speaking countries does not 
work!

Original comment by jag...@gmail.com on 29 May 2010 at 7:59

GoogleCodeExporter commented 8 years ago 
Hello, why they can not fix. Can we not write back. Tell my where to write that 
they have corrected.

Original comment by wrximpre...@gmail.com on 11 Jun 2010 at 8:39

GoogleCodeExporter commented 8 years ago 
It's been couple of weeks now, which tells me that nobody is using that API, at 
least not for anything serious or i18nized, maybe we should not use it as well, 
and let it die from under-usage disease.

What do you think big brother?

Original comment by dusan.ma...@gmail.com on 11 Jun 2010 at 8:47

GoogleCodeExporter commented 8 years ago 
Google does not support their own JS API. Two months no change.

Original comment by jag...@gmail.com on 28 Jun 2010 at 7:18

GoogleCodeExporter commented 8 years ago 
I don't have the issue since a week and it looks like it's fixed. Strange that 
you still have it. Otherwise, I still have the issue on Google Calendar JS API.

Original comment by efat...@gmail.com on 28 Jun 2010 at 8:40

GoogleCodeExporter commented 8 years ago 
Hey all,

As efattal experienced, this issue has now been fixed (at least it's working on 
my tests).

If you guys are still facing the issue, could you provide a way for me to 
replicate it?

efattal -> Same thing, could you provide a step by step way to replicate the 
issue on Calendar if possible?

Cheers!
Nicolas

Original comment by api.nico...@gtempaccount.com on 29 Jun 2010 at 2:46

GoogleCodeExporter commented 8 years ago 
@Nicolas:
- Create an event sith accentuated characters in the title
- Open the samples page in the API docs : 
http://gdata-jsguide.appspot.com/static/calendar/index.html#retrieveallevent_anc
hor
- Run the "Retrieve all events" example

You get #65533 unicode chars instead of the accentuated letters.

Original comment by efat...@gmail.com on 29 Jun 2010 at 2:50

GoogleCodeExporter commented 8 years ago 
Thanks efattal,

Indeed, I can confirm, looks like the same bug.
I'll let the developer know right now. Thanks for your report!

I'll keep you updated on this thread!
Cheers!

Original comment by api.nico...@gtempaccount.com on 29 Jun 2010 at 2:59

GoogleCodeExporter commented 8 years ago 
@Nicolas:
By the way, there is the same problem on Google Analytics JS API (accentuated 
characters in the name of profiles are replaced by #65533 unicode chars).

Thanks for your help, it is very urgent now (2 months!).

Original comment by efat...@gmail.com on 29 Jun 2010 at 3:44

GoogleCodeExporter commented 8 years ago 
This should be fixed now.  Please let us know if you have any issues.

Original comment by mon...@gmail.com on 29 Jun 2010 at 3:46

GoogleCodeExporter commented 8 years ago 
Thanks efattal,

I'll let Monsur know internally for the Analytics API as well ;) He probably 
haven't read my last emails yet :D

Cheers!

Original comment by api.nico...@gtempaccount.com on 29 Jun 2010 at 3:48

GoogleCodeExporter commented 8 years ago 
Hey efattal,

So the code has been fixed but both products (Calendar and Contacts) have 
different release cycle for their servers. Contacts have already updated their 
server to a new version. This fix should be applied to Calendar API servers 
early next week.

Cheer!

Original comment by api.nico...@gtempaccount.com on 30 Jun 2010 at 12:35