[yunqa.de] Re: New DIUnicode warning
- From: "Jon Burnham" <jba@xxxxxxxxxxxxxx>
- To: <yunqa@xxxxxxxxxxxxx>
- Date: Sat, 5 May 2012 12:37:04 +0100
Hi Michael, Ralf et al
After your great link, I decided to investigate this stuff further on SO,
and came up with a few good links (with good external links as well).
For those like me who archive the Yunqa list, I thought it might be helpful
as a reference for this complex (to me) subject.
Here they are:
http://stackoverflow.com/questions/498315/delphi-2009-rawbytestring-vagaries
http://stackoverflow.com/questions/6061919/delphi-xe-rawbytestring-vs-ansist
ring
http://stackoverflow.com/questions/1115023/delphi-2009-implicit-string-to-ra
wbytestring-conversion-warnings
http://stackoverflow.com/questions/1399395/how-do-the-new-string-types-work-
in-delphi-2009-2010
Kind regards
Jon
From: yunqa-bounce@xxxxxxxxxxxxx [mailto:yunqa-bounce@xxxxxxxxxxxxx] On
Behalf Of Michael Schwarzl
Sent: 03 May 2012 10:13
To: yunqa@xxxxxxxxxxxxx
Subject: [yunqa.de] Re: New DIUnicode warning
Hello Jon,
have a look at this thread. It reveals some magic on the assignment of
strings in Delphi2010 and newer:
https://forums.codegear.com/message.jspa?messageID=436937
Best regards,
Michael
Am 03.05.2012 10:54, schrieb Jon Burnham:
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
--
Michael Schwarzl
msse professionelle software
kellau 152 · 5431 kuchl
www.msse.at · www.prophysio.at
t. +43 6244 3333
Sollten Sie nicht der genannte oder beabsichtigte Empfänger dieser
E-Mail sein, dann bitte ich Sie mich kurz darüber zu informieren
oder eine Ansichtskarte zu senden. Herzlichen Dank. ;-)
Other related posts: