Description:
------------
[Excerpt from end of bug 20382, for a separate problem that should be logged as a new bug]:

Compare the PHP script:

<?php
putenv("TZ=Australia/Lord_Howe");
$tStamp = mktime (17, 17, 17, 1, 1, 1970);
echo $tStamp, "\n";
print "tStamp=". date("l Y-m-d H:i:s T", $tStamp). "\n";
$strtotime_tstamp = strtotime("Monday", $tStamp);
echo $strtotime_tstamp, "\n";
print "result=".date("l Y-m-d H:i:s T", $strtotime_tstamp)."\n";
print "wanted=Monday            00:00:00\n\n";
?>

output:
26237
tStamp=Thursday 1970-01-01 17:17:17 EST
306000
result=Sunday 1970-01-04 23:00:00 EST
wanted=Monday            00:00:00

with the code that the timelib does:

derick@kossu:/dat/dev/timelib$ ./tester-create-ts "1970-01-01 17:17:17
Monday" "" "Australia/Lord_Howe"

TS: 306000 | 1970-01-05 00:00:00 LHST Australia/Lord_Howe  0Y   0M   0D
/   0H  0M   0S / 0

derick@kossu:/dat/dev/timelib$ ./tester-render-ts 306000
Australia/Lord_Howe

TYPE: 3 TS: 306000 | 1970-01-05 00:00:00 LHST Australia/Lord_Howe

You see that the timestamp is the same, but that the date() function renders it wrongly as 1970-01-04 23:00:00 EST while it should have been 1970-01-05 00:00:00 LHST. The EST is not even part of the timezone information for Lord Howe.