Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=481750
--- Comment #9 from Mamoru Tasaka mtasaka@ioa.s.u-tokyo.ac.jp 2009-02-02 02:54:28 EDT --- To make this bug more clearer:
* As I said in comment 0 Japanese man pages for bash need fixing. I am not saying that bash binary should be fixed.
* What became critical now is that Japanese bash man page says that *in* posix mode source command _does_ search current path.
This was not a problem on bash 3.x, because - In English bash man page, there was (and also is) no mention about how source behaves *in* posix mode for current path English bash man page explains how source behaves in *non*-posix mode only - And actually sh 3.x searched current path *in* posix mode
But with bash 4.x, in posix mode sh no longer searches current path - This behavior is "correct" because English man page does not say anything how source behaves in posix mode for current path - But Japanese man page _does_ say that sh searches current path in posix mode.
So now not only there is misinterpretation on Japanese man page, but also current Japanese man page says what is _against_ what sh in posix mode behaves.