public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Mg3a - a version of Mg2a developed on Cygwin
Date: Thu, 24 Feb 2011 14:48:00 -0000	[thread overview]
Message-ID: <4D666FCA.9070301@redhat.com> (raw)
In-Reply-To: <20110224115056.GT9392@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

On 02/24/2011 04:50 AM, Corinna Vinschen wrote:
> On Feb 24 12:19, Bengt Larsson wrote:
>> Bengt Larsson wrote:
>>> I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's
>>> wcwidth may be worth thinking about. I suppose it will be consistent
>>> with mintty that way; otherwise not?
>>
>> And: is wcwidth always available in modern Unices? How do you find out
>> these things? I mean practically available.
> 
> wcwidth and wcswidth are XSI extensions, so they are optional.  As for
> finding out, that's usally nicely done by autoconf'ing your project.

And if you don't mind [L]GPL licensing, gnulib provides a source code
replacement that guarantees wide character support on all modern porting
platforms (particularly useful for mingw, which is sorely lacking on
this front); and is currently working on introducing a wwchar_t type
that is guaranteed to be UTF-32 even on cygwin (this is how coreutils
gets wide character support for things like wc).  Portions of that
gnulib code are incorporated into libunistring.  But from the sounds of
your program's license, I'm not sure you can take advantage of gnulib or
libunistring.

-- 
Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2011-02-24 14:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23  8:57 Bengt Larsson
2011-02-23  9:11 ` Bengt Larsson
2011-02-23  9:29   ` Corinna Vinschen
2011-02-23  9:33     ` Bengt Larsson
2011-02-23 18:25 ` Buchbinder, Barry (NIH/NIAID) [E]
2011-02-23 18:53   ` Andrew Schulman
2011-02-23 19:36     ` Bengt Larsson
2011-02-24  8:56       ` Corinna Vinschen
2011-02-24 10:56         ` Bengt Larsson
2011-02-24 11:15           ` Corinna Vinschen
2011-02-24 11:40             ` Bengt Larsson
2011-02-24 11:55               ` Corinna Vinschen
2011-02-24 12:16             ` Andy Koppe
2011-02-24 18:51               ` Bengt Larsson
2011-02-25  2:24                 ` Cyrille Lefevre
2011-02-25  2:25                   ` Cyrille Lefevre
2011-02-25  6:48                     ` Bengt Larsson
2011-02-25  6:47                   ` Bengt Larsson
2011-02-25  6:55                     ` Kenneth Wolcott
2011-02-25 14:09                       ` Bengt Larsson
2011-02-25 21:46                         ` Bengt Larsson
2011-02-26  2:48                           ` Kenneth Wolcott
2011-02-24 11:19           ` Bengt Larsson
2011-02-24 11:51             ` Corinna Vinschen
2011-02-24 14:48               ` Eric Blake [this message]
2011-02-25  8:05         ` wcwidth and terminals [Re: Mg3a - a version of Mg2a developed on Cygwin] Thomas Wolff
2011-02-25 11:06           ` Corinna Vinschen
2011-02-26  9:52             ` Andy Koppe

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=4D666FCA.9070301@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    /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).