From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: 'The Vulgar and Unprofessional Cygwin-Talk List'
<cygwin-talk@cygwin.com>
Subject: RE: [RFC] Refresh iswblank and iswspace (was Re: Update wctype functions to Unicode 5.2?)
Date: Mon, 15 Feb 2010 20:12:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A208B4292D0E@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <4B79A6B1.3000508@gmail.com>
Dave Korn sent the following at Monday, February 15, 2010 2:55 PM
>On 15/02/2010 09:35, Corinna Vinschen wrote:
>> On Feb 14 18:21, Andy Koppe wrote:
>>>>> For a start, here are patches to iswblank and iswspace to add the
>>>>> missing characters U+180e (MONGOLIAN VOWEL SEPARATOR),
>>>> The sons of the mighty Chinggis do not "separate" their vowels!
>>>> They sweep down in a mighty horde from the steppe on horseback and
>>>> cleave them asunder with their swords!
>>> Yeah, shouldn't that be MONGOLIAN BOWEL SEPARATOR?
>>
>> I'm concerned. Do you think that's a bug in Unicode 5.2? Should we
>> report this upstream?
>
> We don't "report" to upstream! We pillage and burn and disembowel
> our way across Europe to upstream, leaving a trail of grieving
> orphans and widows in our wake!
^
Windows
next prev parent reply other threads:[~2010-02-15 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100212205705.GF5683@calimero.vinschen.de>
[not found] ` <20100213143809.GM5683@calimero.vinschen.de>
2010-02-14 17:25 ` Dave Korn
2010-02-14 18:21 ` Andy Koppe
2010-02-15 9:35 ` Corinna Vinschen
2010-02-15 19:38 ` Dave Korn
2010-02-15 20:12 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2010-02-15 20:54 ` Mike Marchywka
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=0105D5C1E0353146B1B222348B0411A208B4292D0E@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=cygwin-talk@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).