Set encoding via Escape sequence
Submitted by Mathias Hasselmann (IRC: tbf)
Link to original bug (#332147)
Description
If you use Secure Shell for working on remote hosts it happens quite often, that the remote host uses a different character encoding, than your local machine (think for instance of ISO-8859-1 vs. UTF-8). To address that issue vte supports switching of the terminal encoding on the fly (in GNOME Terminal exposed via the menu entry "Terminal -> Set Character Encoding -> ...").
It's a really nice feature - unfortunatly is is far to inconvenient for beeing used - most of the time I end up accepting garbage in my screen, instead of using to that menu. Well, but recently I came up with an idea how to work arround that issue: Why not implement a special Escape sequence recognized by vte causing the terminal encoding getting switched. Once that sequence exists, I'd just patch my profile scripts on the remote machines to emit that sequence on login - and voilá: "Set Character Encoding" finally would become usefull.
When raising that issue on #gnome-hackers some time ago, it was mentioned, that ISO-2022 would provide a mechanism for that switch - but everything I've found just where sequences for toggling interpretation of the lower seven character bits . Maybe the relevant sequences just aren't implemented in vte, so if someone knows the relevant ISO-2022 sequences, an implementation of this feature request should be implemented upon that set of sequences. Otherwise we'd have to invent our very own GNOME- or Freedesktopism.
Btw: If that feature request gets accepted, I'd feel happy to implement it - don't try to steal your time. ;-) Just need to know, which Escape sequences to use.
Version: 0.11.x
Resolution: RESOLVED DUPLICATE