[Alpine-info] UTF-8 test message for your viewing (dis?)pleasure

[Matt Ackeret]

On Mon, 9 Mar 2009, Eduardo Chappa wrote:

>There is no guess in the code. The decision of the code is clear. 

>Everything that is ambiguous has width 2. This comes from the call to 

>c-client. This in turn produces several problems, as I have pointed out 

>earlier.


<Rodney King>
Can't we all just get along?
</Rodney King>

I admit I don't know how alpine and c-client talk to each other, if at all.
But it seems to me that if someone really wanted to put the effort into it,
some more "hidden configuration options" could be added to set the user's
choice of width for the ambiguous characters.  (And/or platform-specific code
could be added too -- I'm not sure if one can figure out on a particular
platform what font is being used, but once one DID know what font was being
used, then platform specific code is possible to find out the width of 
specific characters (err, I guess 'code points' is the real term here.))

It minorly irked me that the first and last lines of that 'box' wrapped 
for (seemingly) no good reason.  Now I know the reason.

Heck, one idea for a first try is to try to set everything as single-width
and see if tha made the behavior better for anecdotal experiences.  Even
that might be worth a hidden pref.  "Treat ambiguous characters as single
width."