Re: Unicode POST with IWebBrowser2::Navigate
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Wed, 20 Feb 2008 07:38:44 -0500
"Jeff" <jeff.hillman@xxxxxxxxx> wrote in message
news:404276d9-959f-4642-ac49-bf33e3bf61fe@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 20, 9:55 am, "Igor Tandetnik" <itandet...@xxxxxxxx> wrote:
I suggest you use UTF-8, and specify appropriate charset in
Content-Type header.
Thank you very much for your reply. If you don't mind, could I ask
for a little clarification? I assume the Content-Type header would be
"Content-Type: text/xml; encoding=utf-8\r\n"
charset=, not encoding=
but I'm not sure how I
would use that encoding in my call to IWebBrowser2::Navigate. What do
I need to do differently to initialize the "VARIANT *PostData"
parameter?
Nothing. It's still an array of bytes. Presumably, you have a Unicode
string you want to post. Convert it to UTF-8 with
WideCharToMultiByte(CP_UTF8), then pack the resulting bytes into a
safearray.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Follow-Ups:
- Re: Unicode POST with IWebBrowser2::Navigate
- From: Jeff
- Re: Unicode POST with IWebBrowser2::Navigate
- References:
- Unicode POST with IWebBrowser2::Navigate
- From: Jeff
- Re: Unicode POST with IWebBrowser2::Navigate
- From: Igor Tandetnik
- Re: Unicode POST with IWebBrowser2::Navigate
- From: Jeff
- Unicode POST with IWebBrowser2::Navigate
- Prev by Date: Re: Unicode POST with IWebBrowser2::Navigate
- Next by Date: Re: Unicode POST with IWebBrowser2::Navigate
- Previous by thread: Re: Unicode POST with IWebBrowser2::Navigate
- Next by thread: Re: Unicode POST with IWebBrowser2::Navigate
- Index(es):
Relevant Pages
|