[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly.
From: |
Chet Ramey |
Subject: |
Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly. |
Date: |
Tue, 21 Feb 2012 16:54:37 -0500 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0 |
On 2/21/12 8:43 AM, John Kearney wrote:
> signed / unsigend isn't really the problem anyway utf-8 only encodes
> up to 0x7fff ffff and utf-16 only encodes up to 0x0010 ffff.
>
> In my latest version I've pretty much removed all reference to wchar_t
> in unicode.c. It was unnecessary.
It's useful if the platform defines __STDC_ISO_10646__, wchar_t is 32 bits,
and the value is less than 0x7fffffff.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
- Fix u32toutf8 so it encodes values > 0xFFFF correctly., John Kearney, 2012/02/18
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly., Chet Ramey, 2012/02/20
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly., Eric Blake, 2012/02/21
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly., John Kearney, 2012/02/21
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly.,
Chet Ramey <=
- Initial test code for \U, John Kearney, 2012/02/21
- Here is a diff of all the changed to the unicode, John Kearney, 2012/02/21
- Re: Initial test code for \U, Chet Ramey, 2012/02/22
- Re: Initial test code for \U, Eric Blake, 2012/02/22
- Re: Initial test code for \U, John Kearney, 2012/02/26
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly., Linda Walsh, 2012/02/22
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly., Eric Blake, 2012/02/22
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly., John Kearney, 2012/02/22
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly., Linda Walsh, 2012/02/22
- Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly., Eric Blake, 2012/02/22