On Wed, 03 Oct 2001, ESR wrote:
Just I as expected, the attempt to build fetchmail.pot at distribution
time triggered yet another obscure and fatal bug in the festering pile
of rancid dog vomit that is GNU gettext (that's with the latest
version installed, too).
Or in the absurd mess that the fetchmail makefiles are (INCLUDING the
gettext stuff in them)... I am more afraid of touching the makefiles
than trying to get the stuff under intl/ and po/ to work :(
Our makefiles and configure stuff for gettext have been different for quite
a while now, and I've had no problems to get the .pot to build using my
version of the makefiles and the gettext in Debian, other than the fact that
it reordered all the stuff inside the .po files, creating a very huge diff.
I've had it. I'm done. At this point I am planning to remove
gettext support in the next release. I have left it in this release
only because I wanted to get the buffer-overflow guard code out quickly.
Not again :( ARGH. Eric, I can maintain the gettext stuff for you. As long
as you do not mind using --with-included-gettext yourself when building
fetchmail, that should reduce your gettext problems to nearly nothing.
The only problem is that to fully take over gettext-in-fetchmail
maintenance, I'd also need to somehow override the m4 macros your system
uses when you run aclocal, but that should not be too dificult.
Please do not remove the i18n support. People whose native language is
English almost always understimate the need, and value of i18n... How would
you deal with software in Finish, Portuguese or, say, Turkish?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh