MobileRead Forums - View Single Post

BetterRed · 10-10-2013, 05:22 AM

Locale takes account of the vagaries of seasonal adjustments to the local time. Locations close to the equator don't adjust their clocks because there is little benefit in doing so, locations in the same time zone but closer to the poles do adjust there clocks because there is a benefit. Case in point the states of NSW and Queensland in Australia are in the same timezone, but as of last weekend when its 20:00hrs in Sydney its 19:00hrs in Brisbane.

If I create a CSV catalog, then a pubdate for which I have entered 2013-10-07, will appear as 2013-10-06 in the CSV, I fix it by getting Excel to unadjust it. It may not matter if its the pubdate of fiction, but it matters if its a pubdate of an op-ed from the Daily Telegraph - which is not published on Sundays.

My assumption is that the OP's issue is related to what I get with pubdates in CSV catalogs.

BR

10-10-2013, 05:22 AM	#93
BetterRed null operator (he/him) Posts: 21,823 Karma: 30277270 Join Date: Mar 2012 Location: Sydney Australia Device: none	Locale takes account of the vagaries of seasonal adjustments to the local time. Locations close to the equator don't adjust their clocks because there is little benefit in doing so, locations in the same time zone but closer to the poles do adjust there clocks because there is a benefit. Case in point the states of NSW and Queensland in Australia are in the same timezone, but as of last weekend when its 20:00hrs in Sydney its 19:00hrs in Brisbane. If I create a CSV catalog, then a pubdate for which I have entered 2013-10-07, will appear as 2013-10-06 in the CSV, I fix it by getting Excel to unadjust it. It may not matter if its the pubdate of fiction, but it matters if its a pubdate of an op-ed from the Daily Telegraph - which is not published on Sundays. My assumption is that the OP's issue is related to what I get with pubdates in CSV catalogs. BR Last edited by BetterRed; 10-10-2013 at 05:46 AM.