> It was the functional change. I re-reverted, fixed, merged the two
> changes in one commit and reapplied in
> 1a21355dd1b50a796e35d9fc55c76b94424b126e
It works now, thanks.
Werner
On Fri, Aug 04, 2023 at 11:33:38AM +0200, Patrice Dumas wrote:
> > Perhaps it will be easier to split this change into a functional change
> > and a change just to move code around. Then it will be more possible to
> > understand which part of it caused the problem.
>
> It was the functional chan
On Fri, Aug 04, 2023 at 10:03:22AM +0100, Gavin Smith wrote:
> On Fri, Aug 04, 2023 at 08:06:44AM +, Werner LEMBERG wrote:
> > After a standard compilation and installation on my openSUSE GNU/Linux
> > box I see latin1-encoded strings on my UTF-8 console.
>
> > Bisecting leads to the following
On Fri, Aug 04, 2023 at 08:06:44AM +, Werner LEMBERG wrote:
> After a standard compilation and installation on my openSUSE GNU/Linux
> box I see latin1-encoded strings on my UTF-8 console.
> Bisecting leads to the following commit:
>
> ```
> afca9f95f8dcca047ad9637b1abe9e4117111e8c is the fir
Hello,
Thanks for the report and analysis. It is due to a missing shift of
set_translations_encoding argument...
Gavin reverted it, I will reapply with the fix.
On Fri, Aug 04, 2023 at 08:06:44AM +, Werner LEMBERG wrote:
>
> [1bc5824f2c4aa1d633d62210f1bc7daa210f620c]
>
> [LANG=en_US.UTF-8
[1bc5824f2c4aa1d633d62210f1bc7daa210f620c]
[LANG=en_US.UTF-8
LANGUAGE=de]
[perl v5.26.1]
After a standard compilation and installation on my openSUSE GNU/Linux
box I see latin1-encoded strings on my UTF-8 console.
```
> makeinfo --help
Aufruf: makeinfo [OPTION]⦠TEXINFO-DATEIâ¦
Ãbersetzt T
