Re: Make Unicode bugs release critical?
On 2011-02-11 15:02:02 +0100, Adam Borowski wrote:
> On Fri, Feb 11, 2011 at 02:30:24PM +0100, Vincent Lefevre wrote:
> > On 2011-02-11 15:33:49 +0500, Andrey Rahmatullin wrote:
> > > On Fri, Feb 11, 2011 at 11:14:42AM +0100, Miroslav Kure wrote:
> > > > > However, I'm curious: is there a lot of software that is broken with
> > > > > Unicode, particularly with the UTF-8 encoding? I can't remember anything
> > > > > much in recent times.
> > "less" has problems with new Unicode characters (bug 597918).
> Unicode 6.0 came out in october 2010,
The character mentioned in my bug report (U+1E9F LATIN SMALL LETTER DELTA)
appeared in Unicode 5.1.0 (March 2008).
> well after Squeeze's freeze, so you can't expect support for new
> characters already.
Well, March 2008 was more than 1 year before Squeeze's freeze.
> There are in no fonts shipped with squeeze, so not recognizing the
> characters as valid is not a big problem.
Fonts containing the character in question are shipped with Squeeze:
the character appears correctly in xterm.
> Less shouldn't maintain a private copy of character properties if
> all that data is already present in libc
> -- but guess what, wcwidth(0x1F4A9) and iswprint() don't know them
No problems with U+1E9F:
Property alnum : yes
Property alpha : yes
Property cntrl : no
Property digit : no
Property graph : yes
Property lower : yes
Property print : yes
Property punct : no
Property space : no
Property upper : no
Property xdigit: no
wcwidth = 1
So, if "less" were using libc, it wouldn't have any problem with
Vincent Lefèvre <email@example.com> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)