From manningc2@actrix.gen.nz Thu Jul 09 02:43:41 2009 Received: from smtp.firstline.co.nz ([203.167.210.162] helo=firstline.co.nz) by stoneboat.aleph1.co.uk with smtp (Exim 4.69) (envelope-from ) id 1MOifb-0002WM-44 for yaffs@lists.aleph1.co.uk; Thu, 09 Jul 2009 02:43:41 +0100 Received: (qmail 14798 invoked by uid 453); 9 Jul 2009 01:43:09 -0000 X-Virus-Checked: Checked by ClamAV on firstline.co.nz Received: from Unknown (HELO linux-dual-head.local) (10.14.210.25) by firstline.co.nz (qpsmtpd/0.40) with ESMTP; Thu, 09 Jul 2009 13:43:09 +1200 From: Charles Manning To: yaffs@lists.aleph1.co.uk Date: Thu, 9 Jul 2009 13:43:07 +1200 User-Agent: KMail/1.9.10 References: <4A5350E4.9050404@ecoscentric.com> In-Reply-To: <4A5350E4.9050404@ecoscentric.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200907091343.08012.manningc2@actrix.gen.nz> X-SA-Exim-Connect-IP: 203.167.210.162 X-SA-Exim-Mail-From: manningc2@actrix.gen.nz X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-1.0 required=4.5 tests=AWL,BAYES_20,SPF_NEUTRAL autolearn=no version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Subject: Re: [Yaffs] Support for UTF-8 filenames? X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.11 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2009 01:43:41 -0000 On Wednesday 08 July 2009 01:43:00 Ross Younger wrote: > This is just a thought experiment at the moment, but to what extent would > we expect YAFFS to work with UTF-8 filenames? From what I have looked at = of > the guts, YAFFS is simply treating filenames as NUL-terminated octet > strings, so it smells like it all ought to Just Work provided the given > filenames are valid UTF-8 sequences? That's my understanding too. =46rom my limited understanding, UTF-8 does not embed NULs like Unicode do= es.=20 As such I would expect UTFs to just seem like ASCII strings with odd-ball=20 characters in it. YAFFS does use strlen etc in a few places and it seems that strlen will jus= t=20 count the non-NUL bytes which will be fine. If strlen tries to be clever an= d=20 count the number of UTF-8s then that will break. =2D- Charles