On 2026-08-28 14:51 -0400, Thomas Dickey wrote:
> On Fri, Aug 28, 2026 at 08:13:55PM +0200, Sven Joachim wrote:
>> On 2026-08-27 20:17 +0000, Debian Bug Tracking System wrote:
>>
>> > Processing commands for [email protected]:
>> >
>> >> tags 687699 fixed-upstream
>> > Bug #687699 [xterm] xterm: screen output is cut off
>> > Bug #751757 [xterm] xterm: installing ca-certificates-java stops output
>> > Added tag(s) fixed-upstream.
>> > Added tag(s) fixed-upstream.
>>
>> Thanks for the new xterm 411 release, but I did not notice an
>> improvement in this regard. The recipe given by the bug submitter still
>> stops output in a non-UTF-8 locale.
>
> fwiw, my (local) commit comment said:
>
> the original report was invalid, as I noted in response. But this
> followup comment showed a problem. That turns out to be a small fix to
> charproc.c, to allow C1 controls to be interpreted _after_ initializing
> wide characters but _after_ turning UTF-8 mode off again.
>
> If starting from POSIX locale as OP did, that can be done with the menu.
> Normally (starting from UTF-8 locale) the menu entry is grayed out, but
> the
> control sequence still works.
I am not sure I understand that. Does "the control sequence" refer to
"ESC % @" which selects the ISO 8859-1 character set?
> I also verified that this is the case for OpenBSD 7.2, in case Ingo or
> Matthieu
> questions it.
I have no idea who Ingo or Matthieu are, but whatever.
In any case I consider what happened to the submitters of
#687699/#751757 rather surprising and undesirable and would prefer to
leave the bug open, even if you consider it invalid. Feel free to tag
it wontfix, though.
Cheers,
Sven
