Re: UTF-8 locale & POSIX text model

2017-11-26 Thread Hans Åberg
> On 26 Nov 2017, at 13:43, k...@keldix.com wrote: > > Well, the pathname processing should be a function of the filesystem. Eg if > you have a windows > filesystem, or an apple filesystem mounted on a linux operating system, then > the file names > of the foreign system should be interpreted

Re: UTF-8 locale & POSIX text model

2017-11-26 Thread Hans Åberg
> On 26 Nov 2017, at 13:43, k...@keldix.com wrote: > > I don't have windos nor apple systems, but they run utf-16 natively, and > recent > Windows 10 system have a full linux (ubuntu) subsystem. I could also see > problems > with utf-16 and posix, but at least apple should have solved that

Re: UTF-8 locale & POSIX text model

2017-11-26 Thread Stephane Chazelas
2017-11-26 14:07:50 +0100, k...@keldix.com: [...] > > For instance, as currently specified, POSIX says that the > > output of the "locale" utility be suitable for reinput to the > > shell and requiring double-quote quoting in some cases. > > > > Using double-quote quoting is problematic because

Re: UTF-8 locale & POSIX text model

2017-11-26 Thread k...@keldix.com
On Sun, Nov 26, 2017 at 02:09:21AM +, Danny Niu wrote: > > > On 26 Nov 2017, at 3:53 AM, k...@keldix.com wrote: > > On Wed, Nov 22, 2017 at 05:43:51PM +, Stephane Chazelas wrote: > 2017-11-22 16:27:15 +0100, Martijn Dekker: > Op 22-11-17 om 16:02 schreef Geoff

Re: UTF-8 locale & POSIX text model

2017-11-26 Thread Stephane Chazelas
2017-11-25 20:53:20 +0100, k...@keldix.com: [...] > > It just says those characters are the one constituting the > > portable character set. It doesn't specify the encoding other > > than it mandates the encoding of those characters to be > > invariant in the charsets in the system's supported