From lovesan.ru at gmail.com Sun Oct 3 08:44:32 2010 From: lovesan.ru at gmail.com (Dmitry Ignatiev) Date: Sun, 3 Oct 2010 12:44:32 +0400 Subject: [babel-devel] UTF-16/32 encodings with explicit endianness Message-ID: Hi there. I've added support for UTF-16LE, UTF-16BE, UTF-32LE and UTF-32BE. Here's the new version of enc-unicode.lisp -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: enc-unicode.tar.gz Type: application/x-gzip Size: 7694 bytes Desc: not available URL: From luismbo at gmail.com Mon Oct 4 00:09:34 2010 From: luismbo at gmail.com (=?ISO-8859-1?Q?Lu=EDs_Oliveira?=) Date: Mon, 4 Oct 2010 01:09:34 +0100 Subject: [babel-devel] UTF-16/32 encodings with explicit endianness In-Reply-To: References: Message-ID: Hello Dmitry, On Sun, Oct 3, 2010 at 9:44 AM, Dmitry Ignatiev wrote: > I've added support for UTF-16LE, UTF-16BE, UTF-32LE and UTF-32BE. > Here's the new version of enc-unicode.lisp Thanks for your patch. Do you think you could generalize the code generation a bit in order to avoid all that code repetition? If you don't have the inclination to do that, I'll probably apply your patch as is. Tests would be nice as well. Cheers, -- Lu?s Oliveira http://r42.eu/~luis/ From lovesan.ru at gmail.com Mon Oct 4 11:38:16 2010 From: lovesan.ru at gmail.com (Dmitry Ignatiev) Date: Mon, 4 Oct 2010 15:38:16 +0400 Subject: [babel-devel] UTF-16/32 encodings with explicit endianness In-Reply-To: References: Message-ID: Alright, i've removed all that copy'n'paste code. Hope those new macros don't seem too weird. Btw, and also added UCS-2 variations. But no tests for now, sorry. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: enc-unicode.tar.gz Type: application/x-gzip Size: 7858 bytes Desc: not available URL: From lovesan.ru at gmail.com Mon Oct 4 13:37:27 2010 From: lovesan.ru at gmail.com (Dmitry Ignatiev) Date: Mon, 4 Oct 2010 17:37:27 +0400 Subject: [babel-devel] UTF-16/32 encodings with explicit endianness In-Reply-To: References: Message-ID: Oh, wait. There was a bug with code limit stuff and ucs-2. Here's the fixed version. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: enc-unicode.tar.gz Type: application/x-gzip Size: 7877 bytes Desc: not available URL: From lovesan.ru at gmail.com Mon Oct 4 19:42:33 2010 From: lovesan.ru at gmail.com (Dmitry Ignatiev) Date: Mon, 4 Oct 2010 23:42:33 +0400 Subject: [babel-devel] UTF-16/32 encodings with explicit endianness In-Reply-To: References: Message-ID: Btw, there was a bug in (define-decoder :utf-32) and (define-code-point-counter :utf-32) At the beginning of that macros, the code that checks for BOM: (case (,getter seq 0 4) ... I suppose there must be "start"(as in utf-16 decoder/code-point-counter), not "0", in this form? If so, that bug is in my code also. And so, this line in "make-bom-check-form" local function of "define-ucs" macro: (case (,,getter ,,src 0 ,',bytes :ne) should be replaced by this line: (case (,,getter ,,src ,,start ,',bytes :ne) -------------- next part -------------- An HTML attachment was scrubbed... URL: From lovesan.ru at gmail.com Thu Oct 28 17:50:07 2010 From: lovesan.ru at gmail.com (Dmitry Ignatiev) Date: Thu, 28 Oct 2010 21:50:07 +0400 Subject: [babel-devel] Unicode encodings with explicit endianness Message-ID: Hello again, Lu?s Please, can you hurry up a bit with applying my unicode-related patch? I'm currently in process of developing a library, a binding to ms windows api: http://github.com/Lovesan/doors And the reason of me being worried about that patch is because my library is unable to correctly operate on windows unicode strings without UTF-16LE support in babel. -------------- next part -------------- An HTML attachment was scrubbed... URL: