Opened 18 years ago

Closed 18 years ago

#1827 closed defect (fixed)

nano-1.3.10

Reported by: alexander@… Owned by: dnicholson@…
Priority: normal Milestone: 6.2.0
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

Development version of nano is required for UTF-8 support. Nano-1.3.9 is already present on the LiveCD.

Tested personally by me only when compiled against ncursesw, not S-Lang, although use of S-Lang 2.x is possible.

Change History (7)

comment:1 by dnicholson@…, 18 years ago

Owner: changed from blfs-book@… to dnicholson@…
Status: newassigned

I use nano extensively, and I have a UTF-8 build to test with. I'll get to this soon, after I get a couple other bugs first.

Are there any test cases I should try for locale coverage?

comment:2 by alexander@…, 18 years ago

Test cases:

  • Attempt to start nano in some non-English UTF-8 based locale, as follows:
    LANG=xx_YY.UTF-8 xterm -lc -e nano
    

Here "xterm -lc" is just a known-good terminal. Watch for prematurely-cut or improperly-aligned text in the button captions, etc. The reference rendering can be obtained by running nano in xterm in the corresponding non-UTF-8 locale.

  • Attempt to edit a text file containing one long (60 characters or so) string of different ASCII characters and one string with non-ASCII characters just below. Try moving the cursor in each string with left and right arrows, then between strings with up and down arrows, then delete and re-add some characters in both lines (not in the beginning). Save the file and compare with the original.
  • LANG=ja_JP.UTF-8 yes --help >testfile.txt, then try joining lines and deleting characters from testfile.txt.

comment:3 by dnicholson@…, 18 years ago

Version: a-SVN

comment:4 by dnicholson@…, 18 years ago

OK, I installed nano-1.3.10 and am using it with en_US.UTF-8. So far, everything's good, but I don't have xterm since this is a fairly fresh build and I have to tackle Xorg-7.

Regardless, this is a development version of nano and it looks like there is still quite a bit of development before a stable 1.4 version:

http://lists.gnu.org/archive/html/nano-devel/2006-03/msg00000.html

Possibly this can be added to the Locale Related Issues page in the meantime? Or, I can add a Wiki link on the Nano page and we can put the info there.

comment:5 by alexander@…, 18 years ago

If you object to replacing nano-1.2.5 with 1.3.10, please have both versions in the book and explain the UTF-8 issue either on nano-1.2.5 page or on locale-related issues page, and point readers to nano-1.3.10.

comment:6 by dnicholson@…, 18 years ago

OK. After finally figuring out that my xterm was not using luit (book mistakenly says --with-luit), I now have a proper terminal for locale conversion. The tests above work against ncurses. Haven't tested S-Lang.

I will be adding a link to the Locale Issues page on Nano, and there I'll be adding info about nano-1.3.10 (or possibly .11 http://lists.gnu.org/archive/html/nano-devel/2006-03/msg00006.html).

This is one of my top priorities, so hopefully it should happen soon.

comment:7 by dnicholson@…, 18 years ago

Resolution: fixed
Status: assignedclosed

Fixed in r5860. When version 1.4 becomes stable, I will remove the notes about UTF-8 support from the book.

Note: See TracTickets for help on using tickets.