Bug 121135 - Add Encoding selection to Session configuration dialog
Summary: Add Encoding selection to Session configuration dialog
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-01 09:38 UTC by Sebastian Frei
Modified: 2007-12-16 07:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Frei 2006-02-01 09:38:04 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc-4.0.2 
OS:                Linux

I have a utf8 enabled system, so if I use konsole for a local session, I need utf8 encoding. This works, e.g. midnight command display everything correctly.

But some remote systems I log into, are not utf8 enabled. Konsole always selects the default encoding (utf8) for these sessions, midnight commander and ls output is displayed faulty. I have to change the encoding everytime manually to iso 8859-1 for those sessions.

It would be very helpful, if I could set the encoding on a per session basis to utf8 for the local sessions, and to iso 8859-1 for the remote sessions. Like it is done already with the colour scheme, the font type, the icon, ... .
Comment 1 Kurt Hindenburg 2006-02-02 19:00:39 UTC
This is possible in KDE 3.5.x.  Change the encoding via the menu items...

# Check encoding via DCOP; note DCOP setEncoding doesn't currently work.
% dcop konsole-8503 session-4 encoding
UTF-8
% dcop konsole-8503 session-5 encoding
CP 1255

The encoding is also saved in the session managment...

This what you wanted?
Comment 2 Sebastian Frei 2006-02-03 09:06:11 UTC
This is not exactly what I want. I want to have an additional "Encoding" box in the Settings->Configure Konsole->Session dialog, like the Font, $TERM, Keytab, Schema boxes.

What you described is possible, but has some drawbacks. With this method I can open all my different connections, set the right encoding option and save a profile. If I start console now via kicker->Terminalsessions->New session using profile->XXXXX I get a konsole with all connections and the right encoding settings.

But starting a single console for example via kicker->Terminalsessions->University the encoding is set to default, not ISO-8859-1.

Also if I have a konsole running, and want to add a new connection to my university server (non-utf8) I usually just click on File/University and it opens. But the encoding setting is set to default too.

This can't work with a profile, at least I don't know how to do it. It has to be saved on a per session basis, like the icon, $TERM,...
Comment 3 András 2007-05-25 16:09:54 UTC
I use this workaround for my remote sessions:

In Konsole > Settings menu > Configure Konsole > Session put the following line to the 'Execute' row:
dcop $KONSOLE_DCOP_SESSION setEncoding 'iso 8859-1' && ssh -Y user@remote.machine

And everything will be funky, no manual settings needed from now on.
Comment 4 Robert Knight 2007-12-16 07:45:01 UTC
Fixed in KDE 4.  There is a "Default Character Encoding" option which can be set on a per profile basis.

It can be accessed as follows:

1.  Go to Settings -> Manage Profile
2.  Select the Profile you wish to change and click "Edit Profile"
3.  Go the the Advanced tab 
4.  Change the 'Default character encoding' option at the bottom.
5.  Click OK.