[yunqa.de] Re: New DIUnicode warning
- From: "Jon Burnham" <jba@xxxxxxxxxxxxxx>
- To: <yunqa@xxxxxxxxxxxxx>
- Date: Thu, 3 May 2012 09:54:00 +0100
I think this question arose because of the new warning with the latest
update, that was the only problem. In conclusion, and from what you are
saying, as long as it's known UTF8 in and out, then we can ignore the
warning.
Until the APIs I am working with can do more than European languages, I
don't envisage working with anything other than 8 bit strings.
Thanks again Ralf.
Jon
-----Original Message-----
From: yunqa-bounce@xxxxxxxxxxxxx [mailto:yunqa-bounce@xxxxxxxxxxxxx] On
Behalf Of Delphi Inspiration
Sent: 03 May 2012 09:44
To: yunqa@xxxxxxxxxxxxx
Subject: [yunqa.de] Re: New DIUnicode warning
On 03.05.2012 10:31, Jon Burnham wrote:
> Yes, this is what I am doing - telling the parser to read UTF8 and
> working in 8 bit. I am only dealing with European languages. URLs,
> phrases and keywords, tested German, French and Spanish - all OK
> before the new update warning through to the end of the procedure.
If you use a "string" variable in Delphi XE2, you are not working entirely
in 8-bit.
> So the fact that this assigned string is already testing correct
> before casting to a RawByteString should make no difference? - as
> RawByteString does nothing to what is assigned to it, it is entirely
character neutral?
RawByteString is character neutral for 8-bit strings. It is not if you mix
it with 16-bit strings.
I can not tell from the code snippets where your problem is. I would need to
analyze the complete project (or a stripped down version of it) for more
advice.
Ralf
_______________________________________________
Delphi Inspiration mailing list
yunqa@xxxxxxxxxxxxx
//www.freelists.org/list/yunqa
_______________________________________________
Delphi Inspiration mailing list
yunqa@xxxxxxxxxxxxx
//www.freelists.org/list/yunqa
Other related posts:
