"YOU AND THE ART OF ONLINE DATING" is the only product on the market that will take you step-by-step through the process of online dating, provide you with the resources to help ensure success. Get it now!
Yes. The standard COM string type is BSTR. It is a Unicode string encoded in UTF16, just like Windows' native string type No, a COM method isn't going to understand a UTF8 string, it will turn it into Chinese.
UTF8 is a good encoding for a text file, not for programs manipulating strings in memory. UTF8 requires anywhere between 1 and 4 bytes to encode a Unicode codepoint. Very incompatible with basic string manipulations like getting the size or indexing a character C and C++ programs tend to use 8-bit encodings, compatible with the "char" type.
That's an old practice, dating back from an era before Unicode was around. There's nothing attractive about it, there are many 8-bit encodings. The typical problem is that data entered as text can only be interpreted correctly if it is read by a program that uses the same 8-bit encoding.In other words, when the computers are less than 1000 miles apart.
Less in Europe.
Yes. The standard COM string type is BSTR. It is a Unicode string encoded in UTF16, just like Windows' native string type.No, a COM method isn't going to understand a UTF8 string, it will turn it into Chinese.
UTF8 is a good encoding for a text file, not for programs manipulating strings in memory. UTF8 requires anywhere between 1 and 4 bytes to encode a Unicode codepoint. Very incompatible with basic string manipulations like getting the size or indexing a character.
C and C++ programs tend to use 8-bit encodings, compatible with the "char" type. That's an old practice, dating back from an era before Unicode was around. There's nothing attractive about it, there are many 8-bit encodings.
The typical problem is that data entered as text can only be interpreted correctly if it is read by a program that uses the same 8-bit encoding. In other words, when the computers are less than 1000 miles apart. Less in Europe.
Sounds to me like you've got it backward. He's calling into a C# COM component from C++. – sblom Apr 24 '10 at 23:06 @sblom: yes, your answer mystified me.COM looks the same way on both ends.
Automation has always been Unicode enabled. – Hans Passant Apr 25 '10 at 8:00.
No. Yes. Put the attribute return: MarshalAs(UnmanagedType.
LPStr) before the method definition in C# if you'd like to return the string as an ANSI string instead of Unicode. Yeah--the author may have done that to maintain very fine-grained control on the encoding of the contents of the string by side-stepping the default marshalling behavior.
The standard COM string type is BSTR. It is a Unicode string encoded in UTF16, just like Windows' native string type. No, a COM method isn't going to understand a UTF8 string, it will turn it into Chinese.
UTF8 is a good encoding for a text file, not for programs manipulating strings in memory. UTF8 requires anywhere between 1 and 4 bytes to encode a Unicode codepoint. Very incompatible with basic string manipulations like getting the size or indexing a character.
C and C++ programs tend to use 8-bit encodings, compatible with the "char" type. That's an old practice, dating back from an era before Unicode was around. There's nothing attractive about it, there are many 8-bit encodings.
The typical problem is that data entered as text can only be interpreted correctly if it is read by a program that uses the same 8-bit encoding. In other words, when the computers are less than 1000 miles apart. Less in Europe.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.