From: Dave Kleikamp <shaggy@austin.ibm.com>
To: frederik@ofb.net
Cc: fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: jfs, special characters
Date: Sun, 27 Feb 2005 22:47:06 -0600 [thread overview]
Message-ID: <1109566026.8448.19.camel@localhost> (raw)
In-Reply-To: <20050227230012.GA23340@a5.repetae.net>
On Sun, 2005-02-27 at 15:00 -0800, Frederik Eaton wrote:
> Thanks, you were right that I recently upgraded to 2.6 (actually I
> transferred the hard drive between machines), and with a "mount /home -o
> remount,iocharset=utf8" at least I can access the files now. But the
> names aren't what they should be, for instance I see:
>
> 04-The_Dark_Of_The_MatinΘe.ogg
>
> (that's a theta). Were they supposed to be correct?
Not necessarily. Even if the character returned is correct utf8, the
terminal (xterm?) displaying the name may be assuming a different
character set. It's also possible that on the older system,
CONFIG_NLS_DEFAULT was not set to the same locale that the system used,
so the character stored in the name was not the right unicode, but it
was accessed consistently on the old system so it worked as long as
nothing changed.
> As an aside, now, I just tried "mount /home -o
> remount,iocharset=iso8859-1", and got same problem
This is no surprise. iso8859-1 has the same mapping as iocharset=none
(the 2.6 default). (The "none" keyword is first supported in
2.6.11-rc4-mm1 and 2.4.30-pre2, so you probably won't be able to use
it.)
> ls: '/home/shared/frederik/Franz_Ferdinand/Franz_Ferdinand/04-The_Dark_Of_The_Matin?e.ogg': No such file or directory
>
> But when I repeated the "mount /home -o remount,iocharset=utf8"
> command, the listing didn't show the name with a theta character, but
> instead with two question marks:
>
> 04-The_Dark_Of_The_Matin??e.ogg
>
> Strange behavior. I.e., upon changing the mount options and then
> changing them back I get a different listing.
That I wouldn't expect. I really have no clue why it isn't consistent.
The easiest way to "fix" these files (assuming there aren't too many) is
to mount with iocharset=utf8, rename the files using only ascii
characters, remount again with iocharset=iso8859-1, and rename the files
to their proper names. After that you should be able to mount without
any iocharset flag and get sane behavior.
> Frederik
--
David Kleikamp
IBM Linux Technology Center
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-02-28 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 4:34 jfs, special characters Frederik Eaton
2005-02-26 16:51 ` Sonny Rao
2005-02-26 17:58 ` Dave Kleikamp
2005-02-27 23:00 ` Frederik Eaton
2005-02-28 4:47 ` Dave Kleikamp [this message]
2005-02-28 5:42 ` Frederik Eaton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1109566026.8448.19.camel@localhost \
--to=shaggy@austin.ibm.com \
--cc=frederik@ofb.net \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.