locale.5: Clarify lang_term / lang_lib

As noted by Keld Simonsen in the lib-locales@sourceware mailing
list:

    https://sourceware.org/ml/libc-locales/2014-q2/msg00008.html
    From: Keld Simonsen <keld at rap dot rap dot dk>
    To: Marko Myllynen <myllynen at redhat dot com>
    Date: Tue, 29 Apr 2014 17:02:09 +0200

    lang_term reflects ISO 639-2/T (terminology) codes, while
    lang_lib reflects ISO 639-2/B (bibliographic) codes.
    lang_term is preferred over lang_lib codes for locale names.
    There are 20 specific ISO 639-2/B codes.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Marko Myllynen 2014-05-22 11:32:53 +03:00 committed by Michael Kerrisk
parent 261ce50b66
commit e6812b0dfd
1 changed files with 6 additions and 3 deletions

View File

@ -197,11 +197,14 @@ followed by the language name in the language of the current document.
followed by the two-letter abbreviation of the language (ISO 639).
.TP
.I lang_term
followed by the three-letter abbreviation of the language (ISO 639-2).
followed by the three-letter abbreviation of the language (ISO 639-2/T).
.TP
.I lang_lib
followed by the three-letter abbreviation of the language for
library use (ISO 639-2).
followed by the three-letter abbreviation of the language for library
use (ISO 639-2/B). Applications should prefer in general
.IR lang_term
over
.IR lang_lib .
.PP
The
.B LC_ADDRESS