Closed 375gnu closed 11 years ago
I'm sorry but I reject the request.
The rxgettext behavior is more useful rather than xgettext.
po-mode.el that is provided by GNU gettext searches source file relative from where the PO file stands by s
.
http://www.gnu.org/software/gettext/manual/gettext.html#C-Sources-Context
Program source files are usually found relative to where the PO file stands.
If there is any reasonable reason to adjust to the xgettext behavior, I may implement an option to use a directory for base directory.
This bug is originally reported as Debian bug 726946.
I noticed something really weird in rxgettext. It seems that its output .pot file includes location paths relative to the destination directory, rather than to the current working directory!
I am not sure this causes problems with ruby-gettext library, but it sure looks unusual and awkward.
I'll show the issue with my usual test case, described in bug #684182 .
Let's start with the example application in a directory:
Then, let's create a subdirectory:
and create the .pot file with xgettext:
This is OK. Let's try with rxgettext:
Please note that the location paths are "../myapplication.rb", rather than "myapplication.rb". I think that rxgettext should behave like xgettext in this respect.
Please fix this bug and/or forward this bug report upstream. Thanks for your time!