Re: International characters problem - Kyle Marvin - com.googlegroups.google-calendar-help-dataapi

11 messages in com.googlegroups.google-calendar-help-dataapiRe: International characters problem

From	Sent On	Attachments
Kulvinder Singh	21 Mar 2007 05:05
Kulvinder Singh	28 Mar 2007 05:56
Kyle Marvin	28 Mar 2007 07:02
Kulvinder Singh	28 Mar 2007 21:31
Kyle Marvin	29 Mar 2007 06:28
Kulvinder Singh	29 Mar 2007 06:52
Kyle Marvin	29 Mar 2007 07:17
Kulvinder Singh	29 Mar 2007 07:52
Kulvinder Singh	29 Mar 2007 07:53
Charlie Wood	29 Mar 2007 08:07
Kyle Marvin	29 Mar 2007 08:25

Subject:	Re: International characters problem
From:	Kyle Marvin (kmar...@google.com)
Date:	03/29/2007 06:28:34 AM
List:	com.googlegroups.google-calendar-help-dataapi

On 3/28/07, Kulvinder Singh <kulv...@yahoo.com> wrote:

Hi Kyle,

Thanks a lot for your reply. Please help me furthur in this.

I want to insert an Event in Google Calendar with Description/Content as "松本真司 &&&&". Now, how should i decide whether this is an HTML or text programmatically?

If you aren't using any HTML formatting in the content (as in the example string) , then I'd recommend just using plain text content. If you encode it as UTF-8 characters, you shouldn't have to worry about doing anything else with the HTTP Content-Type header or XML encoding attribute.

Should i set the "type" of Content element as "text/html" everytime and

HTMLENCODE it by default or any other way ?

See above. Just use "text" or leave it off since that is the default.

Hi Kulvinder,

For data in the API, you should not HTML encode the input data unless the "type" attribute of the title and content is "html". If you haven't set type, the default value is "text", per the Atom syntax spec (RFC4287). The gd:where element attributes don't have a type and are always considered to be text.

For GData to be able to properly interpret encoded characters in your data, you need to provide appropriate signals about the encoding. The character set encoding of data sent via the API is determined by one of two things: the value of the charset attribute of the HTTP Content-Type header or the value of the "encoding" attribute on the <xml> declaration. If both are present, the HTTP header is considered canonical. If neither is present, the default is "utf-8". See [1] for more details and some examples.

Hope this is helpful,

[1] - http://diveintomark.org/archives/2004/02/13/xml-media-types

Hi,

I am facing some international characterization problem with Google API.

I created a Google Event with Title = "Planeringsmöte för ansökan VR 20/3 kl 18.00 ca" and Where = "Planeringsmöte för ansökan VR 20/3 kl 18.00 ca" and Content = "Planeringsmöte för ansökan VR 20/3 kl 18.00 ca "

I did an HTMLEncode on these values of Title, Where and Content before inserting in Google

Now the event is sucessfully created at Google but with a problem. When i see the agenda or any Week/Month view etc. these characters are being rendered as :

"Planeringsmöte för ansökan VR 20/3 kl 18.00 ca"

but when i go to edit this event, the Title and Where seems corrected to "Planeringsmöte för ansökan VR 20/3 kl 18.00 ca" but whenever i switch to any other view i again see them Encoded.

Please help ------------------------------ The fish are biting. Get more
visitors<http://us.rd.yahoo.com/evt=49679/*http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php?o=US2140&cmp=Yahoo&ctv=Q107Tagline&s=Y&s2=EM&b=50>on
your site using Yahoo! Search Marketing.