Hi,

DH wrote:
> It took some tweaking to get the XS version to compile,

Reporting success or failure for patched CPAN packages to the official CPAN
testers database is somewhat confusing to other users.  Is there any way to
remove the test report from the database?

The right place for your failure report would have been
http://rt.cpan.org/NoAuth/Bugs.html?Dist=libintl-perl where you can report
bugs/feature requests.

> besides messing with include/lib paths, I commented out all mention of
> _nl_msg_cat_cntr
> _nl_domain_bindings
> in the test case, and  added #include <libintl.h> to gettext_xs.xs

The tests for the internal symbols _nl_.* had been included to prevent
attempts to compile the XS version under non-GNU systems. ;-)

Before you frown on that: This hack was suggested and recommended by Bruno
Haible, the maintainer of libiconv and gettext. ;-)

> I'm using libiconv-1.9 and gettext-0.12

I have endeavored to build libiconv 1.9.1 and gettext 0.13 with Microsoft
Visual C, and despite the test failures, things seem to work basically here.
The main problem seems to be, that the test scripts assume a slash as the
path separator (and so does libintl-perl internally).  This works fine with
the pure Perl version, but loses when external native libraries like gettext
are getting involved.

I will come back to the problem, but I cannot tell you how long this will
take.  Until then: The pure Perl emulation of GNU gettext works alright under
Windows, and under normal circumstances you will not really slow down your
programs by using the Perl version.

Ciao

Guido
--
Imperia AG, Development
Leyboldstr. 10 - D-50354 Hürth - http://www.imperia.net/