bugGNU nano - Bugs: bug #40059, Please --enable-utf8 by default

 
 

bug #40059: Please --enable-utf8 by default

Submitted by:  Egmont Koblinger <egmont>
Submitted on:  Wed 18 Sep 2013 02:46:26 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: NoneStatus: Works For Me
Privacy: PublicAssigned to: Benno Schulenberg <bens>
Open/Closed: ClosedRelease: None

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 25 Sep 2013 02:55:42 PM UTC, comment #4:

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.

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:

checking whether to enable UTF-8 support... auto

For me (in a UTF-8 locale) it results in an UTF-8-enabeld nano.

But in fact I agree that UTF-8 is so standard nowadays that it should be enabled by default, should not be autoconfigured, and should only be disabled when actively --disable-utf8 is chosen.

I would provide a patch, but all this autoconf stuff is muesli to me.

Benno Schulenberg <bens>
Project MemberIn charge of this item.
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:

$ src/nano --version | tail -1
Compiled options: --enable-color --enable-extra --enable-multibuffer --enable-nanorc --enable-utf8

Benno Schulenberg <bens>
Project MemberIn charge of this item.
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.

UTF-8 is the standard character set in pretty much every Linux distribution by now. Supporting it out of the box should be the default by every application, not something special feature that I have to look up how to enable.

Thanks!

Egmont Koblinger <egmont>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by bens (Posted a comment)
  • -unavailable- added by egmont (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 13 Feb 2014 10:24:38 AM UTCbensStatusNone=>Works For Me
      Assigned toNone=>bens
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup