X-Spam-Check-By: sourceware.org
X-Authenticated: #449785
Date: Mon, 5 Dec 2005 01:35:14 +0100 (CET)
From: Martin Koeppe <mkoeppe AT gmx DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: open() giving ENOENT when trying to create files with control  chars
In-Reply-To: <20051204194350.GG2999@calimero.vinschen.de>
Message-ID: <Pine.LNX.4.62.0512050123280.5613@vmdebian.local.koeppe-net.de>
References: <120220052038 DOT 3878 DOT 4390B0AC000B476600000F2622007601800A050E040D0C079D0A AT comcast DOT net>  <20051202220905 DOT GA2999 AT calimero DOT vinschen DOT de> <20051204172940 DOT GB3276 AT efn DOT org>  <20051204194350 DOT GG2999 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Y-GMX-Trusted: 0
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


On Sun, 4 Dec 2005, Corinna Vinschen wrote:

>> http://support.microsoft.com/default.aspx?scid=kb;en-us;117258
>> is interesting...
>
> This is certainly interesting.  Using this in Cygwin would require to
> change the path handling to using UNICODE, though, which is a major
> undertaking since the path handling throughout Cygwin is plain ASCII
> right now.

I remember having read about those mappings used by
Services for Macintosh and Services for Unix. If I remeber right, they 
are unfortunately incompatible!

SFM uses (from link above):
    Macintosh ANSI  Unicode
    -----------------------------
    0x01-0x1F       0xF001-0xF01F
    "               0xF020
    *               0xF021
    /               0xF022
    <               0xF023
    >               0xF024
    ?               0xF025
    \               0xF026
    |               0xF027

But SFU uses:
    <any invalid ascii char>   =>  0xF000 + ascii code

So for 0x01-0x1f the mapping is the same, but e.g. "?" is mapped
0x3f => 0xf03f by SFU, and not to 0xf025.

Unfortunately I didn't find the source of SFU mapping any more. The 
only thing I found:
http://www.interopsystems.com/tools/forum/tm.aspx?m=1233&mpage=1&#1236

While searching I found this thread which might be interesting when 
planning to migrate cygwin from ascii to unicode internally:
http://www.opengroup.org/austin/mailarchives/ag/msg08574.html


Martin

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/