Continuing the discussion from Hugo timezone format issue: (the original thread was already marked as ‘solved’)
While the solution is the following:
It only addressed the timezone “getting send twice”. The “MST value not being reported as it should” is only solved partially.
See the following examples (note: I set my TZ env to Asia/Manila)
- EN-PH: timezone abbr with offset – YourOnly.One's Hugo Test Site - working correctly
- EN-PH: timezone abbr without offset – YourOnly.One's Hugo Test Site -working correctly
- JA: timezone abbr with offset – YourOnly.OneのHugoテストサイト - incorrect MST value
- JA: timezone abbr without offset – YourOnly.OneのHugoテストサイト - incorrect MST value
- KO: timezone abbr with offset – YourOnly.One's Hugo 테스트 사이트 - incorrect MST value
- KO: timezone abbr without offset – YourOnly.One's Hugo 테스트 사이트 - incorrect MST value
The TZ workaround will only work if the TZ env matches the timezone language or offset. In the examples above, since the timezone for the Japanese and Korean pages is set (without offset) JA/KO lang (which is +0900), or (with offset set) +09:00, the “MST” value is still not being displayed correctly, it should be “JST” and “KST” respectively.
As we can see in these two “without offset” samples:
- JA: timezone abbr without offset – YourOnly.OneのHugoテストサイト - incorrect MST value
- KO: timezone abbr without offset – YourOnly.One's Hugo 테스트 사이트 - incorrect MST value
The system is capable of displaying the correct MST value.
As per @M4rt1n’s reply:
I assume that this issue is entirely Go related?
notes:
- Test site auto-generates the “checkmark” or “x-mark” on build, it’s not manually edited.
- Repo for test site is at: GitHub - techmagus/hugo-test-site: YourOnly.One's Hugo Test Site if one wants to test locally or deploy in CF Pages (or other services/servers).
