[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: convert-standard-filename

From: Lennart Borgman
Subject: Re: convert-standard-filename
Date: Mon, 8 Aug 2011 12:37:56 +0200

On Mon, Aug 8, 2011 at 06:38, Eli Zaretskii <address@hidden> wrote:
>> From: Lennart Borgman <address@hidden>
>> Date: Mon, 8 Aug 2011 06:26:28 +0200
>> Cc: address@hidden, address@hidden, address@hidden
>> On Mon, Aug 8, 2011 at 06:19, Eli Zaretskii <address@hidden> wrote:
>> >
>> >> Are there any cases were the result would be ambigious?
>> >
>> > The case of "c:foobar", as pointed out by Stefan earlier in this
>> > thread.  If it's taken as a local absolute file name, then on Windows
>> > there's no need to do anything about it.  If it is taken as a Posix
>> > relative file name, the colon should be replaced with some other
>> > character.
>> I see. But on Windows it could hardly be a Posix relative file name,
>> or could it?
> It can't, so convert-standard-filename should replace the colon.
> That's what convert-standard-filename does: takes a Posix file name
> and produces a file name usable on non-Posix filesystems.

And when does such a situation arise? (I.e. when does it happen that a
Posix file name looking like a Windows file name needs to be converted
to a Windows file name.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]