bug#44155: Print integers as characters

[Eli Zaretskii]

> From: Juri Linkov <juri@linkov.net>
> Cc: rgm@gnu.org,  44155@debbugs.gnu.org,  schwab@linux-m68k.org
> Date: Sun, 01 Nov 2020 21:13:03 +0200
> 
> >> >>         if (EQ (Vinteger_output_format, Qt) && CHARACTERP (obj)
> >> >> -           && (c = XFIXNUM (obj)))
> >> >> +           && (c = XFIXNUM (obj)) && ! CHAR_BYTE8_P (c))
> >> >
> >> > If a test fails, it is better to fix the test and not make the code
> >> > less powerful, don't you agree?
> >> 
> >> This means sweeping the problems under the carpet.
> >
> > Which problem?
> 
> Problem of ambiguous numbers 128 and 4194176 that are both printed as ?\200.

Octal escapes are generally a sign of a raw byte.  This is not
different from buffer display -- how do you know what does ?\200 mean
inside buffer text?

> ?\200 and 128 are two forms of the same character too.

See my question above.  I don't think what you say is true.