Hi Simon, > I'm finally testing this, now that gnulib-l10n is in Debian and libidn2 > is coming closer to a release that could make use of it. I'm happy to > say it is working! This is a nice improvement, it gets the version-etc > translations from the gnulib domain: > > jas@kaka:~/src/libidn2$ LANG=sv_SE.UTF-8 src/idn2 --version|tail -1 > Skrivet av Simon Josefsson, Tim Ruehsen. > jas@kaka:~/src/libidn2$
Nice! > However I wonder if the automatic value of GNULIB_LOCALEDIR is the right > one. It seems to prefer $prefix which results in > > #define GNULIB_LOCALEDIR "/usr/local/share/locale" > > by default, unless I specify --prefix and/or --with-gnulib-prefix. Most people do specify --prefix when running configure: - Distributors use '--prefix=/usr', - Users most often use --prefix=SOME_WRITABLE_DIRECTORY. Only few users don't use --prefix. They quickly realize that having to use 'sudo' for installing the built binaries is cumbersome. > But > I don't think gnulib.mo would never be in $prefix as /usr/local, which > means gnulib translations doesn't work without --with-gnulib-prefix. That is a documentation problem in libidn2. See <https://gitlab.com/libidn/libidn2/-/issues/128>. > Wouldn't it make more sense for GNULIB_LOCALEDIR to default to the > system-wide locale dir rather than the one under prefix? It could. But my vote is for simplicity and for keeping the user empowered. For the latter, - we can use documentation in the DEPENDENCIES file, - './configure --help' lists the available command-line option. Bruno
