Re: New escape method proposal (was: Re: Possible solution for special characters in makefile paths)

[Eli Zaretskii]

> From: Paul Smith <address@hidden>
> Date: Tue, 22 Apr 2014 15:00:27 -0400
> 
> The quoting sequence works like a function.  When a string containing it
> is expanded, first its contents are expanded.  This allows values like
> "$[$(DIR)]" to behave as expected.  It does mean that users still need
> to be careful with "$" inside quoting; they'll need to double it as
> usual.  The $(value ...) function may also prove useful in this context.
> 
> After expansion, all special characters in the resulting string will be
> replaced with encoded values so that those characters no longer match
> the "normal" versions of those characters: e.g., the quoted space will
> not match SPACE (ASCII 32).
> 
> The resulting encoded string will be compatible with any character
> encoding which uses ASCII-compatible meanings for characters codes
> 0-127.

What about non-ASCII characters?  Make works in the current locale
(AFAIK), so non-ASCII characters can have arbitrary single- or
multi-byte encodings.  Will the above encoding of special characters
be compatible with the locale-encoded non-ASCII characters?