From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262145AbVFRQEk (ORCPT ); Sat, 18 Jun 2005 12:04:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262144AbVFRQEk (ORCPT ); Sat, 18 Jun 2005 12:04:40 -0400 Received: from 212-28-208-94.customer.telia.com ([212.28.208.94]:16648 "EHLO www.dewire.com") by vger.kernel.org with ESMTP id S262145AbVFRQEi convert rfc822-to-8bit (ORCPT ); Sat, 18 Jun 2005 12:04:38 -0400 From: Robin Rosenberg To: Kernel Mailing List Subject: Re: A Great Idea (tm) about reimplementing NLS. Date: Sat, 18 Jun 2005 18:04:20 +0200 User-Agent: KMail/1.8.1 Cc: =?iso-8859-1?q?M=E5ns_Rullg=E5rd?= , Lennart Sorensen , Patrick McFarland , "Richard B. Johnson" , Lukasz Stelmach , "Alexander E. Patrakov" References: <20050617130914.GB23488@csclub.uwaterloo.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200506181804.21366.robin.rosenberg.lists@dewire.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org fredagen den 17 juni 2005 15.23 skrev Måns Rullgård: > Some characters can be encoded in several equally shortest ways. No they cannot. How to encode characters i explicitly and well defined. If you don't follow the rules you are simply not producing UTF-8, but something else. Every unicode character has exactly one UTF-8 representation. -- robin