From luismbo at gmail.com Tue May 10 08:38:38 2011 From: luismbo at gmail.com (=?ISO-8859-1?Q?Lu=EDs_Oliveira?=) Date: Tue, 10 May 2011 09:38:38 +0100 Subject: [babel-devel] patch for cp1252 In-Reply-To: <874o5pggxd.fsf@gmail.com> References: <874o5pggxd.fsf@gmail.com> Message-ID: Hello, On Sat, Apr 23, 2011 at 3:50 PM, Nicolas Martyanoff wrote: > I added support for the cp1252 encoding: Just dropping a note to tell you I've applied your patch but haven't been able to push it yet because c-l.net is undergoing a migration process. Thanks, -- Lu?s Oliveira http://r42.eu/~luis/ From luismbo at gmail.com Wed May 11 07:32:33 2011 From: luismbo at gmail.com (=?ISO-8859-1?Q?Lu=EDs_Oliveira?=) Date: Wed, 11 May 2011 08:32:33 +0100 Subject: [babel-devel] octets-to-string with UTF8 and Byte Order Marker In-Reply-To: <6D8D0E393259694788637A444E1C5EC75C2AEE@venus.intra.aws.net> References: <6D8D0E393259694788637A444E1C5EC75C2A62@venus.intra.aws.net> <6D8D0E393259694788637A444E1C5EC75C2AEE@venus.intra.aws.net> Message-ID: Hello, Sorry for the late reply. On Thu, Apr 21, 2011 at 10:36 PM, Rob Blackwell wrote: > I'm still a little confused as to why the length is 4 and not 3 - shouldn?t the byte order mark have been discarded? I'm not sure. I couldn't find any clear indications on how leading BOMs should be handled for UTF-8. The BOM FAQ seems to indicate they should be converted to ZERO WIDTH NON-BREAKING SPACEs, maybe. Any comments? It would perhaps be interesting to check what well established libraries such as ICU do. Cheers, -- Lu?s Oliveira http://r42.eu/~luis/