[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gettext problems
From: |
Patrice Dumas |
Subject: |
Re: gettext problems |
Date: |
Fri, 4 Aug 2023 11:33:38 +0200 |
On Fri, Aug 04, 2023 at 10:03:22AM +0100, Gavin Smith wrote:
> On Fri, Aug 04, 2023 at 08:06:44AM +0000, 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 first bad commit
>
> Thanks for investigating this. I have reverted the changes in a recent
> commit, and confirmed that this fixes the problem.
>
> "make check" still runs fine, and looking at the ChangeLog I didn't see
> other commits that obviously depended on this one, so hopefully it makes
> sense to revert this change in isolation.
It does, nothing should depend on it.
> 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 change. I re-reverted, fixed, merged the two
changes in one commit and reapplied in
1a21355dd1b50a796e35d9fc55c76b94424b126e
I can re-re-revert, split in two and re-apply separately, if needed.
I will redo a proper Changelog entry, but first wait to see if I
rererevert and split before doing it.
--
Pat