Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp3824509ybz; Tue, 28 Apr 2020 00:49:27 -0700 (PDT) X-Google-Smtp-Source: APiQypLpKnEhHMmR8C4Kih/wGLCR5ArALXQhXG/QjgFZ4V50Rh/Jf5HV1bgf1j6QwwHlFK+jTbI2 X-Received: by 2002:a17:906:35cd:: with SMTP id p13mr24400098ejb.206.1588060167139; Tue, 28 Apr 2020 00:49:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588060167; cv=none; d=google.com; s=arc-20160816; b=BMgFXIa9ogR7J6a31a05FOXIK1RxdrZJQ4Ixh457ssc9poSo8suRZEzfPb9rLveq2A x4TWz+1DSoGNTB+xd+8uMqw1ZzJ0wM4XmZVIzbDxKkWLfBBg+uL61x+iryO84DZo3Rw0 46kYE8mM0jKyVLR2/5aJUh4NKHYwxixafLIejN6Bss7koxkfwSIvJerc7Ppl0mDCfAWl /P1pr7Rs2Tksph9VAkyNOPs/njEEkmg0vaJVmg6/d1tny+xAx9ZZA+nZpGOsODxOSFsC DnIMdV4YiHo4gzn8J7kQAg455TTLAEZ06AiLfny/RPe1TBSfnSclFLXabymjPPYzKFT7 9nOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=LC7WSxyrhmQeR1Rd7WNagiqLWbF+q6mi2gRt/hUisas=; b=V4oKCZxD7ucHnZD96RgXXzoH2TbNFk7A5w02LuTAO6n6md040AJ0VDHEG08V9Lfx0v faBNPud6Vt3BPmq63VCtnLXqLPGsFXXjzoRKspfFP+F19dxjJsxTyDQMhJTA5wbLSBTp yhHWmFfxB8j/sXMznkOcCnnDnrf4VsnSBoXi1lc0Qefr5DPTs5OPMNtoUh4Cs4trJ/gz xwHJiCfP7bqat8Am6GHlSrIFbkQfiM3N0Tte4xihcgs+IeDM991ZJayP9E8ZT0Iw4NwR VX+0sDhqCubfYi+T6hQa109YcWL8PHr//dDWbwCw0lpM2f5fLJTeNhuO0xT9TfTxMcIL U73w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="g2J9L/Z+"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s4si1370426ejx.332.2020.04.28.00.49.04; Tue, 28 Apr 2020 00:49:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="g2J9L/Z+"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726678AbgD1Hq4 (ORCPT + 99 others); Tue, 28 Apr 2020 03:46:56 -0400 Received: from mail.kernel.org ([198.145.29.99]:40398 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726253AbgD1Hqz (ORCPT ); Tue, 28 Apr 2020 03:46:55 -0400 Received: from pali.im (pali.im [31.31.79.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 17626206A5; Tue, 28 Apr 2020 07:46:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588060015; bh=Yu1yHSEbM7UvnreW4VbWBBp6FDeif1jXQ1bMBO+35AI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=g2J9L/Z+US9yUFhggxbwGgaoN7BfTgOzNGAVSF1W5yHTLAAUrfEJlrEUrQcnmb8EF RLN+hTR6fYKIh+o67x++dRLLYAJWkrIpdE/m2b58mO8xyXA+0PhsI+A1akVDTLXjZ6 7kDJXwmhsUojV8JTeFGQZMzmIpADrf4RwY2RL1xw= Received: by pali.im (Postfix) id 2E053735; Tue, 28 Apr 2020 09:46:53 +0200 (CEST) Date: Tue, 28 Apr 2020 09:46:53 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Sasha Levin Cc: Valdis =?utf-8?Q?Kl=C4=93tnieks?= , Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Sasha Levin , Christoph Hellwig Subject: Re: exfat upcase table for code points above U+FFFF (Was: Re: [PATCH] staging: exfat: add exfat filesystem code to staging) Message-ID: <20200428074653.kcq6ibj6rjlrnau7@pali> References: <20190830075647.wvhrx4asnkrfkkwk@pali> <20191016140353.4hrncxa5wkx47oau@pali> <20191016143113.GS31224@sasha-vm> <20191016160349.pwghlg566hh2o7id@pali> <20191016203317.GU31224@sasha-vm> <20191017075008.2uqgdimo3hrktj3i@pali> <20200213000656.hx5wdofkcpg7aoyo@pali> <20200213211847.GA1734@sasha-vm> <20200421213045.skv2dvgm3xuspbl7@pali> <20200427154913.GR13035@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200427154913.GR13035@sasha-vm> User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 27 April 2020 11:49:13 Sasha Levin wrote: > On Tue, Apr 21, 2020 at 11:30:45PM +0200, Pali Rohár wrote: > > On Thursday 13 February 2020 16:18:47 Sasha Levin wrote: > > > On Thu, Feb 13, 2020 at 01:06:56AM +0100, Pali Rohár wrote: > > > > In released exFAT specification is not written how are Unicode code > > > > points above U+FFFF represented in exFAT upcase table. Normally in > > > > UTF-16 are Unicode code points above U+FFFF represented by surrogate > > > > pairs but compression format of exFAT upcase table is not clear how to > > > > do it there. > > > > > > > > Are you able to send question about this problem to relevant MS people? > > > > > > > > New Linux implementation of exfat which is waiting on mailing list just > > > > do not support Unicode code points above U+FFFF in exFAT upcase table. > > > > > > Sure, I'll forward this question on. I'll see if I can get someone from > > > their team who could be available to answer questions such as these in > > > the future - Microsoft is interested in maintaining compatiblity between > > > Linux and Windows exFAT implementations. > > > > Hello Sasha! Have you got any answer from exfat MS team about upcase > > table for Unicode code points above U+FFFF? > > Sorry for taking so long. This is my understanding from the Windows > folks: Windows filesystems just don't support variable encoding length, > and expect UCS-2 strings. Ok, so should I understand your answer as exFAT upcase table does not support representing Unicode code points above U+FFFF and therefore exFAT implementation should expect that toupper(u) = u and tolower(u) = u for any Unicode code point u in range [U+10000, U+10FFFF]? This is how current exfat linux driver behave.