From c9651fdb586f93d1dcd632340ee245b8acf309e7 Mon Sep 17 00:00:00 2001 From: Trey Blancher Date: Fri, 11 Nov 2022 19:18:19 -0500 Subject: [PATCH] Fixed minor typo ("code" at the end, not "codes") --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d445164..f297f7b 100644 --- a/README.md +++ b/README.md @@ -68,5 +68,5 @@ Again, this is for my old Microsoft Bluetooth Notebook mouse which is more than ## Note Due to limitations of Rust's strftime implementation, the string representation of the timezone (in the example above, "EST") is ignored. This program currently has a limited set of timezone abbreviations it supports. If the log contains other timezones not explicitly defined in the `match timezone {}` block in the main program loop (`for line in reader.lines(){}`), the program will panic. We'd need to include an explicit mapping for the desired timezone. -Again, this timezone abbreviation to actual timezone mapping is not intended to be exhaustive, as there are inherent ambiguities in the timezone abbreviations. E.g., "CDT" could mean Central Daylight Time (US), or China Daylight Time. This match codes handles the ambiguity rather arbitrarily, consider changing the mapping to suit your needs. +Again, this timezone abbreviation to actual timezone mapping is not intended to be exhaustive, as there are inherent ambiguities in the timezone abbreviations. E.g., "CDT" could mean Central Daylight Time (US), or China Daylight Time. This match code handles the ambiguity rather arbitrarily, consider changing the mapping to suit your needs.