Bug with 21.5.16: cannot use UTF-8 encoded file names.

[Hrvoje Niksic]

"Stephen J. Turnbull" <stephen at xemacs.org> writes:

> I see a lot of UTF-8, UTF-16, UTF-16-broken-by-Microsoft, and
> UTF-16-broken-by-Microsoft-embedded-in-a-proprietary-file-format,
> and I've never seen a use for anything except the standard Mule
> APIs.  The only low-level things you might need are
> `char-to-unicode' and `unicode-to-char', and those are already in
> 21.5.

Except we also need encode-char if we're going for FSF compatibility
and/or the minimum compatibility with mule-ucs.

> AFAICT, "compatibility" is just a matter of
>
> (unless (emacs-version>= 21 5 6)
>   (require 'un-define))
>
> If there's something provided by mule-ucs that isn't provided by
> 21.5, then it's _not provided by 21.5_, and we need to fix
> 21.5---there's no "compatibility API" when the feature itself isn't
> provided.

I think I see what you mean.