-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
During a package build, I need to produce translated files using
gettext. By this, I mean using the .mo files at build-time to produce
sets of translated PPD files. (I know this is ugly, but it's the only
way to localise static data files.)
This works fine when the locales exist for each localisation, but if
they don't exist, it defaults to C locale/US-ASCII charset. Can the
autobuilders guarantee a full set of generated locales, or is only C
available?
Thanks,
Roger
- --
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848 available on public keyservers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAj6mggoACgkQVcFcaSW/uEh81gCgwjG+MTRoLWh4t0RiiVFMJznE
vpIAoJ2uCt2ny+YzhYJV1JzBVbaafXbT
=WgXD
-----END PGP SIGNATURE-----
