> > In general, they don't. Command-line utilities just use the sequence
> > of bytes entered by the user.
>
> Obviously that depends on the application. A command-line utility that
> interprets an normal xml file containing filenames know the characters
> but not the bytes. The same goes for com
Marcus Sundman <[EMAIL PROTECTED]> writes:
> So, you see, there is no way for me to use filenames intelligibly unless
> their encodings are knowable. (In fact I'm quite surprised that zfs
> doesn't (and even can't) know the encoding(s) of filenames. Usually Sun
> seems to make relatively sane desig
"Anton B. Rang" <[EMAIL PROTECTED]> wrote:
> > Do you happen to know where programs in (Open)Solaris look when they
> > want to know how to encode text to be used in a filename? Is it
> > LC_CTYPE?
>
> In general, they don't. Command-line utilities just use the sequence
> of bytes entered by the
> Do you happen to know where programs in (Open)Solaris look when they
> want to know how to encode text to be used in a filename? Is it
> LC_CTYPE?
In general, they don't. Command-line utilities just use the sequence of
bytes entered by the user. GUI-based software does as well, but the
encodin
Bart Smaalders <[EMAIL PROTECTED]> wrote:
> The OS has no way of merging your various encodings. If I create a
> directory, and have people from around the world create a file
> in that directory named after themselves in their own character sets,
> what should I see when I invoke:
>
> % ls -l |
Marcus Sundman <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Joerg Schilling) wrote:
> > Marcus Sundman <[EMAIL PROTECTED]> wrote:
> > > [EMAIL PROTECTED] (Joerg Schilling) wrote:
> > > > [...] ISO-8859-1 (the low 8 bits of UNOICODE) [...]
> > >
> > > Unicode is not an encoding, but you probably
Bart Smaalders <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Bart Smaalders <[EMAIL PROTECTED]> wrote:
> >> UTF8 is the answer here. If you care about anything more than
> >> simple ascii and you work in more than a single locale/encoding,
> >> use UTF8. You may not understand the meaning
Marcus Sundman wrote:
> Bart Smaalders <[EMAIL PROTECTED]> wrote:
>> UTF8 is the answer here. If you care about anything more than simple
>> ascii and you work in more than a single locale/encoding, use UTF8.
>> You may not understand the meaning of a filename, but at least
>> you'll see the same
[EMAIL PROTECTED] (Joerg Schilling) wrote:
> Marcus Sundman <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] (Joerg Schilling) wrote:
> > > [...] ISO-8859-1 (the low 8 bits of UNOICODE) [...]
> >
> > Unicode is not an encoding, but you probably mean "the low 8 bits of
> > UCS-2" or "the first 256 c
Bart Smaalders <[EMAIL PROTECTED]> wrote:
> > OK, thanks. I still haven't got any answer to my original question,
> > though. I.e., is there some way to know what text the filename is, or
> > do I have to make a more or less wild guess what encoding the program
> > that created the file used?
>
>
Marcus Sundman <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Joerg Schilling) wrote:
> > [...] ISO-8859-1 (the low 8 bits of UNOICODE) [...]
>
> Unicode is not an encoding, but you probably mean "the low 8 bits of
> UCS-2" or "the first 256 codepoints in Unicode" or somesuch.
Unicode _is_ an en
[EMAIL PROTECTED] (Joerg Schilling) wrote:
> [...] ISO-8859-1 (the low 8 bits of UNOICODE) [...]
Unicode is not an encoding, but you probably mean "the low 8 bits of
UCS-2" or "the first 256 codepoints in Unicode" or somesuch.
Regards,
Marcus
___
zfs-
"Anton B. Rang" <[EMAIL PROTECTED]> wrote:
> > OK, thanks. I still haven't got any answer to my original question,
> > though. I.e., is there some way to know what text the
> > filename is, or do I have to make a more or less wild guess what
> > encoding the program that created the file used?
>
>
"Anton B. Rang" <[EMAIL PROTECTED]> wrote:
> Yes -- that's why Apple includes an encoding byte in both HFS and HFS+. (In
> HFS+, filenames are normalized to 16-bit Unicode, but the encoding is still
> useful in choosing how to recompose the characters, and in providing hints
> for applications
Bart Smaalders <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Bart Smaalders <[EMAIL PROTECTED]> wrote:
> >>> I'm unable to find more info about this. E.g., what does "reject
> >>> file names" mean in practice? E.g., if a program tries to create a
> >>> file using an utf8-incompatible filen
> OK, thanks. I still haven't got any answer to my original question,
> though. I.e., is there some way to know what text the
> filename is, or do I have to make a more or less wild guess what
> encoding the program that created the file used?
You have to guess. As far as I know, Apple's HFS (and
Marcus Sundman wrote:
> Bart Smaalders <[EMAIL PROTECTED]> wrote:
>>> I'm unable to find more info about this. E.g., what does "reject
>>> file names" mean in practice? E.g., if a program tries to create a
>>> file using an utf8-incompatible filename, what happens? Does the
>>> fopen() fail? Would
Bart Smaalders <[EMAIL PROTECTED]> wrote:
> > I'm unable to find more info about this. E.g., what does "reject
> > file names" mean in practice? E.g., if a program tries to create a
> > file using an utf8-incompatible filename, what happens? Does the
> > fopen() fail? Would this normally be a probl
On Thu, Feb 28, 2008 at 05:57:21AM +0100, Roland Mainz wrote:
> Tim Haley wrote:
> > ZFS doesn't muck with names it is sent when storing them on-disk. The
> > on-disk name is exactly the sequence of bytes provided to the open(),
> > creat(), etc. If normalization options are chosen, it may do som
Roland Mainz wrote:
> Tim Haley wrote:
> > Roland Mainz wrote:
> > > Bart Smaalders wrote:
> > >> Marcus Sundman wrote:
> > >>> I'm unable to find more info about this. E.g., what does "reject file
> > >>> names" mean in practice? E.g., if a program tries to create a file
> > >>> using an utf8-inco
Tim Haley wrote:
> Roland Mainz wrote:
> > Bart Smaalders wrote:
> >> Marcus Sundman wrote:
> >>> I'm unable to find more info about this. E.g., what does "reject file
> >>> names" mean in practice? E.g., if a program tries to create a file
> >>> using an utf8-incompatible filename, what happens? D
Roland Mainz wrote:
> Bart Smaalders wrote:
>> Marcus Sundman wrote:
>>> I'm unable to find more info about this. E.g., what does "reject file
>>> names" mean in practice? E.g., if a program tries to create a file
>>> using an utf8-incompatible filename, what happens? Does the fopen()
>>> fail? Wou
Bart Smaalders wrote:
> Marcus Sundman wrote:
> > I'm unable to find more info about this. E.g., what does "reject file
> > names" mean in practice? E.g., if a program tries to create a file
> > using an utf8-incompatible filename, what happens? Does the fopen()
> > fail? Would this normally be a p
Marcus Sundman wrote:
> I'm unable to find more info about this. E.g., what does "reject file
> names" mean in practice? E.g., if a program tries to create a file
> using an utf8-incompatible filename, what happens? Does the fopen()
> fail? Would this normally be a problem? E.g., do tar and simila
Darren J Moffat <[EMAIL PROTECTED]> wrote:
> See the description of the normalization and utf8only properties in
> the zfs(1) man page.
>
> I think this might help you.
>
> normalization =none | formD | formKCf
That's apparently only for comparisons, so I don't see how it's
relevant.
>
See the description of the normalization and utf8only properties in the
zfs(1) man page.
I think this might help you.
normalization =none | formD | formKCf
Indicates whether the file system should perform a
unicode normalization of file names whenever two fil
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Marcus Sundman wrote:
> > Are path-names text or raw data in zfs? I.e., is it possible to know
> > what the name of a file/dir/whatever is, or do I have to make more
> > or less wild guesses what encoding is used where?
>
> I'm not sure what you are
Hi Marcus,
Marcus Sundman wrote:
> Are path-names text or raw data in zfs? I.e., is it possible to know
> what the name of a file/dir/whatever is, or do I have to make more or
> less wild guesses what encoding is used where?
>
> - Marcus
>
I'm not sure what you are asking here. When a zfs file
Are path-names text or raw data in zfs? I.e., is it possible to know
what the name of a file/dir/whatever is, or do I have to make more or
less wild guesses what encoding is used where?
- Marcus
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
ht
29 matches
Mail list logo
