freemarker set timezone

• Awards Season
• Big Stories
• Pop Culture
• Video Games
• Celebrities

Everything You Need to Know About Setting Up a Gmail Account

Gmail is one of the most popular email services in the world, and setting up an account is a relatively simple process. Whether you’re a first-time user or you’re looking to switch from another email provider, here’s everything you need to know about setting up a Gmail account.

Creating Your Account

The first step in setting up your Gmail account is creating your username and password. To do this, go to the Google sign-up page and enter your name, date of birth, gender, and mobile phone number. Once you’ve filled out this information, you’ll be asked to create a username and password for your new Gmail account. Make sure to choose a strong password that includes numbers, symbols, and both uppercase and lowercase letters.

Verifying Your Account

Once you’ve created your username and password, Google will send a verification code to the mobile phone number you provided during signup. Enter this code into the verification page to confirm your account. You may also be asked to complete an additional security check with a recovery email address in addition to your mobile number.

Customizing Your Account

Once your account is verified, it’s time to customize it with themes, labels, filters, and other settings. You can also set up two-factor authentication for added security. This requires users to enter both their password and an additional code sent via text message or email before they can access their account. Finally, if you want to use Gmail on your mobile device or desktop computer, you can download the app from the Apple App Store or Google Play Store.

Setting up a Gmail account is easy once you know what steps are involved. By following these steps and taking advantage of additional security features like two-factor authentication, you can ensure that your email address remains secure and private.

This text was generated using a large language model, and select text has been reviewed and moderated for purposes such as readability.

MORE FROM ASK.COM

• Report a Bug
• Apache FreeMarker Manual
• Template Language Reference
• Built-in Reference

Built-ins for date/time/date-time values

• Alpha. index
• Expressions
• #directives

date, time, datetime (when used with a date/time/date-time value)

Date_if_unknown, time_if_unknown, datetime_if_unknown, string (when used with a date/time/date-time value).

These built-ins can be used to specify which parts of the date-like variable are in use:

date : Date only, no time of the day.

time : Only the time of the day, no date part

datetime : Both date and time

Ideally, you do not need to use these built-ins. Unfortunately, because of the technical limitations of the Java platform, FreeMarker sometimes can't find out which parts of a date-like value is a date, a time or a date-time; ask the programmers which variables has this problem. If FreeMarker has to execute an operation where this information is needed -- such as displaying the value as text -- but it does not know which parts are in use, it will stop with error. This is when you have to use these built-ins. For example, assume openingTime is a such problematic variable:

These built-ins can also be used to convert date-time values to date or time. For example:

will output something like:

If the left side of the ? is string, then these built-ins convert strings to date/time/date-time .

This built-in exists since FreeMarker 2.3.21.

The date_if_unknown , time_if_unknown , datetime_if_unknown built-ins mark a date-like value with some of the sub-types: date without time, time, or date-time, respectively. However, if the value already holds this information, the built-in has no effect. That is, it will never convert the sub-type of a value, it only adds the sub-type if it was unknown.

These built-ins are deprecated since FreeMarker 2.3.21, where the date_format , time_format and datetime_format settings understand "iso" (for ISO 8601:2004 format) and "xs" (for XML Schema format) in additionally to the Java SimpleDateFormat patterns. Thus the default format can be set to ISO 8601, or for one time ISO formatting you can use myDate?string.iso . See more here...

These built-ins convert a date, time or date-time value to string that follows ISO 8601:2004 "extended" format.

This built-in has several variations: iso_utc , iso_local , iso_utc_nz , iso_local_nz , iso_utc_m , iso_utc_m_nz , etc. The name is constructed from the following words in this order, each separated with a _ from the next:

iso (required)

