Menu
▾
▴
[Bacula-bugs] [bacula 0000809]: UTF-8 issue in bsmtp and bweb
|
From: <bac...@li...> - 2007-04-22 13:35:02
|
The following issue has been CLOSED ====================================================================== http://bugs.bacula.org/view.php?id=809 ====================================================================== Reported By: mschmid Assigned To: ====================================================================== Project: bacula Issue ID: 809 Category: Director Reproducibility: always Severity: minor Priority: normal Status: closed Resolution: fixed Fixed in Version: 2.1.x ====================================================================== Date Submitted: 03-23-2007 04:03 EDT Last Modified: 04-22-2007 09:34 EDT ====================================================================== Summary: UTF-8 issue in bsmtp and bweb Description: If the system's standard encoding is UTF-8 (or anything else), both the email client and the web interface still continue sending all as default charset which is ISO-8859. ====================================================================== ---------------------------------------------------------------------- kern - 03-24-07 08:06 ---------------------------------------------------------------------- bsmtp explicitly sets the LOCAL to en_US because otherwise SMTP does not work correctly when sending dates and such. As far as I know, the actual data that is read and sent by bsmtp is not modified at all, which means it should remain in whatever character set you use. Your bug report is very incomplete as you have not described what problems occur or why nor provided any output showing a failure. Please supply additional information that permit us to understand and possibly correct the problem. ---------------------------------------------------------------------- mschmid - 03-25-07 10:37 ---------------------------------------------------------------------- The problem does not lie in any conversion that bsmtp may or may not make but as long as you don't declare the character set in the mail header, the mail client switches to ISO-8859. So, since bsmtp does not convert anything, but the log file is in UTF-8, all mail is wrongly displayed as ISO-8859. I'd suggest a command line parameter to bsmtp that would allow any additional header. ---------------------------------------------------------------------- mschmid - 03-25-07 10:48 ---------------------------------------------------------------------- I should also say that the same applies to bweb which may be another's responsability. There also are two lines in the templates where the encoding is not declared at all and that leads to wrong presentations of the log files: There is something like CGI::header("text/html") but with a declatation of the character set used, everything would be fine: CGI::header("text/html; charset UTF-8") Please, be aware of the fact that I can not view the real code as I have modified it. It's all as I remember things. I'm not in the office right now. For both, bweb and bsmtp, they should declare the system's character set to web and mail clients... ---------------------------------------------------------------------- mschmid - 04-10-07 08:46 ---------------------------------------------------------------------- I've reported the bweb issue to ebollengier. That's a separate story. But the bsmtp problem remains. I'm in trouble clarifying it more extensively. If I send in a sample file, it may not be displayed equally on your and my PC. In the very end, it's the client (the mail program) that will display it wrongly. The cause however lies in the missing declaration of the system's standard encoding. Debian Etch's is UTF-8 and all of bacula's logs are written in the same encoding. Because this is not declared to the mail client at all, it will be displayed wrongly. First of all, umlauts will be affected. ---------------------------------------------------------------------- kern - 04-10-07 09:03 ---------------------------------------------------------------------- Thanks for reporting this. However, it is not 100% obvious how to resolve this, and in any case, it isn't the highest priority at the moment. If you want it fixed quickly, I'd recommend submitting a patch. Looking at patches gets quite high priority ... ---------------------------------------------------------------------- kern - 04-22-07 09:34 ---------------------------------------------------------------------- I've added a -8 command line option, which will cause bsmtp to send the following line to the server: Content-Type: text/plain; charset=UTF-8 Issue History Date Modified Username Field Change ====================================================================== 03-23-07 04:03 mschmid New Issue 03-24-07 08:06 kern Note Added: 0002318 03-24-07 08:06 kern Status new => feedback 03-25-07 10:37 mschmid Note Added: 0002321 03-25-07 10:48 mschmid Note Added: 0002322 04-10-07 08:46 mschmid Note Added: 0002353 04-10-07 09:03 kern Note Added: 0002355 04-22-07 09:34 kern Note Added: 0002380 04-22-07 09:34 kern Status feedback => closed 04-22-07 09:34 kern Resolution open => fixed 04-22-07 09:34 kern Fixed in Version => 2.1.x ====================================================================== |