Date: Sat, 26 Jul 2014 16:02:24 -0400 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Locale system ready for testing As of commit c5b8f1930512d206a7c1cf1093a4a47e1722a414, it should be possible to start testing the locale system and developing translation files. By default no locale files are loaded; the MUSL_LOCPATH environment variable must be set to a colon-delimited list of directories to search for locale files. Locale files are in .mo format, the format generated by gettext msgfmt. Note that as of right now, gettext-tiny from the sabotage repo does not generate valid .mo files and cannot be used in place of the GNU msgfmt; I hope we can get this fixed quickly. There's no list of strings to be translated yet, but they can generally be found in the source for strerror and similar functions (see the above commit) and in src/locale/langinfo.c. I'm not sure what best practice is for making this easy for translators; perhaps there should be a dummy .po file for the C locale that translates all translatable strings to themselves, and it should be maintained with the libc source rather than separately? Note that the gettext family of functions are still stubs, so while libc message translations should work, applications will not get their own translations unless they use their own out-of-libc version of gettext. I'll work on correcting this soon but since the documentation on gettext is sparse (e.g. I don't know how the pgettext contexts translate into the string for lookup) it's somewhat nontrivial. Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.