On Tue, Nov 06, 2007 at 08:33:33AM -0600, Eric Sandeen wrote: > Apparently there was some issue with this, once upon a time, which > resulted in our rpms needing to update the po files... I guess I need to > do a bit more code archeology / research. It looks like sct added this > when the pkg updated to 1.36, though there is no comment about why. One potential reason could be that we are using ancient libintl files, and there was some compatibility problem --- although I can't think of a reason that would require updating the po files. I know there is currently an issue on Debian because the po files are getting intstalled in the wrong locations and the gettext shared libraries are looking for them somewhere else, but I only vaguely recall what was going on. I had only enough time to start doing a quick investigation to see why the translation files were getting ignored, and didn't have time to try to fix it. If someone would like to update the po directory and the configure.in hunks for -po to something less antediluvian, patches would be greatly appreciated.... - Ted - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
