Hi

On 9/15/19 3:06 PM, Ingo Schwarze wrote:
Hi Jean-Michel,

BESSOT Jean-Michel wrote on Sun, Sep 15, 2019 at 02:08:32PM +0200:

jeanmi@x1:~ $ uniname utf8.txt
Good, so we have confirmed that you indeed have properly encoded UTF-8.

The problem is when I paste the content of the xterm output it get back
to the good characters I don't see this when I make a cat output.txt.
I'm not sure i understand this sentence.

Is this what you mean:

  1. If you do "cat utf8.txt", the output looks like garbage.
  2. If you cut and paste that garbage, what gets pasted is the

original, correctly UTF-8-encoded text.

If that is what you mean, that does sound like an xterm(1) display
problem, possibly due to some misconfiguration.


This is what i mean

I did look at the configuration I didn't touch since years and there is
no utf8 entry.
.Xdefault:
*background:white
*font:-*-terminus-medium-*-*-*-24-*-*-*-*-*-*-*
That line is strange, it doesn't work for me:

    $ xterm -fn '-*-terminus-medium-*-*-*-24-*-*-*-*-*-*-*'
   xterm: cannot load font "-*-terminus-medium-*-*-*-24-*-*-*-*-*-*-*"

It doesn't break anything for me either, though.
The xterm started with the above command works.

Try deleting that line.  Does that change anything?

!Settings by software
XTerm*loginShell:true
XTerm*ScrollBar:false
XTerm*font:-*-terminus-medium-*-*-*-24-*-*-*-*-*-*-*
Delete this line, too.

UXTerm*loginShell:true
UXTerm*ScrollBar:false
UXTerm*font:-*-terminus-medium-*-*-*-24-*-*-*-*-*-*-*
I deleted the line, reloaded the config and it change nothing except the font.
The UXTerm wrapper was deleted long ago, so these three lines no longer
have any effect.  Delete them, too.

In general, when debugging weird problems, try to disable all your
customizations and reproduce with default settings.  If it still
breaks, you produce a better report.  If it works with the defaults,
consider what each of your customizations is supposed to do, and if
you want that, add them back in one by one, checking that each one
actually does what you want it to do.

I don't know what I can make to explain the problem better, it is just
in the displaying in xterm the utf8 characters it get wrong,
It was a good idea to describe the problem in words rather than post
images.  But in this case, a screenshot of how the result of
"cat utf8.txt" looks like might help.  Can you upload that somewhere
and post a URI?

I did take a screenshot of the uniname output, it is more talkative to see a theta in place of an eacute .

The picture: https://tof.cx/image/qql3Fithe picture:


And please, keep the list in Cc: when asking questions.  That way,
you have better chances that somebody understands and can help you
and you put less pressure on an individual developer.
ok
Yours,
   Ingo
byek

Reply via email to