[Bug 1297051] Re: gnome-terminal doesn't recognise C1 controls

boon derek at colourhorizons.com.au
Tue Aug 5 06:45:02 UTC 2014


On 05/08/14 10:17, Egmont Koblinger wrote:
> ./src/vte-2.91 --encoding=latin1 # or whichever other encoding you 
> wish to use
An additional comment on this ... if I use latin1 encoding then normal 
shell commands like 'man' have glitches in their output, presumably 
because they use Unicode characters and assume, for example, UTF-8 
encoding. If I use utf8 encoding then my remote application does not 
work at all (because the remote application is completely incapable of 
sending UTF-8 encoding).

This is OK for me. I just means that I should use the terminal so that 
it automatically SSHs to the remote system, selecting the correct 
encoding for that system (latin1). That is, I need to have a terminal 
that is dedicated to the session on the remote system, while keeping 
that separate from any terminal that is on my local computer. That is 
all fine for me.

What does not work is to make a terminal, type some local commands, then 
SSH to the remote system - unless I change profile around the SSH. (Of 
course it would be nice if this were automatic.) Strangely, while in the 
released gnome-terminal I can right mouse click and change profile 
dynamically, in the program that I built from source as per your 
instructions, this feature seems to have disappeared. Is there still 
some way of maintaining and selecting profiles?

Regards

Derek

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to vte3 in Ubuntu.
https://bugs.launchpad.net/bugs/1297051

Title:
  gnome-terminal doesn't recognise C1 controls

Status in “vte3” package in Ubuntu:
  New

Bug description:
  gnome-terminal seems not to recognise the C1 control characters.

  The particular character that is a problem for me is CSI. However
  there may be a generic issue with non-support of this whole range of
  characters.

  This range of characters should only be recognised when the encoding
  is a character set that is defined to include the C1 control
  characters but, at a quick look, that is all of the ISO-8859-x
  character sets and Unicode. (C1 control characters require encoding as
  a 2 byte sequence when the encoding is UTF-8. As unlikely as this may
  be to occur in practice, UTF-8 is not inconsistent with C1 control
  characters.)

  Part of the motivation for raising this bug report is that PuTTY seems
  to have declined in reliability recently and so I looked at why I am
  using PuTTY as opposed to gnome-terminal. Correct support of C1
  control characters is one reason. This works in PuTTY. It does not
  appear to work in gnome-terminal. Perhaps resources would be better
  spent making gnome-terminal work as well as PuTTY does, rather than
  attempting to get PuTTY fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Mar 25 11:08:00 2014
  InstallationDate: Installed on 2011-10-25 (881 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to saucy on 2013-11-08 (136 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte3/+bug/1297051/+subscriptions



More information about the foundations-bugs mailing list