On Tue, 14 Aug 2001, Byrial Jensen wrote:
Well, gettext, xgettext etc. works fine with \r even though they
complain.
They complain for a good reason. See the gettext docs.
However one problem exists that is not just cosmetic. The messsages
which contain \r are texts which may be mailed to the user by
fetchmail. Fetchmail delivers the e-mails generated by itself in
the same way as it delivers fetched mail. This is a problem when
the translated messages are send by for example SMTP -- the used
charset often has changed from ASCII to something else which is
illegal to send without encoding etc.
A SMTP interface is a SMTP interface. As long as you use the EOL convention
for SMTP, you're on the safe side, and MTAs that screw up on that deserve to
be "deprecated" by force.
I suppose that the best solution is /not/ to handle this in
fetchmail, but to deliver self-generated mail to a MUA which knowns
how to treat messages in the local charset.
No way. Forget it. We already had to file bugs around in Debian to get
programs to stop doing that.
Programs -- even an MTA like fetchmail -- should not deliver
generated mail directly to an MTA.
Please think of the added security problems, as well as the added
reliability problems of using a MUA for that, and tell me just why should we
braindamage fetchmail like that?
No program, *especially* security daemons (which fetchmail isn't,
fortunately :P) is to use anything else than the documented, proven, and
reliable /usr/sbin/sendmail OR direct smtp/lmtp interfaces. Otherwise, you
are risking information loss on errors, security holes, etc.
--
"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