Mail Archives: cygwin-developers/2002/07/03/07:30:13

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
X-WM-Posted-At:; Wed, 3 Jul 02 12:30:04 +0100
Message-ID: <00ca01c22284$f9ce27a0$0100a8c0@advent02>
From: "Chris January" <chris AT atomice DOT net>
To: <cygwin-developers AT cygwin DOT com>
References: <200207031122 DOT g63BM3lL015113 AT burner DOT fokus DOT gmd DOT de>
Subject: Re: UTF8 support in Cygwin
Date: Wed, 3 Jul 2002 12:30:03 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

> >I am working on a patch which would add UTF8 support to Cygwin.
> >i.e. Unicode filenames would be encoded as UTF8 before being returned by,
> >e.g., readdir and then converted back to Unicode before being passed to
> >Windows API.
> >This would solve Ville Herva's problem where he/she wanted to back up a
> >filesystem containing Unicode filenames using Cygwin, but found that the
> >Unicode characters were converted to question marks. Also, with an
> >appropriate terminal, it is actually possible to view the Unicode
> >(altough at the moment, it is not possible to input them correctly
> >The code is currently guarded by a CYGWIN environment variable flag,
> A long awaited feature!
> This would really help for "star" and "mkisofs".
> Star needs to archive UTF-8 coded names in the POSIX.1-2001 filenames
> and "mkisofs" needs to deal with UNICODE names in Joliet and UDF.
> How about using the LC_* locale setup to force UTF-8 coding?
The utf8 flag turns on conversion of Windows filenames from Unicode to UTF-8
and back again. This is completely unrelated to the LC_* stuff. You could
use utf8 filenames without the utf8 flag and they would just be stored as
utf8 on the Windows filesystem, but your application would see exactly the
same filename. The only reason to use this flag is if you wish to access
existing files which have Unicode filenames under Windows NT.

For the record, I've changed all the MultiByteToWideChar, etc.'s to
sys_utf8towcs now, to make it more consistent with the other conversion


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019