Hi, Could you try using: <?xml version="1.0" encoding="iso-2022-jp"?> and specifying in the POST request: Content-Type: application/atom+xml;charset=iso-2022-jp
Another option is to try CDATA again but check that the 0x1B characters are non-encoded and in a CDATA block. Please let me know how it goes, we definitely want to cover you case in our Migration API. Julian. On Feb 21, 1:07 am, YAMANEKO <[EMAIL PROTECTED]> wrote: > Thank you for your reply. > > Yes, I already tried the both, but nothing changed, only error message > has been changed. > "org.xml.sax.SAXParseException: An invalid XML character (Unicode: > 0x1b) was found in the CDATA section." > > It seems that raw 0x1b or escaped  cannot be included in XML, even > CDATA section. Also, any entity does not be interpreted in CDATA > section, so escaped  is meaningless in CDATA. > > For example, here is a short text in iso-2022-jp. > > $B%F%9%H(B > > "" means ESC code "0x1b". > Does anyone can include this text into XML? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
