Base POSIX leaves the handling of backslahes in the operand implementation defined. The XSI extension specifies several escape sequences, like e.g. \n, which shall be transformed upon printing. Originally make_pot.sh expected XSI behaviour and indeed e.g. dash’s echo builtin implements this. echo builtins of other common shells such as bash however, do not (by default). Avoid this portability pitfall by just using printf at all relevant places. See: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/echo.html https://pubs.opengroup.org/onlinepubs/9699919799/utilities/printf.html This also allows us to stop substituting each backslash with multiple backslashes before piping to maybe_append. This substituion existed to safely pass backslahes through maybe_append’s echo'ing. As a bonus also improve quoting. Prior commits, especially 0fbcaea 4aee271 940181c already tried to fix this and adjusted various parts to better work with the shell at hand. The second listed commit even proclaimed it would make the script POSIX compliant. This was not actually true, since I left several instances of echo in place and forgot to adjust the amount of backslash escaping. The latter was fixed (for XSI shells) in the third commit. While I’ll refrain from bold claims like "POSIX compliance" this time, I can attest the new version gives identical results between dash and bash at least. Ported from: arch1t3cht@bc3358f

Commits

Commits on May 1, 2023

Update links in appdata.xml

Use gettext to process AppData file

po/make_pot: increase portability across shells

po: regenerate PO files

po/de: reactivate strings affected by borked escapes

po/de: fix a few errors