From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Cc: Paul Eggert <eggert@cs.ucla.edu>, Eric Blake <eblake@redhat.com>,
bug-gnulib@gnu.org, bug-coreutils <bug-coreutils@gnu.org>
Subject: Re: bug#7948: 16-bit wchar_t on Windows and Cygwin
Date: Wed, 02 Feb 2011 20:43:00 -0000 [thread overview]
Message-ID: <AANLkTikRJxssP7OLr7O+DQZr-BpjpEZJ8Pe2uJ=msDbh@mail.gmail.com> (raw)
In-Reply-To: <201102021957.07676.bruno@clisp.org>
On 2 February 2011 18:57, Bruno Haible wrote:
> Hi Paul,
>
>> > - Define a type 'wwchar_t' on all platforms, equivalent to uint32_t
>> > on Windows platforms and to 'wchar_t' otherwise.
>>
>> As a minor point, would it be OK to call this type
>> 'xchar_t' instead? 'x' is the successor to 'w', after all,
>> and it can be thought of as an abbreviation for 'eXtended'.
>
> 'wwchar_t' means "wide wide character".
>
> In fact it's not really an "extended" character or "complex character".
> It's just what POSIX calls a 'wchar_t'.
It's extended in the sense that the original Unicode was only 16 bits
wide (which of course is why wchar_t on Windows is 16 bits). Also, I
think 'xchar_t' is less prone to typos, in particular forgetting one
of the dubyas.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-02-02 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201101310304.42975.bruno@clisp.org>
2011-01-31 19:16 ` Eric Blake
2011-01-31 20:49 ` Corinna Vinschen
2011-02-02 11:29 ` Bruno Haible
2011-02-02 12:15 ` Corinna Vinschen
2011-02-02 12:21 ` Corinna Vinschen
2011-02-02 16:03 ` Bruno Haible
2011-02-02 16:28 ` Corinna Vinschen
2011-02-02 16:35 ` Corinna Vinschen
2011-02-02 20:28 ` Andy Koppe
2011-02-04 22:46 ` Warren Young
2011-02-02 17:52 ` bug#7948: " Paul Eggert
2011-02-02 18:57 ` Bruno Haible
2011-02-02 20:43 ` Andy Koppe [this message]
2011-02-03 12:57 ` Ulf Zibis
2011-02-02 21:24 ` Eric Blake
2011-02-02 21:39 ` Corinna Vinschen
2011-02-02 23:03 ` Bruno Haible
2011-02-02 23:19 ` Eric Blake
2011-02-03 0:13 ` Bruno Haible
2011-02-03 9:42 ` Corinna Vinschen
2011-02-03 10:48 ` Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikRJxssP7OLr7O+DQZr-BpjpEZJ8Pe2uJ=msDbh@mail.gmail.com' \
--to=andy.koppe@gmail.com \
--cc=bug-coreutils@gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=cygwin@cygwin.com \
--cc=eblake@redhat.com \
--cc=eggert@cs.ucla.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).