Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Tue, 7 Mar 2000 13:20:49 -0500 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Character sets in win32 and cygwin Message-ID: <20000307132048.A2067@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: <200003071433 DOT PAA12299 AT burner DOT fokus DOT gmd DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200003071433.PAA12299@burner.fokus.gmd.de>; from schilling@fokus.gmd.de on Tue, Mar 07, 2000 at 03:33:25PM +0100 On Tue, Mar 07, 2000 at 03:33:25PM +0100, schilling AT fokus DOT gmd DOT de wrote: >I have a problem with mkisofs running on win32 using cygwin. >If I run mkisofs to create a ISO-9660 CD with Joliet extensions, >I get no problems (ISO-8859-1 characters are converted into UNICODE) >If I run mkisofs on cygwin, I get all umlauts converted into '_'. > >It seems that all characters in filenames, all keystrokes are vailable >or get converted into the DOS charater set. > >All outout is assumed to be DOS characters. > >Is this the expected behaviour? > >I thought that win32 should be a UNICODE based OS. It would probably be best for you to debug whatever cygwin DLL calls that mkisofs is using and report on problems there. Possibly this is a problem with the startup code in dcrt0.cc which calls SetFileApisToOEM (). cgf