Review Luxon's table of formatting tokens. You want ZZZZ
for the abbreviated named offset.
Examples:
DateTime.fromObject({year: 2012, month: 1, zone: 'America/New_York'})
.toFormat('ZZZZ') //=> "EST"
DateTime.fromObject({year: 2012, month: 6, zone: 'America/New_York'})
.toFormat('ZZZZ') //=> "EDT"
DateTime.local()
.toFormat('ZZZZ') //=> "PDT" (on my computer)
DateTime.fromISO("2020-05-23T13:30:00+05:30", {zone: 'Asia/Kolkata', locale: 'en-IN'})
.toFormat('ZZZZ') //=> "IST"
Note in that last one, you also have to specify en-IN
as the locale to get IST
. Otherwise you will get GMT+05:30
, unless the system locale is already en-IN
. That is because Luxon relies upon the browser's internationalization APIs, which in turn takes its data from CLDR.
In CLDR, many names and abbreviations are designated as being specific to a given locale, rather than being used worldwide. The same thing happens with Europe/London
getting GMT+1
instead of BST
unless the locale is en-GB
. (I personally disagree with this, but that is how it is currently implemented.)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…