Re: [Mutt] #3061: display broken when a mail contains U+FEFF

To: cb@xxxxxxxx, agriffis@xxxxxxxxx, brendan@xxxxxxxxxx, cam@xxxxxxxxx, pdmef@xxxxxxx
Subject: Re: [Mutt] #3061: display broken when a mail contains U+FEFF
From: Mutt <fleas@xxxxxxxx>
Date: Sun, 20 Jul 2008 19:39:13 -0000
Cc: mutt-dev@xxxxxxxx
In-reply-to: <036.2a5f9aae750d707a7048242b2b04ba5d@xxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: fleas@xxxxxxxx
References: <036.2a5f9aae750d707a7048242b2b04ba5d@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#3061: display broken when a mail contains U+FEFF

Comment (by pdmef):

 I'm not sure about k==0 either, but shouldn't that happen only when we
 read L'\0'?

 You're right that testing for wcwidth returning 0 should be used instead,
 but it's broken on for example OS X. Linux says u+feff and u+200b have a
 width of 0 and are printable, OS X says u+200b has a width of 1 and is
 printable but u+feff has a width of -1 (non-printable) and and iswprint
 "correctly" returns 0 for it.

 I attached a patch that tests for wcwidth being zero and for the hard-
 coded constants.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3061#comment:10>

References:
- [Mutt] #3061: display broken when a mail contains U+FEFF
  - From: Mutt

Prev by Date: [PATCH] Interix support in regexp.c
Next by Date: Re: [Mutt] #2893: fcc_attach=no should record filenames (like
Previous by thread: Re: [Mutt] #3061: display broken when a mail contains U+FEFF
Next by thread: Re: [Mutt] #3061: display broken when a mail contains U+FEFF
Index(es):
- Date
- Thread