GNU nano - Bugs: bug #40059, Please --enable-utf8 by default
You are not allowed to post comments on this tracker with your current authentication level.
bug #40059: Please --enable-utf8 by default
Submitter: | Egmont Koblinger <egmont> | ||
Submitted: | Wed 18 Sep 2013 02:46:26 PM UTC | ||
Severity: | 3 - Normal | Status: | Works For Me |
Assigned to: | bens | Open/Closed: | Closed |
Wed 25 Sep 2013 02:55:42 PM UTC, comment #4: |
Egmont Koblinger <egmont> |
Wed 25 Sep 2013 02:41:24 PM UTC, comment #3: Well, 2.3.2 should behave the same as SVN. Maybe you are building nano in a non-URF-8 environment and does it therefore choose to not enable UTF-8? During a ./configure run, this line passes here:
|
Benno Schulenberg <bens> |
Wed 25 Sep 2013 12:33:26 PM UTC, comment #2: I was trying the newest devel tarball (2.3.2). Glad to hear that it's already modified in svn, thanks and sorry for bothering! |
Egmont Koblinger <egmont> |
Tue 24 Sep 2013 08:16:15 PM UTC, comment #1: What version of nano are you referring to? Current svn, when built with a bare « ./autogen.sh && ./configure && make » gives a nano which is UTF-8 enabled:
|
Benno Schulenberg <bens> |
Wed 18 Sep 2013 02:46:26 PM UTC, original submission:
Please make the configure script enable utf8 by default, and disable on explicit demand.
|
Egmont Koblinger <egmont> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-02-13 | bens | Status | None | Works For Me | |
Assigned to | None | bens | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-758e.
Corresponding source code
Investigating a bit, and thinking back what happened, I think the story is:
I didn't have ncursesw headers installed. I compiled nano but didn't notice the big fat warning that configure printed. I was surprised to see that it didn't have UTF-8 support.
So I checked "./configure --help" and saw "--enable-utf8" listed there, unlike many other options that are listed as "--disable-foo". This made me suggest that UTF-8 was off by default and I had to turn it on.
Of course, after turning it on I got an error message about missing headers, I installed them and then everything went on fine.