Hello Colomban,

I thought I was onto something with there being a need to also call vte_terminal_set_encoding, besides running Geany with LANG=C.UTF-8 given in the environment. I have rebuild Geany without the vte_terminal_set_encoding code, and LANG=C.UTF-8 alone gave the expected representation of 'ș' in the Terminal. It results I made a mistake. Sorry for wasting a little time with this non-issue. Also thanks for helping with clarifying the utf-8 behavior in Geany's terminal.

Best Regards, Marius

Here it is my default environment:

$ env | grep -E '^(LC|LANG)' LC_PAPER=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TELEPHONE=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LANG=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LANGUAGE=en_US:en LC_TIME=en_US.UTF-8 LC_NAME=en_US.UTF-8

I start Geany with a Gnu Bash script which exports LANG=C.UTF-8 before running Geany.

-------------------------------------------- On Sun, 10/22/17, Colomban Wendling lists.ban@herbesfolles.org wrote:

Subject: Re: [Geany-Devel] UTF-8 in geany's termina, eg. ș To: "Geany development list" devel@lists.geany.org Date: Sunday, October 22, 2017, 1:25 AM

Hi Marius,

Le 21/10/2017 à 06:49, marius buzea a écrit :

I would like to share a simple use-case

with Geany.  Here it is:  you go to the Geany's terminal and

you list a directory that

contains files with names containing 'ș'.  It may be that instead of 'ș' you see

'??'.

That's very odd, because I've never seen this problem, and use UTF-8 characters occasionally (I'm French and we do have é, è, ê, ô, etc.) and have never ever seen this problem.  I just tested with Geany with LANG=C.UTF-8 and it does work just fine.

You might see a problem if the encoding of one of the locale environment variables is not properly set to UTF-8: e.g. if I set LANG=C (so not specifying the encoding) I do see what you mention; but not if I properly set the encoding using LANG=C.UTF-8.

What is the output of `env | grep -E '^(LC|LANG)'`?  If any of those variables doesn't properly have an encoding set it might be the reason.

Regards, Colomban _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel