Hi Danny,
I don't know how to LC environment variables map to code pages, but I
can tell you a few other things :
1. UTF-8 is THE standard : Internet, default set up for the fast
majority of Linux users etc. etc.
2. CP_UTF8 is NOT supported on all WinCE (Core) devices.
The solution is to not to u
Ah, I didn't get the detail of your first message right.
So you're saying the CP_ACP is a bad idea.
Do you (does anyone) know of a way to figure out which conversion to
use ?
Danny
On Fri, 2008-09-12 at 02:26 -0700, Pawel Veselov wrote:
> In windows, you specify what the target encoding
In windows, you specify what the target encoding is. It's possible to
convert to UTF-8, or other things, but the current implementation uses
CP_ACP that requests the translation is done into ASCII encoding. I
think in UNIX that is determined by one of them LC_* environment
variables.
On Fri, Sep 1
I believed multibyte strings were using UTF-8, is it true or not?
2008/9/11 Danny Backx <[EMAIL PROTECTED]>
> On Thu, 2008-09-11 at 11:25 -0700, Pawel Veselov wrote:
> > Hi,
> >
> > I was looking at the libcwd... There is a XCEGetCurrentDirectoryA()
> > function. It picks the current directory, t
On Thu, 2008-09-11 at 11:25 -0700, Pawel Veselov wrote:
> Hi,
>
> I was looking at the libcwd... There is a XCEGetCurrentDirectoryA()
> function. It picks the current directory, that is stored in wide
> chars, determines its length (in wide chars), and then converts wide
> chars to multibyte. Then
Hi,
I was looking at the libcwd... There is a XCEGetCurrentDirectoryA()
function. It picks the current directory, that is stored in wide
chars, determines its length (in wide chars), and then converts wide
chars to multibyte. Then the wide char length is used as a terminator
for the length of the
