summary refs log tree commit diff
path: root/src/blog/java-timezones.md
diff options
context:
space:
mode:
authorStarfall <us@starfall.systems>2023-08-17 12:21:14 -0500
committerStarfall <us@starfall.systems>2023-08-17 12:24:10 -0500
commita369e660f5b387f2e68288518ac0130945b6affd (patch)
tree94f58b7b969efe95ab1da176a9f46ef69b2cf49a /src/blog/java-timezones.md
parent246d9537a7edf8d93f75decd83872374813449df (diff)
add excerpts to blog posts
Diffstat (limited to 'src/blog/java-timezones.md')
-rw-r--r--src/blog/java-timezones.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/blog/java-timezones.md b/src/blog/java-timezones.md
index dd135d4..b33f4f7 100644
--- a/src/blog/java-timezones.md
+++ b/src/blog/java-timezones.md
@@ -6,7 +6,7 @@ categories = [ "software" ]
 Recently ran into an issue at work that we couldn't find a direct answer to anywhere on the Internet (thanks to the terrible state of search in the modern day after Search Engine Optimization and Large Language Models have screwed it over, but that's another topic...) relating to three-letter abbreviations for timezones.
 
 Long story short, use canonical timezone names [from tzdb](http://web.cs.ucla.edu/~eggert/tz/tz-link.htm) like "America/New\_York" instead of abbreviations like "ET".
-
+---
 The abbreviations like EST, CDT, CET, BST... mostly don't work any more, and for good reasons. Is MST Malaysian Standard Time (UTC+8) or North America Mountain Standard Time (UTC-7)? They might be standardized within a given nation's borders, but not worldwide. So, if you run across an error that looks like *this* when trying to parse a date:
 
 ```java