Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

localeconv(3) [linux man page]

LOCALECONV(3)						     Linux Programmer's Manual						     LOCALECONV(3)

NAME
localeconv - get numeric formatting information SYNOPSIS
#include <locale.h> struct lconv *localeconv(void); DESCRIPTION
The localeconv() function returns a pointer to a struct lconv for the current locale. This structure is shown in locale(7), and contains all values associated with the locale categories LC_NUMERIC and LC_MONETARY. Programs may also use the functions printf(3) and strfmon(3), which behave according to the actual locale in use. CONFORMING TO
C89, C99. BUGS
The printf(3) family of functions may or may not honor the current locale. SEE ALSO
locale(1), localedef(1), isalpha(3), nl_langinfo(3), setlocale(3), strcoll(3), strftime(3), locale(7) COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. GNU
1993-04-25 LOCALECONV(3)

Check Out this Related Man Page

LOCALECONV(3)						     Linux Programmer's Manual						     LOCALECONV(3)

NAME
localeconv - get numeric formatting information SYNOPSIS
#include <locale.h> struct lconv *localeconv(void); DESCRIPTION
The localeconv() function returns a pointer to a struct lconv for the current locale. This structure is shown in locale(7), and contains all values associated with the locale categories LC_NUMERIC and LC_MONETARY. Programs may also use the functions printf(3) and strfmon(3), which behave according to the actual locale in use. RETURN VALUE
The localeconv() function returns a pointer to a filled in struct lconv. This structure may be (in glibc, is) statically allocated, and may be overwritten by subsequent calls. According to POSIX, the caller should not modify the contents of this structure. The localeconv() function always succeeds. ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +-------------+---------------+----------------------------------+ |Interface | Attribute | Value | +-------------+---------------+----------------------------------+ |localeconv() | Thread safety | MT-Unsafe race:localeconv locale | +-------------+---------------+----------------------------------+ CONFORMING TO
C89, C99. BUGS
The printf(3) family of functions may or may not honor the current locale. SEE ALSO
locale(1), localedef(1), isalpha(3), nl_langinfo(3), setlocale(3), strcoll(3), strftime(3), locale(7) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
2015-03-02 LOCALECONV(3)
Man Page

3 More Discussions You Might Find Interesting

1. Programming

Not able to compile Pro*c file due - give errors and points to /usr/include/.. file

I am trying to compile the pro*C file but gives errors. It says it encountered "std" while it was expecting ; , = ( $ $ORACLE_HOME/bin/proc tradewind/dataaccess/Blob.pcc Pro*C/C++: Release 10.2.0.3.0 - Production on Fri May 9 11:10:54 2008 Copyright (c) 1982, 2005, Oracle. All rights... (0 Replies)
Discussion started by: shafi2all
0 Replies

2. Shell Programming and Scripting

awk, sed and a shell doubts

Hi, I have 3 doubts which I posted it here. Doubt 1: I have a file containing data: 22 -73 89 10 99 21 15 -77 23 63 -80 91 -22 65 28 97 I am trying to print the fields in the reverse order and replace every field by its absolute (positive) value (ie.) I am looking for output: 10... (8 Replies)
Discussion started by: royalibrahim
8 Replies

3. HP-UX

utf-8, problem with special characters

Hi all, We are facing the following problem in our HP-UX machine: software that manipulates utf-8 encoded strings (e.g. during string cut), fails to correctly manipulate strings (all containing Greek characters) that contain special characters like @, &, # etc. Actually, in different... (3 Replies)
Discussion started by: alina
3 Replies