mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: NamJae Jeon <linkinjeon@gmail.com>,
	Jeff Layton <jlayton@redhat.com>,
	Steve French <sfrench@samba.org>, <linux-cifs@vger.kernel.org>,
	<samba-technical@lists.samba.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Unix Support <unix-support@ucs.cam.ac.uk>,
	Steve French <smfrench@gmail.com>, <akpm@linux-foundation.org>,
	Anton Altaparmakov <aia21@cam.ac.uk>, <ashishsangwan2@gmail.com>
Subject: Re: CIFS: Rename bug on servers not supporting inode numbers
Date: Wed, 23 Nov 2011 17:12:45 +0000	[thread overview]
Message-ID: <20111123171245.3e3f18a7@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1111231131100.2111-100000@iolanthe.rowland.org>

On Wed, 23 Nov 2011 11:31:47 -0500 (EST)
Alan Stern <stern@rowland.harvard.edu> wrote:

> On Wed, 23 Nov 2011, NamJae Jeon wrote:
> 
> > Hi. Alan.
> > Would you know why there is no upper/lower case table in nls utf8 ?
> > And Currently Surrogate pair is not supported also in nls utf8. Is
> > there the reason ?
> 
> I don't know.

For one case translations are locale specific and very very complicated.

  reply	other threads:[~2011-11-23 17:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 15:20 Anton Altaparmakov
2011-11-03 15:42 ` Anton Altaparmakov
2011-11-03 17:40   ` Jeff Layton
2011-11-03 23:25     ` Anton Altaparmakov
2011-11-03 23:34       ` Steve French
2011-11-03 23:37         ` NamJae Jeon
2011-11-23 10:34           ` NamJae Jeon
2011-11-23 16:31             ` Alan Stern
2011-11-23 17:12               ` Alan Cox [this message]
2011-11-23 18:00                 ` Amit Sahrawat
2011-11-24  5:08                   ` Günter Kukkukk
2011-11-28  7:56                     ` Ashish Sangwan
2011-11-03 18:40   ` Shirish Pargaonkar
2011-11-04 11:16 ` Björn JACKE

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=20111123171245.3e3f18a7@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=aia21@cam.ac.uk \
    --cc=akpm@linux-foundation.org \
    --cc=ashishsangwan2@gmail.com \
    --cc=jlayton@redhat.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    --cc=smfrench@gmail.com \
    --cc=stern@rowland.harvard.edu \
    --cc=unix-support@ucs.cam.ac.uk \
    /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

all inboxes | Powered by JetHome®