Re[2]: 3 bugs

[Paul Sokolovsky <paul-ml at is dot lg dot ua>]

Hello DJ,

DJ Delorie <dj@delorie.com> wrote:

DD> It sounds like this is a "feature" of the Win32 file system, in that
DD> it doesn't *quite* preserve the file name correctly.  If so, there's
DD> not much we can do about it.  Except, perhaps, to MIME encode the
DD> problem file names :-(

    Cool idea! ;-) But what about mere urlencoding filenames? Here
problem arises: what to do with '%' itself. At least 3 following
choices are available:

1. Be formally correct: replace '%' with '%25'. But this will lead to
incompatibility with native apps. E.g.: script, native apps delivers
filename and cygwin apps tries to open it.

2. Don't touch '%' at all.

3. Oversafing: try filename with '%' urlencoded, if it fails, try
original.

         For me, 1 is not acceptable, and 3 way to complicated. So,
I've chosen 2 - I don't know about any app using % in filenames
consistently, so to come upon filename with '%' followed by two uppercase
hex digits is very low probability for me.



--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com