On Thu, Mar 21, 2002 at 07:45:11PM +0100, Petter Reinholdtsen wrote: > [Matt Kraai] > > Does this actually work with pointerize? If not, could we just use > > the first locale in the list, since it should always be valid? > > I'm not sure what pointerize is. $ apt-cache show pointerize Package: pointerize Priority: optional Section: devel Installed-Size: 120 Maintainer: Enrique Zanardi <ezanard@debian.org> Architecture: powerpc Version: 0.5 Depends: libc6-dev, gettext Filename: pool/main/p/pointerize/pointerize_0.5_powerpc.deb Size: 20568 MD5sum: 9b5cee445e3566911e4122acc90915e6 Description: Internationalization utilities, based on gettext pointerize is a set of tools used to generate message catalogs from a set of specially formated C source files. Those message catalogs are loaded at run-time, making it possible to have one binary that displays messages in several languages. . It's based on gettext, but it makes smaller binary message catalogs (a must when one is making internationalized boot floppies). The programmer may use his gettexttified C source files just applying one small change to the main() function. The translator will work with the well known PO format. Nevermind. I'm pretty sure your code will work with it. I don't understand the need for fall back languages on the boot-floppies, however. > (Btw: the content of the LANGUAGE variable is not locales but language > codes). My bad. Like I said, my knowledge of i18n and l10n is sorely lacking. Matt
Attachment:
pgp9lsBF0FL9J.pgp
Description: PGP signature