Re: Multibyte and unibyte file names

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden,  address@hidden,  address@hidden
> Date: Sun, 27 Jan 2013 20:55:16 -0500
> 
> At least I disagree with your Ffile_name_directory suggestion: if the
> file-name is already encoded and it results in bugs, the fix should be
> in the caller.

So you are saying these primitives should assume decoded file names,
and if called with encoded ones, exhibit undefined behavior, for which
the fix is in the caller, is that right?