Ok. But i did not understand a point: if i work
with "char" and call any function of the Windows Api what version it will
call?
The Wide version (W) or the Ascii version (A)? So
you are advicing me to use almost always "char"?
My first thought was to have 3 versions of each
library function, one for each UTF type. It quickly became clear that Phobos
would get too large and bulky with this. So, the plan evolved so that Phobos
would revolve about UTF-8 (which *is* unicode, so the library functions do
support unicode). Currently, not all of the Phobos library functions handle
UTF-8 correctly, but many do (see
std.file).