|<#[system.date_time_short]#> ⇒||2023-06-02 04:10:37|
|<#[system.date_time_short as timezone]#> ⇒||2023-06-02 00:10:37|
|<#[system.date_time_short as tz "America/Los_Angeles"]#> ⇒||2023-06-01 21:10:37|
<h4 class="alert alert-success text-center"> Local Time: <#[system.date_time as timezone as date "h:mm A"]#> </h4>
Note: When a bare "timezone" or "tz" context is used, any "timezone" or "tz" value in the current session is applied to adjust the Date Time value.
If the current session does not include either a "timezone" or "tz" value, but a latitude, longitude, and country code values are available (such as in Google App Engine requests), a best guess timezone is calculated and set for the current session. The best guess calculation for timezone isn't always right, such as for cities that opt out of daylight savings time, cities with multiple timezones, overhanging borders, as well as users who route their internet traffic over a VPN in a different timezone, so it's best to allow the user to select their own timezone.
The Hashtag Markup Language provides Contexts for reformatting Variable values.
The examples in this section cover the many Contexts the Hashtag Framework supports to alter Variable values.