2015-06-30 13:30:50 +0200, Vincent Lefevre: [...] > > I don't understand what you mean. > > My point was, applications/systems use different locales. Nothing will > > change that. > > Thus when you process output from a remote application on the local > > system, you must assume that this is happening or assure that the > > expected locale is going to be set remotely as well. > > You should learn how terminals work. When using a terminal, the remote > charmap MUST be the same as the local one (or be a subset), otherwise > the terminal cannot interpret the byte sequences correctly. > > So, if there is no way to tell the remote side what the local charmap > is, then the only possibility is that the remote side uses a charmap > compatible with every other charmap, i.e. US-ASCII. [...]
Or use luit that has been designed for that: >From a UTF-8 terminal: luit -encoding 'ISO 8859-1' ssh host-known-to-use-latin1 Or: ssh -t host luit (assuming luit is installed on host). (unfortunately it doesn't seem to support the /new/ Western Europe charset iso8859-15). -- Stephane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
