Thursday, November 30, 2017

Re: xterm(1) changing UTF-8 characters when copy-pasting?

Hi Ingo,

Ingo Schwarze writes:
> Except in a professional typesetting system like groff or LaTeX, i
> consider anything that makes the end user worry about fonts
> fundamentally broken.

I think everybody's in agreement that xterm is broken and wrong here.

> Fonts that work should be installed by default
> and not configurable, in my opinion. Toying around with fonts
> causes nothing but grief.

You'll need extra fonts once I finish my patch to add situationally
appropriate emoji to all our manpages.

> +*precompose: false

Sure.

> +*VT100.utf8: 1

xterm(1):
This option and the utf8 resource are overridden by the -lc and
-en options and locale resource.

We set the locale resource, so this appears redundant.

> +*VT100.font2: -misc-fixed-medium-r-normal--8-80-75-75-c-50-iso10646-1
> +*VT100.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646
> -1
> +*VT100.font3: -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1
> +*VT100.font4: -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1
> +*VT100.font5: -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
> +*VT100.font6: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1

These are already the default according to appres(1).

--
Anthony J. Bentley

No comments:

Post a Comment