|SETLOCALE(3)||Library Functions Manual||SETLOCALE(3)|
category, const char
setlocale() function sets and retrieves the active locale for the current process. The locale modifies the behaviour of some functions in the C library with respect to the character encoding, and on other operating systems also with respect to some language and cultural conventions. For more information about locales in general, see the locale(1) manual page.
On OpenBSD, the only useful value for the
LC_CTYPE. It sets
the locale used for character encoding, character classification, and case
conversion. For compatibility with natural language support in
packages(7), all other categories
— can be set and retrieved, too, but their values are ignored by the
OpenBSD C library. A category of
LC_ALL sets the entire locale generically, which is
strongly discouraged for security reasons in portable programs.
The syntax and semantics of the locale
argument are not standardized and vary among operating systems. On
OpenBSD, if the locale string
ends with “.UTF-8”, the UTF-8 locale is selected; otherwise,
the “C” locale is selected, which uses the ASCII character
set. If the locale contains a dot but does not end
If locale is an empty string
(“”), the value of the environment variable
LC_ALL, with a fallback to the variable
corresponding to category, and with a further fallback
LANG, is used instead, as documented in the
locale(1) manual page.
If locale is
the locale remains unchanged. This can be used to determine the currently
By default, C programs start in the “C” locale. The
only function in the library that sets the locale is
setlocale(); the locale is never changed as a side
effect of some other routine.
LC_CTYPE category modifies the
behaviour of at least the following functions:
wctype(3), and the functions documented
setlocale() returns a pointer to a static string describing the locale that is in force after the call. Subsequent calls to
setlocale() may change the content of the string. The format of the string is not standardized and varies among operating systems.
On OpenBSD, if
setlocale() was never called with a
NULL locale argument, the
string “C” is returned. Otherwise, if the
category was not
LC_ALL or if
the locale is the same for all categories, a copy of the
locale argument is returned. Otherwise, the locales
for the six categories
LC_TIME are concatenated in that order, with slash
/’) characters in between.
In case of failure,
NULL. On OpenBSD, that can
only happen if the category is invalid, if a character
encoding other than UTF-8 is requested, if the requested
locale name is of excessive length, or if memory
at the beginning of a program selects the UTF-8 locale and returns “en_US.UTF-8”. Calling
right afterwards leaves the locale unchanged and returns “C/en_US.UTF-8/C/C/C/C”.locale(1), newlocale(3), nl_langinfo(3), uselocale(3)
setlocale() function conforms to ANSI X3.159-1989 (“ANSI C89”).
setlocale() function first appeared in 4.4BSD. OpenBSD, calling
setlocale() or uselocale(3) with a category other than
LC_CTYPEcan cause erratic behaviour of many library functions. For security reasons, make sure that portable programs only use
For example, the following functions may be affected. The list is probably incomplete. For example, additional library functions may be impacted if they directly or indirectly call affected functions, or if they attempt to imitate aspects of their behaviour. Functions that are not standardized may be affected too.
strfmon(), and the functions documented in printf(3), scanf(3), strtod(3), wcstod(3), wprintf(3), wscanf(3). This category is particularly dangerous because it can cause bugs in the parsing and formatting of numbers, for example failures to recognize or properly write decimal points.
getdate(), nl_langinfo(3), strftime(3), strptime(3). Similarly, this is prone to causing bugs in the parsing and formatting of date strings.
|January 13, 2019||OpenBSD-current|