public inbox for
 help / color / mirror / Atom feed
From: Mike Marchywka <>
To: <>
Subject: RE: [RFC] Refresh iswblank and iswspace (was Re: Update wctype     	functions to Unicode 5.2?)
Date: Mon, 15 Feb 2010 20:54:00 -0000	[thread overview]
Message-ID: <BLU113-W19C7A7C07639CBA7CE7898BE4A0@phx.gbl> (raw)
In-Reply-To: <>

> Date: Mon, 15 Feb 2010 19:55:29 +0000
> From: 
> To:
> Subject: Re: [RFC] Refresh iswblank and iswspace (was Re: Update wctype functions to Unicode 5.2?)
> 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!

anything more than 7 bits/ char, 8th can be used for partiy, does this to you.
Imagine what would happen to humanity with fonts being intermingled with

> cheers,
> DaveK
Hotmail: Free, trusted and rich email service.

      parent reply	other threads:[~2010-02-15 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
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]
2010-02-15 20:54           ` Mike Marchywka [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BLU113-W19C7A7C07639CBA7CE7898BE4A0@phx.gbl \ \ \

* 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).