Re: Multibyte and unibyte file names

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden,  address@hidden,  address@hidden
> Date: Thu, 24 Jan 2013 19:06:56 -0500
> 
> >> > So you are saying that each primitive should detect unibyte file names
> >> > it gets as arguments and DECODE_FILE them right away?
> >> I think not: I was talking about decoding the file names *returned*
> >> by primitives.
> > What would be the difference, from the POV of the callers of the
> > primitives?
> 
> That the callers get to see meaningful (decoded) names?
> That file-name manipulation functions don't have the side effect of
> encoding/decoding file names?

If we decode unibyte file names at entry to each primitive, before
doing anything else, and thereafter manipulate decoded multibyte
strings, this will happen anyway.

But since everybody (at least those who spoke) seem to think this is a
w32 only problem, I will solve it for w32 only.