GNU nano - Bugs: bug #38888, [Request] add the ability to...
You are not allowed to post comments on this tracker with your current authentication level.
bug #38888: [Request] add the ability to handle UTF-16 encoded files
Submitter: | None | ||
Submitted: | Sat 04 May 2013 05:38:05 PM UTC | ||
Severity: | 1 - Wish | Status: | Wont Fix |
Assigned to: | None | Open/Closed: | Closed |
Fri 24 Feb 2017 12:12:25 PM UTC, comment #4: |
Benno Schulenberg <bens> |
Mon 02 Sep 2013 10:38:17 PM UTC, comment #3: My apologies, but I have not had the time to get a fix for this to work. I'm not going to be doing any more work on nano for the time being.
|
Bob Hogg <rwhogg> |
Tue 18 Jun 2013 12:38:11 PM UTC, comment #2: Based on a cursory source code reading, it appears that nano only specifically supports UTF-8. However, adding support for UTF-16 might not be too difficult. I'll try and add support for it myself over the next few weeks, and if it works I can send you a patch or something. No promises that I'll be able to get it to work though. |
Bob Hogg <rwhogg> |
Sat 04 May 2013 05:40:02 PM UTC, comment #1: This is for nano 2.2.6. |
Anonymous |
Sat 04 May 2013 05:38:05 PM UTC, original submission:
Nano can't read UTF-16 encoded files, shows garbage. Such a file is attached to this bug report. |
Anonymous |
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 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-02-24 | bens | Status | None | Wont Fix | |
Open/Closed | Open | Closed | |||
2015-04-24 | bens | Severity | 3 - Normal | 1 - Wish | |
Summary | can\'t read UTF-16 encoded files | [Request] add the ability to handle UTF-16 encoded files | |||
2014-02-19 | dennisd | Carbon-Copy | - | Added dennisd | |
2013-05-04 | None | Attached File | - | Added local_settings.txt, #28017 |
Powered by Savane 3.13-f8d8.
Corresponding source code
Meanwhile nano's source code has been streamlined by using some knowledge of UTF-8. Making it work for UTF-16 too will be too hard. The only possibility would be to convert UTF-16 to UTF-8 upon reading and saving a file. But you could probably make a little script, say n16.sh, that does the conversion before feeding it to nano, and converting the result back.