GNU bug report logs - #32272
[PATCH] iscntrl: behavior for chars >= 0x80

Previous Next

Package: coreutils;

Reported by: L A Walsh <coreutils <at> tlinx.org>

Date: Wed, 25 Jul 2018 17:24:02 UTC

Severity: normal

Tags: patch

To reply to this bug, email your comments to 32272 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-coreutils <at> gnu.org:
bug#32272; Package coreutils. (Wed, 25 Jul 2018 17:24:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to L A Walsh <coreutils <at> tlinx.org>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Wed, 25 Jul 2018 17:24:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: L A Walsh <coreutils <at> tlinx.org>
To: Coreutils <bug-coreutils <at> gnu.org>
Subject: Re: [PATCH] iscntrl: behavior for chars >= 0x80
Date: Wed, 25 Jul 2018 10:23:15 -0700

Pádraig Brady wrote:
> +This function does not support arguments outside of the range of the
> +unsigned char type in locales with large character sets, on some platforms.
> +OS X 10.5 will return non zero for characters >= 0x80 in UTF-8 locales.
>   
---
   According to Unicode, characters 0x80-0x9F are control
characters, but characters >=0xA0 are not (and have different
classifications (at least in Unicode).

   The patch doesn't say if OS X 10.5 is classifying them correctly
or not.  For example,  0xA0 is a type of Space, some are symbols, some are
letters, some are a type of punctuation, etc...

   Perhaps OS X is using their Unicode definition for characters defined
to be in a Unicode compatible encoding?
This bug report was last modified 6 years and 329 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.