Lukasz Stelmach <[email protected]> writes:
> Lennart Sorensen napisał(a):
>
>>>And it is good in a way, however, i think kernel level translation
>>>should be also possible. Either done by a code in each filsystem or by
>>>some layer above it.
>>
>> What do you do if the underlying filesystem can not store some unicode
>> characters that are allowed on others?
>
> That's why UTF-8 is suggested. UTF-8 has been developed to "fool" the
> software that need not to be aware of unicodeness of the text it manages
> to handle it without any hickups *and* to store in the text information
> about multibyte characters.What characters exactly you do mean? NULL?
> There is no NULL byte in any UTF-8 string except the one which
> terminates it.
That's exactly how ext3, reiserfs, xfs, jfs, etc. all work. A few
filesystems are tagged as using some specific encoding. If your
filesystem is marked for iso-8859-1, what should a kernel with a
conversion mechanism do if a user tries to name a file 김?
>> I think UDF is a better filesystem for many types of media since it is
>> able to me more gently to the sectors storing the meta data than VFAT
>> ever will be.
>
> I've tried cd packet writing with UDF and it gives insane overhead of
> about 20%. What metadata you'd like to store for example on your
> flashdrive or a floppy disk?
Filename, timestamps, all the usual.
--
Måns Rullgård
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
