On Tue, Jun 30, 2015, Alexandre Pereira Nunes wrote:
> Only UTF32 has fixed length encoding (I overheard people saying it's not
> exactly true even there, because it has unrepresentable code points, but I
> never confirmed).
Unicode allows you to take a character like 'e' and add twenty different
Em qua, 1 de jul de 2015 às 02:36, Greg Jung escreveu:
> In my programming instead of "multibytetowide" conversion preparing for a
> windows API inside #ifdef UNICODE blocks, I just call the ANSI mode of
> the function with ascii c-strings
> passed in, and let microsoft perform the A->W convers
In my programming instead of "multibytetowide" conversion preparing for a
windows API inside #ifdef UNICODE blocks, I just call the ANSI mode of the
function with ascii c-strings
passed in, and let microsoft perform the A->W conversions. When does this
simpler approach break?
- Only use Win3
Grasp this sentence: implementation dependent.
wchar_t is wide char, it's made to imply that each representable character
can take more than one byte to encode a character. It was created before
utf8 got mainstream. And, as there were competing encodings (UCS-2 fixed
length vs what ended up being
On 30.06.2015 19:44, p...@arbolone.ca wrote:
> I have been reading that wchat_t, and therefore wstring, is neither UTF-8 nor
> a UTF-16 character set. So, what is wstring good for then?
Whether it's UTF-16 or UCS-2 depends on the implementation of the library
that handles wstring.
Sources, which
I have been reading that wchat_t, and therefore wstring, is neither UTF-8 nor a
UTF-16 character set. So, what is wstring good for then?
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
--
