dselect UTF-8 bug not fixed
> Previously Michael Piefel wrote:
> > dselect incorrectly assumes that one byte in a string occupies one
> > column on the screen. [...] However, with UTF-8, this assumption may
> > not be true.
> Don't use UTF-8, currently only 8 bit encodings are supported. Moving
> to UTF-8 is planned for a future version.
Great, then you will fix it in a future version of dselect. When you do
that, close the bug. Until then, please leave it open.
It's a minor bug. Do you want to get further reports which you have to
close one by one, or do you prefer others see it's already reported and
don't bother you anymore?
|=| Michael Piefel
|=| Humboldt-Universität zu Berlin
|=| Tel. (+49 30) 2093 3831
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org