Jens Bauer <[email protected]> writes: > FAIL: lang-bash [...] > -And my bash version (as shipped with Mac OS X 10.5.8): > GNU bash, version 3.2.17(1)-release (powerpc-apple-darwin9.0)
Thanks for the report, but it's a known issue. See the comment in the lang-bash script: # This test fails on MacOS X 10.5 because its 'bash' command is built with # an included intl directory without iconv support; hence it produces wrong # output when accessing any .mo file not generated from a .po file in UTF-8 # encoding. BTW, it's probably good to skip this test if the brokeness can be easily detected at run time, though I have no idea how to do that. Is this still the case on Mac OS X 10.10? > Now, my question is: Will this affect other builds that depend on gettext ? The test failure means that the gettext bash support doesn't work with the Mac OS X's default 'bash' command: http://www.gnu.org/software/gettext/manual/gettext.html#bash So, as long as other builds don't depend on the bash translation feature, I think you don't need to worry about it. Thanks, -- Daiki Ueno
