>if LANG=C LC_ALL=C $FMTUTIL "$@" > $tempfile 2>&1 ; then
That is indeed better, thanks. Committed.
Norbert
--
PREINING Norbert https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13 fp: F7D8 A928 26E3
Hi Norbert
On Monday, 10 October 2022 17:44:56 AEDT Norbert Preining wrote:
> @@ -76,11 +76,14 @@ dhit_build_format ()
> tempfile=$(mktemp -p /tmp fmtutil.)
> # save LANG
> LANGSAVE=$LANG
> +LCALLSAVE=$LCALLSAVE
> LANG=C
> +LC_ALL=C
> printf "Building forma
Hi Stuart,
thanks for testing ... indeed LC_ALL .. so something like this?
@@ -76,11 +76,14 @@ dhit_build_format ()
tempfile=$(mktemp -p /tmp fmtutil.)
# save LANG
LANGSAVE=$LANG
+LCALLSAVE=$LCALLSAVE
LANG=C
+LC_ALL=C
printf "Building format(s) $*.\n\tThis
Hi Norbert,
On Monday, 10 October 2022 16:23:25 AEDT Norbert Preining wrote:
> What happens if you only feed LANG=C? Does it break?
LANG=C seems to make no difference to solving the problem (it's already
protected in the code as you say), likewise LANGUAGE=C makes no difference.
The only other
Hi Stuart,
> The postinst for tex-common is sensitive to the locale settings from the
Hmm, interesting ...
> $ luahbtex -ini -jobname=luahbtex -progname=luahbtex luatex.ini Unable to read environment locale: exit now.
We do set LANG=C already before running fmtutil, so I am surprised that
th
Package: tex-common
Version: 6.17
Severity: normal
X-Debbugs-Cc: stu...@debian.org
Dear Maintainer,
The postinst for tex-common is sensitive to the locale settings from the
environment and so can fail in strange ways. Users can end up with odd
locale settings in a chroot (as I did, where my login
6 matches
Mail list logo
