linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Pavel Fedin <sonic_amiga@rambler.ru>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Full NLS support for HFS (classic) filesystem
Date: Tue, 31 May 2005 17:28:09 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0505311719330.3728@scrub.home> (raw)
In-Reply-To: <1117550958.8073.30.camel@imp.csi.cam.ac.uk>

Hi,

On Tue, 31 May 2005, Anton Altaparmakov wrote:

> So unless you use UTF8, any other conversion using NLS/code pages will
> always have failure cases...

No suprise. :)
Anyone working with different encodings and doesn't use utf8, simply has 
to expect problems.

> > So create two functions uni2char/char2uni, which provide perfect reverse 
> > mapping. Sorry, but I don't understand what your problem is here.
> > It seems you're making it more complex than it really is.
> 
> That is impossible due to the problems with compatibility characters I
> explained above which why I would agree with you that such magic
> conversions should never happen, just put "use utf8 if you have
> problems" in the mount man page...

He only wants to convert from one 8-bit encoding to another 8-bit 
encoding. It's a hack, but it's a hack which can be done transparently via 
the nls layer, so it doesn't has to be done in the filesystem.

bye, Roman

  reply	other threads:[~2005-05-31 15:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <429B1E35.2040905@rambler.ru>
2005-05-30 11:50 ` [PATCH] Full NLS support for HFS (classic) filesystem Roman Zippel
2005-05-31 13:37   ` Pavel Fedin
2005-05-31 10:45     ` Roman Zippel
2005-05-31 19:35       ` Pavel Fedin
2005-05-31 12:13         ` Roman Zippel
2005-05-31 21:21           ` Pavel Fedin
2005-05-31 13:59             ` Roman Zippel
2005-05-31 14:49               ` Anton Altaparmakov
2005-05-31 15:28                 ` Roman Zippel [this message]
2005-06-02 13:34                 ` Pavel Fedin
2005-06-02  9:24                   ` Anton Altaparmakov
2005-06-03 13:34                     ` Pavel Fedin
2005-06-03  8:09                       ` Anton Altaparmakov
2005-06-06 13:15                         ` Pavel Fedin
2005-06-06 12:44                           ` Roman Zippel
2005-06-06 21:44                             ` Pavel Fedin
2005-06-06 14:44                               ` Roman Zippel
2005-06-08 18:08                                 ` Pavel Fedin
2005-06-01  0:26             ` Roman Zippel
     [not found]               ` <429F0869.4010805@rambler.ru>
     [not found]                 ` <Pine.LNX.4.61.0506021130290.3728@scrub.home>
2005-06-03 14:00                   ` Pavel Fedin
2005-06-09 23:47   ` George Anzinger
2005-05-30 14:05 Pavel Fedin

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=Pine.LNX.4.61.0505311719330.3728@scrub.home \
    --to=zippel@linux-m68k.org \
    --cc=aia21@cam.ac.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sonic_amiga@rambler.ru \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).