HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

l
localedef(4) localedef(4)
negative numbers. For example, an era beginning March 5th
in the year 100 B.C. would be represented as
3-100/3/5.
Years in the range
[SHRT_MIN+1,SHRT_MAX-1]
are sup-
ported.
end_date The ending date of the era in the same form as the start_date
above or one of the two special values
-* or +*. A value of
-* indicates the ending date of the era extends to the begin-
ning of time while +* indicates it extends to the end of time.
The ending date can be chronologically either before or after
the starting date of an era. For example, the expressions for
the Christian eras A.D. and B.C. would be:
+:0:0000/01/01:+*:A.D.:%o %N
+:1:-0001/12/31:-*:B.C.:%o %N
name A string representing the name of the era which is substituted
for the %N directive of date and strftime()
(see date(1)
and strftime(3C)).
format A string for formatting the
%E directive of date and
strftime() . This string is usually a function of the %o
and %N directives. If format is not specified, the string
specified for the LC_TIME category keyword era_d_fmt
(see below) is used as a default.
era_d_fmt The operand is a string defining the format of date in era notation.
era_t_fmt The operand is a string defining the format of time in era notation.
era_d_t_fmt
The operand is a string defining the format of date and time in era notation.
alt_digits The operand is a semi-colon-separated list of strings. The first string is the alter-
native symbol corresponding to zero, the second string is the alternative symbol
corresponding to one, and so on. Note that if the HP-UX-proprietary
alt_digit keyword has been specified in the same locale, the first ten sym-
bols should be identical for these two keywords.
In addition to the above, the following HP-UX-proprietary keywords are recognized (these are pro-
vided for backward compatibility and their use is otherwise not recommended):
year_unit,
mon_unit, day_unit, hour_unit , min_unit, sec_unit.
LC_MESSAGES :
The LC_MESSAGES category defines the format and values for affirmative and negative responses.
The following keywords belong to this category and should come between the category tag
LC_MESSAGES and END LC_MESSAGES :
yesexpr The string operand is an Extended Regular Expression matching acceptable
affirmative responses to yes/no queries.
noexpr The string operand is an Extended Regular Expression matching acceptable
negative responses to yes/no queries.
yesstr The string operand identifies the affirmative response for yes/no questions. This
keyword is now obsolete and yesexpr should be used instead.
nostr The string operand identifies the negative response for yes/no questions This
keyword is now obsolete and noexpr should be used instead.
Keyword Operands
Keyword operands consist of character-code constants and symbols, strings, and metacharacters. The types
of legal expressions are: character lists, string lists, integer lists, shift, collat-
ing element entries
, regular expression , character constants and string:
character lists
character list
operands consist of single character-code constants or symbolic names
separated by semicolons, or a character-code range consisting of a constant or symbolic
name followed by an ellipsis followed by another constant or symbolic name. The constant
preceding the ellipsis must have a smaller code value than the constant following the
HP-UX 11i Version 3: February 2007 − 6 − Hewlett-Packard Company 223