On 07/14/2010 01:40 PM, Matthias Clasen wrote: This happened whenever routine 'terminal-encoding.c' option had been commented out of the encoding menu possibilities. This was done without any comment in the code of the actual reason why this had been done or what replaced it functionality. <snip> static const struct { const char *charset; const char *name; } encodings[] = { // { "UTF-8", N_("Current Locale") }, <--- !!!!! { "ISO-8859-1", N_("Western") }, { "ISO-8859-2", N_("Central European") }, { "ISO-8859-3", N_("South European") }, <snip> This appears to disallow the setting of the terminal encoding depending on the locale setting which allows the character encoding to be set from the command-line and forces the end user to resort to always having to point and click to choose encoding instead of doing for example. . . . "env LC_CTYPE=is_IS.iso88591 gnome-terminal -e 'slogin host1'" Which sets the encoding to whatever the locale specifies if gnome-terminal 'Character Encoding' is set to 'Current Locale' and in this case host1 is using iso88591 charset. env LC_CTYPE=is_IS.utf8 gnome-terminal -e 'slogin host2' if host2 is using utf8. Or simply be doing 'gnome-terminal --characerencoding=xxxxx' where xxxxx is an encoding from the available set. JBG

On 07/15/2010 01:27 PM, Matthias Clasen wrote: Neither have you answered any of mine but git will tell you when the code was changed and in what Fedora release that change ended up in as it will tell me why is what I could have responded with if I wanted to sink to your level of response. Anyway since Gnome-Terminal 2.23 I believe which probably was F9 and earlier release and it does not work in current ( F13 ). You don't actually start to notice the usefulness ( and the lack ) of having this ( and the nuance and headache that comes with the point and click ) until you start to work in a multi encoded/locale Environment ( yes this is an old nugget stored in a file and pulled fourth when needed again ). So the end it's not a matter of when, why or who changed this ( Let's just assume it was done for a very good reason ) but more if there is another now preferred method were I can achieve same/similar functionality in the examples I showed earlier, in Gnome terminal today ( which hopefully works in future releases ) without having to resulting to point and click only alternative. JBG

On 07/15/2010 05:05 PM, Jesse Keating wrote: AFAIK Nobody is being hostile here. It's just the way we communicate. I was expecting an answer something on the lines of.. If we or I can recalled correctly this got removed because of X reason(s). . . Or This got deprecated because y reason(s). . . . Users are expected to do Z now. And you can achieve the same thing by doing this now.. With the following . . . . Hey no problem I'll adjust and adapt .. . . :) Or the opposite We or I ( as in Fedora Gnome Maintainer(s) ) have no clue why this was done and we know of no alternitives/workaround to achive the same or similar thing that was used to do. With the following.. Dam! I just try to not to drive my self mad when dealing with the extra point and click when I run Gnome Terminal. In my infinite wisdom I abandon the ( apparent old ) CLI way of things and tried to go the GUI route which came logically to me which was to create a separated profile in Gnome Terminal and you know try to configuring this per profile. Then I could just start/use Gnome Terminal with various different profiles only to find out you cant and I don't know if that would be considered a bug that you cant configure this per profile since I don't know the real reason why this had to be removed in the first place. JBG

I filed a bug about it upstream. Seems like a regression from a refactoring two years ago. We'll fix it. behdad On 07/15/10 14:02, Jesse Keating wrote: