10 messages in com.googlegroups.google-calendar-help-dataapiRe: 400 Bad Request on Entries with C...| From | Sent On | Attachments |
|---|---|---|
| Marsupi | 20 May 2007 15:33 | |
| Matt (GooSync) | 21 May 2007 08:07 | |
| Marsupi | 21 May 2007 10:26 | |
| Marsupi | 21 May 2007 10:52 | |
| Matt (GooSync) | 23 May 2007 02:34 | |
| Marsupi | 23 May 2007 03:43 | |
| Marsupi | 23 May 2007 03:43 | |
| Matt (GooSync) | 23 May 2007 07:08 | |
| Marsupi | 23 May 2007 10:15 | |
| Lane LiaBraaten (Google) | 23 May 2007 11:24 |
| Subject: | Re: 400 Bad Request on Entries with Content values![]() |
|---|---|
| From: | Lane LiaBraaten (Google) (api....@gmail.com) |
| Date: | 05/23/2007 11:24:47 AM |
| List: | com.googlegroups.google-calendar-help-dataapi |
Hi,
Glad to see you've mostly worked this out. The thread you referenced points out the subtle difference between XML escaping and HTML encoding. It may be possible to move the XML escaping into the client libraries so you don't have to worry about it.
Don't forget about apostrophe (') --> '
Cheers, Lane
On May 23, 10:15 am, Marsupi <mars...@marsupi.ch> wrote:
Hi Matt
Thanks for the hint with the XML-Encode. I found out, that they were discussing this topic here some time ago. see:http://groups.google.com/group/google-calendar-help-dataapi/browse_th...
I changed my implementation to go with XML-Encoding: string content = appointment.Notes; content = content.Replace("\"", """); content = content.Replace("<", "<"); content = content.Replace(">", ">"); content = content.Replace("&", "&"); eventEntry.Content.Content = content;
It works perfect so far.
Cheers, Adrian
On 23 Mai, 16:09, "Matt (GooSync)" <matt...@toffa.com> wrote:
Yeah your right Adrian.
What a bummer swapping one problem for another.
I did find another way around it if you XML encode the "&" as "&" then it works using the regular text content type.
I also found that we get the same problem with "<" although that can be replaced with "<" and that works, however the ">" works fine on its own.
I'm not sure if I need to work around this for the moment or wait to see if Google have a simple fix for it their end.
Mattwww.GooSync.com