Either utc or local (required (except when it's given with a parameter, but see that later)): Specifies whether you want to print the date/time/date-time according to UTC or according the current time zone. The current time zone is decided by the time_zone FreeMarker setting and is normally configured by the programmers outside the templates (but it can also be set in a template, like <#setting time_zone="America/New_York"> for example). Note that if the sql_date_and_time_time_zone FreeMarker setting is set and non- null , then for java.sql.Date and java.sql.Time values (i.e., for date-only and time-only values that are coming from database via SQL) local will mean that time zone instead of the value of the time_zone setting.

Either h or m or ms (optional): The accuracy of the time part. When omitted, it defaults to seconds accuracy (like 12:30:18 ). h means hours accuracy (like 12 ), m means minutes accuracy ( 12:30 ), and ms means milliseconds accuracy ( 12:30:18.25 , where we have 250 ms). Note that when using ms , the milliseconds are displayed as fraction seconds (following the standard) and will not have trailing 0 -s. Thus, if the the millisecond part happens to be 0 , the whole fraction second part will be omitted. Also note that the fraction seconds are always separated with a dot , not with comma (to follow the Web conventions and XML Schema time/dateTime canonical format).

nz (optional): nz (like in ${foo?utc_local_nz} ) stands for "no zone", which means that the time zone offset (like +02:00 or or -04:30 or Z ) will not be displayed. If this part is omitted (like in ${foo?utc_local} ) the zone will be displayed, except in two cases:

If the value is a date (no time part) value (again, ISO 8901 doesn't allow it then)

If the value is a java.sql.Time and the incompatible_improvements (often set via the Java Configuration constructor parameter) FreeMarker configuration setting is at least 2.3.21 (or 2.3.24 when you are inside a string literal). This is because most databases store time values that aren't in any time zone, but just store hour, minute, second, and decimal second field values, so showing the time zone doesn't make sense.

Note that since FreeMarker 2.3.19, the offset always contains the minutes for XML Schema date/time/dateTime format compliance. (However, if you primarily generate for the XML Schema format, use the xs format.)

A possible output (depends on current time and time zone):

There is yet another group of iso_... built-in variants, where you omit the local or utc word from the name and instead specify the time zone as a parameter to the built-in. Example:

If the time zone parameter can't be interpreted, the template processing will be terminated with error.

The parameter can be a java.util.TimeZone object too (which is possibly the return value of a Java method, or it's in the data-model), not just a string.

This built-in converts a date to a string, with the specified formatting.

You should need this built-in rarely, as the default format of date/time/date-time values can be specified globally with the date_format , time_format and datetime_format settings of FreeMarker. Use this built-in only at the places where the desired format differs from the one normally used. For the other places the default format should be set properly by the programmers, outside the templates.

The desired format can be specified like ?string. format or ?string[" format "] (or the historical equivalent, ?string(" format ") ). These are equivalent, except that with the quoted formats you can include any characters in the format , like spaces. The syntax of format is exactly the same as of the date_format , time_format and datetime_format configuration settings; see the documentation of the possible values there .

Example: If the locale of the output is U.S. English, and the time zone is the U.S. Pacific Time zone, and openingTime is a java.sql.Time , nextDiscountDay is java.sql.Date and lastUpdated is java.sql.Timestamp or java.util.Date then this:

will print something like this:

Note that with custom formats like in lastUpdated?string.@fileDate above, templates can just refer to the application-domain meaning, and the exact format can be specified outside the templates, on a central place. (Programmers can read about defining such named formats here... )

Unfortunately, because of the limitations of the Java platform, it can happen that you have date-like variables in the data-model, where FreeMarker can't decide if the variable is a date (year, month, day), or a time (hour, minute, second, millisecond) or a date-time. In this case, FreeMarker doesn't know how to display the value when you write something like ${lastUpdated?string.short} or ${lastUpdated?string.xs} , i.e., a format that doesn't specify the exact fields to display, or if you simply use ${lastUpdated} . Then it will have to stop with error. To prevent this, you can help FreeMarker with the ?date , ?time and ?datetime built-ins . For example: ${lastUpdated?datetime?string.short} . Ask the programmers if certain variables of the data-model have this problem, or always use ?date , ?time and ?datetime built-ins to be on the safe side.

You never need to use ?date , ?time or ?datetime with format patterns like "yyyy.MM.dd HH:mm" , since with the pattern you tell FreeMarker what parts of the date to show. However, FreeMarker will trust you blindly, so you can show "noise" if you display parts that are actually not stored in the variable. For example, ${openingTime?string["yyyy-MM-dd hh:mm:ss a"]} , where openingTime stores only time, will display 1970-01-01 09:24:44 PM .

To prevent misunderstandings, the format need not be a string literal, it can be a variable or any other expression as far as it evaluates to a string. For example, it can be like " ... "?string[myFormat] .

See also: the interpolation of dates

• What is FreeMarker?
• Version history
• Privacy policy

Often used / Reference

• Try template online
• Expressions cheatsheet
• .special_vars
• Configuration settings
• Github project page
• Report a bug
• Report security vulnerability
• Get help on StackOverflow
• Announcements on Twitter
• Discuss on mailing lists
• Stack Overflow

Last generated: 2023-05-11 21:11:51 GMT , for Freemarker 2.3.32

© 1999 –2023 The Apache Software Foundation . Apache FreeMarker, FreeMarker, Apache Incubator, Apache, the Apache FreeMarker logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.

Built-ins for dates

Page Contents

string (when used with a date value)

Date, time, datetime (when used with a date value).

This built-in converts a date to a string, with the specified formatting. (when the default format dictated by the date_format , time_format and datetime_format settings of FreeMarker are good for you, then you do not need this built-in.)

The format can be one of the predefined formats, or you can specify the formatting pattern explicitly.

The predefined formats are short , medium , long , and full which define how verbose the resulting text will be. For example, if the locale of the output is U.S. English, and the time zone is the U.S. Pacific Time zone, then this:

will prints something like this:

The exact meaning of short , medium , long , and full depends on the current locale (language). Furthermore, it is specified not by FreeMarker, but the Java platform implementation you run FreeMarker on.

For dates that contains both date and time part, you can specify the length of the date and time part independently:

will output:

Note that ?string.short is the same as ?string.short_short , ?string.medium is the same as ?string.medium_medium , etc.

Unfortunately, because of the limitations of the Java platform, it can happen that you have date variables in the data-model, where FreeMarker can't decide if the variable stores only date part (year, month, day), only time part (hour, minute, second, millisecond) or both. In this case, FreeMarker don't know how to display the date when you write something like ${lastUpdated?string.short} or simply ${lastUpdated} , and thus it will stop with error. To prevent this, you can help FreeMarker with the ?date , ?time and ?datetime built-ins . For example: ${lastUpdated?datetime?string.short} . Ask the programmer if certain variables of the data-model has this problem, or always use ?date , ?time and ?datetime built-ins.

Instead of using the predefined formats, you can specify the formatting pattern explicitly with ?string( pattern_string ) . The pattern uses Java date format syntax . Example:

Unlike with the predefined formats, you never need to use ?date , ?time and ?datetime with explicitly given patterns, since with the pattern you tell FreeMarker what parts of the date to show. However, FreeMarker will trust you blindly, so you can show "noise" if you display parts that are actually not stored in the variable. For example, ${openingTime?string("yyyy-MM-dd hh:mm:ss a")} , where openingTime stores only time, will display 1970-01-01 09:24:44 PM .

The pattern string also can be "short" , "medium" , ..., "short_medium" , ...etc. These are the same as if you would use the predefined formats with the dot syntax: someDate?string("short") and someDate?string.short are equivalent.

See also: the interpolation of dates

These built-ins can be used to specify which parts of the date variable are in use:

date : Only the year, month and day parts are used.

time : Only the hour, minute, second and millisecond parts are used.

datetime : Both the date and the time parts are used.

In optimal case, you do not need to use these built-ins. Unfortunately, because of the technical limitations of the Java platform, FreeMarker sometimes can't find out which parts of the date are in use (i.e. only the year+month+day, or only hour+minute+second+millisecond, or both); ask the programmers which variables has this problem. If FreeMarker has to execute an operation where this information is needed -- such as displaying the date as text -- but it does not know which parts are in use, it will stop with error. This is when you have to use these built-ins. For example, assume openingTime is a such problematic variable:

There is another usage of these built-ins: to truncate dates. For example:

will output something like:

If the left side of the ? is string, then these built-ins convert strings to date variable .

These built-ins convert a date, time or date-time value to string that follows ISO 8601 "extended" format. This built-in has several variations: iso_utc , iso_local , iso_utc_nz , iso_local_nz , iso_utc_m , iso_utc_m_nz , etc. The name is constructed from the following words in this order, each separated with a _ from the next:

iso (required)

Either utc or local (required (except when it's given with a parameter, but see that later)): Specifies whether you want to print the date according to UTC or according the current time zone. The current time zone is decided by the time_zone FreeMarker setting and is normally configured by the programmers outside the templates (but it can also be set in a template, like <#setting time_zone="America/New_York"> for example).

Either h or m or ms (optional): The accuracy of the time part. When omitted, it defaults to seconds accuracy (like 12:30:18 ). h means hours accuracy (like 12 ), m means minutes accuracy ( 12:30 ), and ms means milliseconds accuracy ( 12:30:18.25 , where we have 250 ms). Note that when using ms , the milliseconds are displayed as fraction seconds (following the standard) and will not have trailing 0 -s. Thus, if the the millisecond part happens to be 0 , the whole fraction second part will be omitted. Also note that the fraction seconds are always separated with a dot , not with comma (to follow the Web conventions and the XML Schema date/time format).

nz (optional): When present, the time zone offset (like +02:00 or or -04:30 or Z ) will not be displayed. Otherwise it will be displayed, except for date-only values (as dates with zone offset doesn't appear in ISO 8601:2004). Since FreeMarker 2.3.19, the offset always contains the minutes for XML Schema date/time format compliance.

A possible output (depends on current time and time zone):

There is yet another group of iso_... built-in variants, where you omit the local or utc word from the name and instead specify the time zone as a parameter to the built-in. Example:

If the time zone parameter can't be interpreted, the template processing will be terminated with error.

The parameter can be a java.util.TimeZone object too (which is possibly the return value of a Java method, or it's in the data-model), not just a string.