[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: consistent line wrapping from msgattrib
From: |
Bruno Haible |
Subject: |
Re: consistent line wrapping from msgattrib |
Date: |
Thu, 20 Jul 2023 15:25:34 +0200 |
Hi,
Sandro Santilli wrote:
> I'm trying to avoid style wars between developers but cannot find a
> way to make .pot and .po files line wrapping consistent across
> machines, despite all machines having the same gettext version.
>
> What affects this operation turning the --width switch of msgattrib
> not consistent ? Is it a bug or am I missing something ?
The precise wrapping behaviour depends on the version of GNU libunistring
in use. "In use" means:
- if msgattrib is dynamically linked against libunistring
(see "ldd msgattrib"), that version of libunistring.so,
- if not, then the version of libunistring that was partially included
in the GNU gettext source code.
So, there are 4 scenarious in which the same gettext version on different
machines may behave differently:
- msgattrib is linked against a libunistring.so on both machines,
and a new version of libunistring was installed on one of the two machines
but not both.
- msgattrib is linked against a libunistring.so on one of the machines,
and a new version of libunistring was installed on this machine later.
- msgattrib is linked against a libunistring.so on both machines,
and they use different versions, and due to a bug in gettext's build
process the installed libunistring.so was used instead of the
sources included in the GNU gettext source code.
- msgattrib is linked against a libunistring.so on one of the machines,
and on this machine, due to a bug in gettext's build process the installed
libunistring.so was used instead of the sources included in the GNU gettext
source code.
If you don't require that the PO files be directly editable by a
translator, you can just use the option --no-wrap.
Bruno