Bug 142818 - Nano does not display characters ��� properly
Summary: Nano does not display characters ��� properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: nano
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-14 14:30 UTC by Henrik Karlsson
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version: 1.3.12
Clone Of:
Environment:
Last Closed: 2006-11-11 20:45:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Henrik Karlsson 2004-12-14 14:30:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
When typing characters like ������ in nano the don't appear properly.
Sometimes the characters become empty squares and sometimes they
become other characters.

Version-Release number of selected component (if applicable):
nano-1.2.4-1

How reproducible:
Always

Steps to Reproduce:
1. start nano from a xterm window
2. type ������
3.
    

Actual Results:  �����^�^

Expected Results:  ������

Additional info:

Comment 1 Henrik Karlsson 2004-12-14 14:34:52 UTC
The actual charcters is (html entity format)
åäöÅÄÖ

Comment 2 Matthew Miller 2006-07-10 21:41:21 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 3 John Thacker 2006-11-11 20:45:45 UTC
nano prior to 1.3.12  doesn't properly support Unicode, which causes issues with
FC3.  (http://www.nano-editor.org/dist/v1.3/faq.html#5.3)  You can workaround
this by changing your locale to a non-Unicode one.

FC6 (and RHEL5) have 1.3.12.


Note You need to log in before you can comment on or make changes to this bug.