Bewertet mit 4 von 5 Sternen

von Brian Woltemate am Jan. 19, 2011 ·

Fix for all messages.
By replacing the prTime2Str function at 416 with the below function will make the date received %datelocal%Reserved word match the time stamp of Thunderbird. The early comment only fix the problem on certain messages.

function prTime2Str(time, type, timezone)
{
//Patch to correctly handle comcast.net emails.
var tm = new Date();
var fmt = Components.classes["@mozilla.org/intl/scriptabledateformat;1"].
createInstance(Components.interfaces.nsIScriptableDateFormat);
var locale = parent.pref.getCom("general.useragent.locale", "en-US");
// Set Time
tm.setTime(time / 1000);
alert(tm);
// Format date string
switch (type) {
case "datelocal":
dateFormat = fmt.dateFormatLong; timeFormat = fmt.timeFormatSeconds;
break;
case "dateshort":
default:
dateFormat = fmt.dateFormatShort; timeFormat = fmt.timeFormatSeconds;
break;
}
return fmt.FormatDateTime(locale, dateFormat, timeFormat,
tm.getFullYear(), tm.getMonth() + 1, tm.getDate(),
tm.getHours(), tm.getMinutes(), tm.getSeconds());
}

Bewertet mit 4 von 5 Sternen

von Brian Woltemate am Jan. 19, 2011 ·

I was having a problem with the %datelocal% Reserved word. When a message was sent from a comcast.net server Smart Template was interpreting the time zone incorrectly making the tame stamp bogus. I was able to fix it for my purposes by inserting the following at line 418.
//Patch to correctly handle comcast.net emails.
if (timezone == 000)
{
timezone = -300;
}

I'm sure this will cause a problem if an email was actually from the timezone 000 but it fixes the problem for my purposes.

Thank You