"Eric Pouech" <[EMAIL PROTECTED]> wrote:
> +static void INT21_ConvertFindDataAtoW(WIN32_FIND_DATAA *dataA,
> + const WIN32_FIND_DATAW *dataW)
> +{
> +dataA->dwFileAttributes = dataW->dwFileAttributes;
> +dataA->ftCreationTime = dataW->ftCreationTime;
"Pouech Eric DMI AEI CAEN" <[EMAIL PROTECTED]> wrote:
> That's exactly my point. If the user didn't correctly configure
> his/her locale wrt. The iocharset of the drive, then trouble's
> ahead. So, we can either suggest that it's up to the user to do
> it correctly (and in that case CP_UNIXCP is j
Pouech Eric DMI AEI CAEN <[EMAIL PROTECTED]> writes:
> My first (dumb) reaction was if it's in there, it means we need it
> for some cases. But, I don't want to support this codepage option
> for no real need, so if no one objects, we could remove it.
It's here because we didn't have CP_UNIXCP su
I.e. it's quite a fair play to assume that the user has correctly configured the system to work with his/her locale.
That's exactly my point. If the user didn't correctly configure his/her locale wrt. The iocharset of the drive, then trouble's ahead. So, we can either suggest that it's up to the
"Eric Pouech" <[EMAIL PROTECTED]> wrote:
> but which charset is used when getting the filename (from a directory
> enum for example). The charset of the mount option, the default charset
> of the kernel, or the charset of default locale ?
Look at the following line, borrowed from my /etc/fstab:
Dmitry Timoshkov wrote:
"Eric Pouech" <[EMAIL PROTECTED]> wrote:
but couldn't this be different from the charset used for mounting the
filesystem ? AFAICS, on VFAT systems, long names are stored in Unicode.
The charset in the mount option let you specify the charset for the
Unicode -> multi-by
"Eric Pouech" <[EMAIL PROTECTED]> wrote:
> but couldn't this be different from the charset used for mounting the
> filesystem ? AFAICS, on VFAT systems, long names are stored in Unicode.
> The charset in the mount option let you specify the charset for the
> Unicode -> multi-byte...
> All filen
Dmitry Timoshkov wrote:
"Eric Pouech" <[EMAIL PROTECTED]> wrote:
Codepage: if you mount a fs with a given codepage, you need that cp
information to transform properly the filenames into unicode. Ideally,
we should get this information from OS
We already have that information, the support for
On September 22, 2003 07:08 am, Dmitry Timoshkov wrote:
> We already have that information, the support for OS locale is implemented
> via a Wine extension - CP_UNIXCP. The codepage parameter should go away as
> soon as all locale information is moved (or duplicated) in ntdll from
> kernel.
OK, I'
"Eric Pouech" <[EMAIL PROTECTED]> wrote:
> Codepage: if you mount a fs with a given codepage, you need that cp
> information to transform properly the filenames into unicode. Ideally,
> we should get this information from OS
We already have that information, the support for OS locale is impleme
On September 21, 2003 10:20 am, Eric Pouech wrote:
> Codepage: if you mount a fs with a given codepage, you need that cp
> information to transform properly the filenames into unicode. Ideally,
> we should get this information from OS
> ReadVolInfo: whether you can try to get the volume information
Dimitrie O. Paun wrote:
On September 20, 2003 02:39 pm, Eric Pouech wrote:
for the time being, we'll be living with two sets of data for device
configuration. At the end, of course, only the newly introduced shall
subsist.
If you add/delete config options, please send me a note so I can
update t
On September 20, 2003 02:39 pm, Eric Pouech wrote:
> for the time being, we'll be living with two sets of data for device
> configuration. At the end, of course, only the newly introduced shall
> subsist.
If you add/delete config options, please send me a note so I can
update the options table. I
13 matches
Mail list logo
