Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #97636

Re: UTF-8 with C, simply

From James Kuyper <jameskuyper@verizon.net>
Newsgroups comp.lang.c
Subject Re: UTF-8 with C, simply
Date 2016-11-28 09:10 -0500
Organization A noiseless patient Spider
Message-ID <o1hdph$km3$1@dont-email.me> (permalink)
References <6a3e7ab3-eb0d-4794-befb-adae3729c746@googlegroups.com> <o1gqmo$cnl$1@gioia.aioe.org>

Show all headers | View raw


On 11/28/2016 03:42 AM, Lorinczy Zsigmond wrote:
> Well, you should now that neither ucs2, ucs4 or utf16 isn't equal to utf8.

Well, that seems consistent with what he said. You wouldn't need to call
special routines to  cause a conversion from utf8 to ucs2 or ucs4 if
utf8 were, in fact, equal to one of them. What made you feel the need to
point that out? Normally, unless you have a specific reason for thinking
otherwise, the simple fact that they have different names would imply
that they're probably not equal.

> under newer C-standards you can use data-types char16_t and char32_t 
> (from header uchar.h),
> they are meant to be utf16 and utf32 respectively

That's only true on implementations that choose to pre#define
__STDC_UTF_16__ or __STDC_UTF_32__, respectively. Otherwise, the
encoding associated with those typedefs is implementation-defined
(6.10.8.2p1). Of course, this is a significant improvement over wchar_t,
for which no such macros are available.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

UTF-8 with C, simply luser droog <luser.droog@gmail.com> - 2016-11-27 18:09 -0800
  Re: UTF-8 with C, simply James Kuyper <jameskuyper@verizon.net> - 2016-11-27 22:05 -0500
  Re: UTF-8 with C, simply Lorinczy Zsigmond <zsiga@nospam.for.me> - 2016-11-28 09:42 +0100
    Re: UTF-8 with C, simply James Kuyper <jameskuyper@verizon.net> - 2016-11-28 09:10 -0500
      Re: UTF-8 with C, simply Philipp Klaus Krause <pkk@spth.de> - 2016-11-28 21:55 +0100
        Re: UTF-8 with C, simply "James R. Kuyper" <jameskuyper@verizon.net> - 2016-11-28 16:18 -0500
  Re: UTF-8 with C, simply Siri Cruise <chine.bleu@yahoo.com> - 2016-11-28 07:00 -0800
    Re: UTF-8 with C, simply Philipp Klaus Krause <pkk@spth.de> - 2016-11-28 21:53 +0100
    Re: UTF-8 with C, simply Keith Thompson <kst-u@mib.org> - 2016-11-28 21:38 -0800
  Re: UTF-8 with C, simply Nobody <nobody@nowhere.invalid> - 2016-12-01 01:52 +0000
    Re: UTF-8 with C, simply luser droog <luser.droog@gmail.com> - 2016-11-30 18:20 -0800
      Re: UTF-8 with C, simply luser droog <luser.droog@gmail.com> - 2016-11-30 18:25 -0800
        Re: UTF-8 with C, simply luser droog <luser.droog@gmail.com> - 2016-11-30 18:28 -0800

csiph-web