On Iau, 2005-08-25 at 20:00 -0400, Daniel B. wrote:
> Which standards?
Traditional unix namespace is a sequence of bytes with '/' as a
seperator and \0 as a terminator. There are no other restrictions. UTF-8
is essentially a retrofit onto that.
> The standards I've read (mostly XML- and
On Thu, 2005-08-25 at 20:00 -0400, Daniel B. wrote:
> Alan Cox wrote:
> > On Sul, 2005-06-19 at 18:55, Pavel Machek wrote:
[...]
> > > If we are serious about utf-8 support in ext3, we should return
> > > -EINVAL if someone passes non-canonical utf-8 string.
> >
> > That would ironically not be
On Thu, 2005-08-25 at 20:00 -0400, Daniel B. wrote:
Alan Cox wrote:
On Sul, 2005-06-19 at 18:55, Pavel Machek wrote:
[...]
If we are serious about utf-8 support in ext3, we should return
-EINVAL if someone passes non-canonical utf-8 string.
That would ironically not be standards
On Iau, 2005-08-25 at 20:00 -0400, Daniel B. wrote:
Which standards?
Traditional unix namespace is a sequence of bytes with '/' as a
seperator and \0 as a terminator. There are no other restrictions. UTF-8
is essentially a retrofit onto that.
The standards I've read (mostly XML- and
Alan Cox wrote:
>
> On Sul, 2005-06-19 at 18:55, Pavel Machek wrote:
> ...
> >
> > If we are serious about utf-8 support in ext3, we should return
> > -EINVAL if someone passes non-canonical utf-8 string.
>
> That would ironically not be standards compliant
Which standards?
The standards I've
Alan Cox wrote:
On Sul, 2005-06-19 at 18:55, Pavel Machek wrote:
...
If we are serious about utf-8 support in ext3, we should return
-EINVAL if someone passes non-canonical utf-8 string.
That would ironically not be standards compliant
Which standards?
The standards I've read
6 matches
Mail list logo
