Below follows information on how to specify the Time Format and the Numeric Format of the output field defined in the template. This feature utilizes the standard Java formatting 'patterns'. This Java documentation is not maintained by Unanet.
To specify the time format use a time pattern string. In this pattern, all ASCII letters are reserved as pattern letters, which are defined as the following:
Symbol Meaning Presentation Example
------ ------- ------------ -------
G era designator (Text) AD
y year (Number) 1996
M month in year (Text & Number) July & 07
d day in month (Number) 10
h hour in am/pm (1~12) (Number) 12
H hour in day (0~23) (Number) 0
m minute in hour (Number) 30
s second in minute (Number) 55
S millisecond (Number) 978
E day in week (Text) Tuesday
D day in year (Number) 189
F day of week in month (Number) 2 (2nd Wed in July)
w week in year (Number) 27
W week in month (Number) 2
a am/pm marker (Text) PM
k hour in day (1~24) (Number) 24
K hour in am/pm (0~11) (Number) 0
z time zone (Text) Pacific Standard Time
' escape for text (Delimiter)
'' single quote (Literal) '
(Text): 4 or more pattern letters--use full form, < 4--use short or abbreviated form if one exists.
(Number): the minimum number of digits. Shorter numbers are zero-padded to this amount. Year is handled specially; that is, if the count of 'y' is 2, the Year will be truncated to 2 digits.
(Text & Number): 3 or over, use text, otherwise use number.
Any characters in the pattern that are not in the ranges of ['a'..'z'] and ['A'..'Z'] will be treated as quoted text. For instance, characters like ':', '.', ' ', '#' and '@' will appear in the resulting time text even they are not embraced within single quotes.
A pattern containing any invalid pattern letter will result in a thrown exception during formatting or parsing.
Examples Using the US Locale:
Format Pattern Result
-------------- -------
"yyyy.MM.dd G 'at' hh:mm:ss z" ->> 1996.07.10 AD at 15:08:56 PDT
"EEE, MMM d, ''yy" ->> Wed, July 10, '96
"h:mm a" ->> 12:08 PM
"hh 'o''clock' a, zzzz" ->> 12 o'clock PM, Pacific Daylight Time
"MM/dd/yyyy" ->> 07/10/1996
"yyyyy.MMMMM.dd GGG hh:mm aaa" ->> 1996.July.10 AD 12:08 PM
A pattern contains a postive and negative subpattern, for example, "#,##0.00;(#,##0.00)". Each subpattern has a prefix, numeric part, and suffix. The negative subpattern is optional; if absent, then the positive subpattern prefixed with the localized minus sign ('-' in most locales) is used as the negative subpattern. That is, "0.00" alone is equivalent to "0.00;-0.00". If there is an explicit negative subpattern, it serves only to specify the negative prefix and suffix; the number of digits, minimal digits, and other characteristics are all the same as the positive pattern. That means that "#,##0.0#;(#)" produces precisely the same behavior as "#,##0.0#;(#,##0.0#)".
The prefixes, suffixes, and various symbols used for
infinity, digits, thousands separators, decimal separators, etc. may be set to
arbitrary values, and they will appear properly during formatting. However, care
must be taken that the symbols and strings do not conflict, or parsing will be
unreliable. For example, either the positive and negative prefixes or the
suffixes must be distinct for the system
to be able to distinguish positive from negative values. (If they are identical,
then the system will behave
as if no negative subpattern was specified.) Another example is that the decimal
separator and thousands separator should be distinct characters, or parsing will
be impossible.
The grouping separator is commonly used for thousands, but in some countries it separates ten-thousands. The grouping size is a constant number of digits between the grouping characters, such as 3 for 100,000,000 or 4 for 1,0000,0000. If you supply a pattern with multiple grouping characters, the interval between the last one and the end of the integer is the one that is used. So "#,##,###,####" == "######,####" == "##,####,####".
Illegal patterns, such as "#.#.#" or
"#.###,###", will cause the
system to display an error message with a message that describes
the problem.
Many characters in a pattern are taken literally; they are matched during parsing and output unchanged during formatting. Special characters, on the other hand, stand for other characters, strings, or classes of characters. They must be quoted, unless noted otherwise, if they are to appear in the prefix or suffix as literals.
|
Symbol |
Location |
Localized? |
Meaning |
|
0 |
Number |
Y |
Digit |
|
# |
Number |
Y |
Digit, zero shows as absent |
|
. |
Number |
Y |
Decimal separator or monetary decimal separator |
|
- |
Number |
Y |
Minus sign |
|
, |
Number |
Y |
Grouping separator |
|
E |
Number |
Y |
Separates mantissa and exponent in scientific notation. Need not be quoted in prefix or suffix. |
|
; |
Subpattern boundary |
Y |
Separates positive and negative subpatterns |
|
% |
Prefix or suffix |
Y |
Multiply by 100 and show as percentage |
|
\u2030 |
Prefix or suffix |
Y |
Multiply by 1000 and show as per mille |
|
¤ |
Prefix or suffix |
N |
Currency sign, replaced by currency symbol. If doubled, replaced by international currency symbol. If present in a pattern, the monetary decimal separator is used instead of the decimal separator. |
|
' |
Prefix or suffix |
N |
Used to quote special characters
in a prefix or suffix, for example, |
Currently, the only time format options are as follows:
|
Symbol |
Location |
Localized? |
Meaning |
|
h |
Number |
Y |
Hours in whole numbers (values < 10 will be one digit. |
|
hh |
Number |
Y |
Hours in whole number (values < 10 will have a leading zero |
|
mm |
Number |
Y |
Minutes in whole number (values < 10 will have a leading zero |
Return to Unanet Table of Contents page
Copyright © 1998-2001 Computer Strategies, Inc.,
All Rights Reserved.
Last revised: February 13, 2003.