bugGNU Screen - Bugs: bug #27586, broken support for unicode plane 1


bug #27586: broken support for unicode plane 1

Submitted by:  Arc Riley <arcx>
Submitted on:  Sat Oct 3 05:12:52 2009  
Category: Program LogicSeverity: 3 - Normal
Priority: 5 - NormalStatus: None
Privacy: PublicAssigned to: None
Open/Closed: OpenRelease: 4.0.3
Fixed Release: NonePlanned Release: None
Work Required: None

Add a New Comment (Rich MarkupRich Markup):

You are not logged in

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


Fri Oct 22 20:52:18 2010, comment #3:

Awesome. Not only is screen broken in this regard, but so is Savannah (it truncated my earlier comment).

Here it is again, reproduced entirely in ASCII.

I just ran into this issue, so I tried out the unicode++ branch.

Sure enough, code points such as <U+26ED9> come out correctly, and they seem to work in copy+paste, scrollback, writebuf, etc.

However, there are problems with the language tag characters (U+E0000 through U+E007F, as they get mangled by screen. For example, if I output the text,


screen turns it into a bunch of garbage that mutates as you scroll or move the copy cursor around. The results differ every time the text is output, too. This text disrupts screen's notion of where lines start and end: after printing this text, the copy mode cursor does not appear on the line that is actually being copied.

Nick Bowler <draconx>
Fri Oct 22 20:49:05 2010, comment #2:

I just ran into this issue, so I tried out the unicode++ branch.

Sure enough, code points such as <U+26ED9> (

Nick Bowler <draconx>
Fri Mar 5 10:34:32 2010, comment #1:

The 'unicode++' branch in the official repository [1] should now support plane-1 unicode stuff. Using this branch, I can visit, for example, http://www.code2000.net/oneplane.htm, and the characters do not show up as '?' any more.

If you (or anyone) could try it out, that'd be great. If someone's testing, please also test copy/paste from the scrollback, writebuf, hardcopy etc. commands.

[1] http://git.savannah.gnu.org/gitweb/?p=screen.git;a=shortlog;h=refs/heads/unicode%2B%2B

Sadrul Habib Chowdhury <sadrul>
Project Administrator
Sat Oct 3 05:12:52 2009, original submission:

I have my locale and screen setup properly for en_US.UTF-8

Unicode characters below uffff appear fine, while unicode characters above u10000 appear as a ?.

The same unicode characters work fine outside of screen in the same terminal.

Arc Riley <arcx>


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

Attach File(s):

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 inimino
  • -unavailable- added by draconx (Posted a comment)
  • -unavailable- added by sadrul (Posted a comment)
  • -unavailable- added by arcx (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 Jun 23 04:42:55 2011iniminoCarbon-Copy-=>Added inimino
    Fri Oct 22 20:53:20 2010draconxCarbon-CopyRemoved -unavailable-=>-
    Fri Oct 22 20:49:05 2010draconxCarbon-Copy-=>Added -unavailable-

    Back to the top

    Powered by Savane 3.1-cleanup1