GNU nano - Bugs: bug #52262, Gnome Terminal shows some...
You are not allowed to post comments on this tracker with your current authentication level.
bug #52262: Gnome Terminal shows some single-width characters as double-width
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Sun 22 Oct 2017 06:00:58 PM UTC | ||
Severity: | 3 - Normal | Status: | Invalid |
Assigned to: | None | Open/Closed: | Closed |
Sat 04 Nov 2017 06:38:11 PM UTC, comment #2: |
Benno Schulenberg <bens> |
Fri 03 Nov 2017 07:58:56 PM UTC, comment #1: Apparently you've enabled Profile Preferences -> Compatibility -> Ambiguous-width characters: Wide.
|
Egmont Koblinger <egmont> |
Sun 22 Oct 2017 06:00:58 PM UTC, original submission:
When running nano from git on Linux Mint 18 (Sarah, based on Ubuntu 16.04, Xenial) and in a Dutch locale, and then typing ^G and paging down to where the cursor commands are (the left and right triangles, etcetera), then this is what I see:
|
Benno Schulenberg <bens> |
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 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-11-13 | bens | Open/Closed | Open | Closed | |
2017-11-04 | bens | Status | None | Invalid |
Powered by Savane 3.13-3230.
Corresponding source code
Aah! Yes, that was it. I remember trying to get the "code-block" characters (the rectangular things with a six-digit hexadecimal code in them that are displayed for unassigned codepoints or when the font doesn't provide a glyph) to occopy two columns instead of one. This was on a tertiary partition of an old machine that I sometimes use to test nano on. I apparently forgot to restore the default setting. :|
Thanks for clearing this up, Egmont.
(I've read a bit in http://www.unicode.org/reports/tr11/, and the reason that é and such are marked as ambiguous seems to be that in some East Asian legacy character sets those characters were fullwidth ("two columns"). When used in Unicode, however, they should only be rendered as fullwidth when they are used in an East Asian context -- so certainly not when in a Dutch locale and when most of the surrounding characters are plain ASCII.)