Ticket #674 (closed defect: invalid)

Opened 11 years ago

Last modified 9 years ago

alpine renders html non-breaking space incorrectly

Reported by: jweiss Owned by:
Priority: trivial Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

It appears that when alpine renders an html message that contains a non-breaking-space, that character is rendered as a capital-A with a caret over it. I'm guessing this will need to be up-streamed, but figured that there might be some charset issue that I'm missing or something,

Change History

comment:1 Changed 11 years ago by geofft

What terminal are you using? This looks like a classic terminal-isn't-UTF-8 bug -- is this with a local terminal on a Debathena machine, or SSH'd in from somewhere?

Do the instructions at  http://utf-8.scripts.mit.edu/ help any?

comment:2 Changed 11 years ago by andersk

==geofft. I tested and it works fine for me in Alpine 1.10 and 2.00.

comment:3 Changed 11 years ago by jweiss

I'm ssh'd in from an RHEL 4 (Athena 9.4) box at the moment. Things also fail from an Athena 9.4 sun, but I suppose that's less surprising. The aforementioned instructions do not help. Is there a way to tell alpine not to use UTF-8 (other than telling it to prefer-text in the Viewer-Options configuration? I'll note that the problem does go away if I launch an xterm on the DebAthena? box that is tunneled through my ssh connection, just not if I launch alpine in the ssh window itself.

comment:4 Changed 11 years ago by andersk

UTF-8 works fine out-of-the-box on RHEL 4 and Athena 9.4 Linux, unless you changed something.

In what terminal are you running ssh? If your local terminal is also xterm, if you Ctrl+Right-click on it, is UTF-8 checked? What is the output of locale (outside and inside ssh), and what’s in /etc/sysconfig/i18n?

comment:5 Changed 11 years ago by jweiss

It's possible that some xresource I've had for a decade or more is biting me here. Indeed, UTF-8 is not checked in the C-right menu, and checking it solves my problem. I am still curious whether there's a way to tell pine not to use UTF-8. Thanks for the help.

comment:6 Changed 9 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to invalid
Note: See TracTickets for help on using tickets.