Re: Getting around .Net Strings being UTF-16 encoded only
- From: "Mike Murray" <outersource@xxxxxxxxx>
- Date: 3 Nov 2005 10:26:15 -0800
Hi folks,
Here is some more information.
The application that is expecting the UTF-8 Encoding creates a file
using the the default that comes in from the web browser and creates
the file via vbscript, windows scripting code. Right now there is no
conversion to UTF-8 happening in the vbscript, the programmer is just
relying on what comes in through the browser to the vbscript (is there
anything funny with variables storing the incoming text as UTF-16 just
like .NET does?)
What I want to do is create the same file but from vb.NET, therefore
that is why i'm using the XmlTextWriter code. Which makes sense to me,
I just want to clarify that my code is correct, and i'm going about
this the right way.
Thanks,
Mike
.
- Follow-Ups:
- Re: Getting around .Net Strings being UTF-16 encoded only
- From: Oleg Tkachenko [MVP]
- Re: Getting around .Net Strings being UTF-16 encoded only
- From: Bruno Jouhier
- Re: Getting around .Net Strings being UTF-16 encoded only
- References:
- Getting around .Net Strings being UTF-16 encoded only
- From: Mike Murray
- Re: Getting around .Net Strings being UTF-16 encoded only
- From: Oleg Tkachenko [MVP]
- Getting around .Net Strings being UTF-16 encoded only
- Prev by Date: how do you add an xml schema attributegroup to a complextype extension?
- Next by Date: Re: question on "include" in schema files (.xsd). Trouble validating schema in .NET
- Previous by thread: Re: Getting around .Net Strings being UTF-16 encoded only
- Next by thread: Re: Getting around .Net Strings being UTF-16 encoded only
- Index(es):
Relevant Pages
|