Closed GoogleCodeExporter closed 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
Does anyone know when the bug will be fixed?
Original comment by jag...@gmail.com
on 6 May 2010 at 8:33
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
I also do not understand. 15 days ago all was fine.
Original comment by jag...@gmail.com
on 6 May 2010 at 11:22
Can anyone answer please?
Original comment by efat...@gmail.com
on 20 May 2010 at 10:15
:-((
Original comment by jag...@gmail.com
on 26 May 2010 at 11:07
Same for me... :-(
Original comment by efat...@gmail.com
on 26 May 2010 at 11:35
C'mon, it's trivial, +1 for fixing this
Original comment by dusan.ma...@gmail.com
on 28 May 2010 at 6:48
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
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
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
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
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
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
@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
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
@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
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
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
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
Original issue reported on code.google.com by
jag...@gmail.com
on 28 Apr 2010 at 7:45