From: Pavel Fedin <sonic_amiga@rambler.ru>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-fsdevel@vger.kernel.org, Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [PATCH] Full NLS support for HFS (classic) filesystem
Date: Mon, 06 Jun 2005 09:15:54 -0400 [thread overview]
Message-ID: <42A44C8A.2000906@rambler.ru> (raw)
In-Reply-To: <Pine.LNX.4.60.0506030906110.4926@hermes-1.csi.cam.ac.uk>
Anton Altaparmakov wrote:
> Well only some codepages have this problem. If you use say KOI-8R and
> Latin9 or something then you would be fine. But use CP936 or Big5 and you
> are screwed.
Understand.
>> Didn't meet such cases. Well, you're right, in this case dynamic table
>>building will fail. But at least dynamic table solves problems with
>>non-translatable characters.
>
>
> That's because you are using KOI-8R which suggests to me that you don't
> often use chineese or other asian characters...
Yes, i don't use them at all.
> I agree with filenames like that you have a problem. But it is EXT3's
> design fault that this happens. It should have stored the names in UTF8
> or Unicode or whatever to start with then you could have used anything on
> the system and it would have always worked...
Well, anyway i don't have time to write EXT4 :-)
P.S. Okay, as Roman suggested i will:
1. Replace "hfscodepage" with "codepage".
2. Fix coding style.
But i would strongly suggest to leave dynamic table algorythm as is.
Please beleive me, i wrote it because it's really needed.
Roman, is it okay?
--
Kind regards, Pavel Fedin
next prev parent reply other threads:[~2005-06-06 5:15 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
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 [this message]
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=42A44C8A.2000906@rambler.ru \
--to=sonic_amiga@rambler.ru \
--cc=aia21@cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zippel@linux-m68k.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 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).