linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: rae l <crquan@gmail.com>
Cc: Alexey Salmin <alexey.salmin@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Maximum filename length
Date: Sat, 22 Nov 2008 22:08:06 -0500	[thread overview]
Message-ID: <20081123030806.GH9150@mit.edu> (raw)
In-Reply-To: <91b13c310811211850s74cb9ec4x6b311612ed31664c@mail.gmail.com>

On Sat, Nov 22, 2008 at 10:50:25AM +0800, rae l wrote:
> In China, there's also a trend moving ahead from 2bytes charsets
> (GB2312/GBK/GB18030/BIG5) to UTF-8, so all Chinese characters will
> need 3 bytes for each to each instead of 2 from then on. The 255
> filename length limit the Chinese filename to 85 characters:

Sure, but 85 characters is a lot, given that each character might be
the equivalent of multiple letters.  For example the English word
"country", which takes six characters, or 6 bytes in UTF-8, can be
encoded as a single Chinese ideograph, which can be encoded in 3 bytes
in UTF-8.  Something like "United States of America", is encoded in 24
bytes in English, and 6 bytes (two ideographs) in Chinese in UTF-8.
My name, "Theodore Yue Tak Ts'o", takes 21 bytes in English and UTF-8.
In Chinese, it's 3 ideographs, or 9 bytes in UTF-8.  I'm choosing
fairly basied examples here, of course, but I think it's in general
true.

As a final example consider, "The Tao which can be described is not
the true Tao".  This can be expressed *much* more succiently in
Chinese.  :-)

So I don't think people who use the Chinese writing system have much
to complain about with respect to the 255 byte / 85 ideograph limit.
I have much more sympathy for people who trying to are trying to write
something like "Union of Soviet Socialist Republics" in Russian, and
find that it takes many more bytes in UTF-8.....

					- Ted

  reply	other threads:[~2008-11-23  4:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 12:51 Maximum filename length Alexey Salmin
2008-11-21 22:32 ` Theodore Tso
2008-11-22  2:50   ` rae l
2008-11-23  3:08     ` Theodore Tso [this message]
2008-11-22 18:48   ` Alexey Salmin
2008-11-22 23:36     ` Andreas Dilger
2008-11-23 22:15       ` Andi Kleen

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=20081123030806.GH9150@mit.edu \
    --to=tytso@mit.edu \
    --cc=alexey.salmin@gmail.com \
    --cc=crquan@gmail.com \
    --cc=linux-ext4@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 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).