Bug 101856 - nano does not support unicode (UTF-8)
Summary: nano does not support unicode (UTF-8)
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: nano   
(Show other bugs)
Version: beta1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Woodhouse
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-08-07 18:24 UTC by Mikko Paananen
Modified: 2007-04-18 16:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-25 16:34:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Mikko Paananen 2003-08-07 18:24:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030601
Mozilla Firebird/0.6

Description of problem:
Nano cannot display or edit UTF-8 coded text properly.

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

How reproducible:

Steps to Reproduce:
1. Install nano from Severn beta
2. Type in some text using extended ascii characters
3. Use backspace to delete typed characters

Actual Results:  Backspace only deletes last byte of multibyte UTF-8 character,
so last character on line gets corrupted to invalid UTF-8 sequence (shown as
square). Also line length is calculated using byte count, not character count so
cursor moves to right after last character on line when refreshing screen.

Expected Results:  Typed characters should be deleted.

Additional info:

Ok, this is problematic, unicode support for nano is only on design stage and
implemented in version 1.3. There are several patches floating around that give
some support for UTF-8 but those have not been accepted upstream.

I understand that nano replaces pico that was removed from RHL as "simple" text
editor, but in current stage nano cannot be used to, say write mail in any other
language than english. It still might be useful to edit some config files or
similar where only US-ASCII is used.

Comment 1 David Woodhouse 2004-08-25 16:34:01 UTC
I don't think I'm supposed to ship a development version of nano -- we
need to wait until 1.4 is released. I'll close this 'UPSTREAM' for now
-- please remind me if necessary when nano 1.4 is released.

If there's a backport of the UTF-8 support I suppose we could consider
applying that?

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