Christian Ohm <chr....@gmx.net> wrote: > On Saturday, 30 January 2010 at 18:37, Siegfried-Angel Gevatter Pujals wrote: >> I am sorry I didn't reply to this before. I had some difficulties with >> it and it ended slipping out of radar. >> >> Basically what I did to get Vilistextum to compile with multibyte is >> adding a build-dependency on "locales-all" and adding the following >> line to debian/rules: >> DEB_CONFIGURE_EXTRA_FLAGS = --enable-multibyte >> --with-unicode-locale=en_US.utf8 >> >> However, the resulting package wouldn't work on my system (running >> vilistextum resulted in error message "setlocale failed with: >> en_US.utf8") unless I installed "locales-all" on it. I suppose adding
I downloaded and run the debian-testing-i386-netinst.iso and then dpkg-source -x vilistext_2.6.9-1.dsc cd vilistextum-2.6.9 vim debian/rules and added DEB_CONFIGURE_EXTRA_FLAGS = --enable-multibyte (and in a second test also with --with-unicode-locale=en_US.utf8) dpkg-buildpackage -rfakeroot and installed the deb-file as root. Both versions just worked. >> locales-all as a dependency of the binary package is not the right >> solution, but I don't really know what's going on here or what I'm >> doing wrong. No, adding locales-all surely isn't a solution. But the building of package worked? And compiling it manually with --with-unicode-locale=en_US.utf8 produced a working binary? That sounds strange. What does 'locale -a' and 'fakeroot locale -a' show? I got for both: C en_US.utf8 POSIX >> If you can provide any pointers on how to fix this, or even a patch, >> this would be great. (By the way, if someone out there is really >> interested in this package, I'd be okay with handling over >> maintainance or co-maintainance of it). > > Hello, > > I've compiled it with only --enable-multibyte, and that compiles and runs. If only --enable-multibyte is specified, the configure script should select a utf8 locale by itself. > Needs -u to output UTF8 though, maybe that should be default. That's because the output character set is defined by the input HTML and not the user environment. If there's not character set specified in the HTML file, vilistextum falls back to latin1 for HTML and UTF-8 for XHTML. Bye Patric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
