Re: LC_MESSAGES and BSD/OS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Giles Lean <giles(at)nemeton(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: LC_MESSAGES and BSD/OS
Date: 2000-06-29 01:13:30
Message-ID: 17838.962241210@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> OK, I am willing to make them #ifdef'ed, if someone would explain what
> LC_MESSAGES is used for.

The HPUX locale man pages say:

LC_CTYPE determines the interpretation of text as single and/or
multi-byte characters, the classification of characters as printable,
and the characters matched by character class expressions in regular
expressions.

LC_COLLATE provides collation sequence definition
for relative ordering between collating elements (single- and
multi-character collating elements) in the locale.

LC_MESSAGES determines the locale that should be used to affect the
format and content of diagnostic messages written to standard error,
and informative messages written to standard output.

LC_MONETARY defines the rules and symbols used to
format monetary numeric information.

LC_NUMERIC defines rules and symbols used to format
non-monetary numeric information.

LC_TIME defines the rules for generating locale-specific formatted
date strings.

LC_ALL, when set to a non-empty string value, overrides the values of
all other internationalization variables.

Dunno which LC_foo variable corresponds to LC_MESSAGES on BSDI.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-06-29 01:19:04 Re: LC_MESSAGES and BSD/OS
Previous Message Tom Lane 2000-06-29 01:05:02 Re: Big 7.1 open items