The DESCRIPTION says

  The  nl_langinfo()  and  nl_langinfo_l()  functions  provide  access to
         locale information in a more flexible way than localeconv(3). 
nl_lang‐
         info() returns a string which is the value corresponding to 
item in the
         program's current global locale.  nl_langinfo() returns a 
string  which
         is  the  value  corresponding  to item for the locale 
identified by the
         locale object locale, which was  previously  created  by 
newlocale(1).
         Individual  and  additional  elements  of  the locale 
categories can be
         queried.  setlocale(3) needs  to  be  executed  with  proper 
arguments
         before.

Notice that it says two different things about nl_langinfo, and none 
about nl_langinfo_l.

And it's wrong.  I looked at the implementation, and these functions 
follow the paradigm of things like isalnum(), which is what one hopes 
they do.

nl_langinfo looks first for a thread-specific locale object, and only if 
not found does it fall back to the global one.  Neither of the two 
sentences say this.

The final sentence is also wrong.  Either setlocale or uselocale should 
have been done on the category or object needed.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html