[Aptitude-devel] Bug#489150: aptitude: broken vertical alignment of line ends if there are umlauts in changelogs

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo


Hi Axel,

2008-07-04 16:14 Daniel Burrows:
>On Thu, Jul 03, 2008 at 03:50:10PM +0200, Axel Beckert <abe at deuxchevaux.org> was heard to say:
>> When I open an uxterm on some Etch machine, ssh into my Unstable
>                 ^^^^^^
>> machine as root, start aptitude interactively, select the dhcp3-server
>> package and press "C" for changelog, all lines in the changelog which
>> contain umlauts or letters with accents have the line ending shifted
>> to the left and leaves some blank white blocks. The umlauts itself are
>> displayed fine, though.
>
>  [snip]
>
>> Kernel: Linux 2.6.18-6-xen-amd64 (SMP w/1 CPU core)
>> Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
>          ^^^^^^^^^^^^^^^^^^^^^^
>
>  It looks to me like you're running xterm with a UTF-8 encoding, but your
>encoding is set to use the ISO-8859-15 charset.  I get screen corruption
>too if I do this.  What do you get if you run either
>
>    LC_ALL=en_US.UTF-8 aptitude
>
>  or use a plain xterm?


With these settings I cannot reproduce it:

  LANG=en_GB.UTF-8
  LANGUAGE=en_GB:en

With "LANG=en_US.ISO-8859-15" I get things like these, that don't look
good, but no shortening of lines in the widget box as with your
screenshot:

  - Thanks to Fran??ois-R??gis Vuillemin.
  ...
  * Added patch from Fr??d??ric Bri??re to fix spurious "option space
    agent does

I wonder if it could be also an issue with the changelog not being
encoded in utf-8, while now it is.

Maybe in reality this is a bug and ideally all combinations of should
work, I am not well versed on these matters.  However, reallistically, I
think that UTF-8 was invented with the idea that people use this
encoding universally and to get rid of this kind of issues.

This is also a release goal: https://wiki.debian.org/ReleaseGoals/utf-8

So I am not sure if we should do anything else about this bug.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>