Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 91b81c4

Browse files
committed
Some minor clarifications for find()'s arguments based on SF bug
#463572. Closing.
1 parent c10039c commit 91b81c4

1 file changed

Lines changed: 6 additions & 5 deletions

File tree

Doc/lib/libgettext.tex

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -98,18 +98,19 @@ \subsection{Class-based API}
9898
\begin{funcdesc}{find}{domain\optional{, localedir\optional{, languages}}}
9999
This function implements the standard \file{.mo} file search
100100
algorithm. It takes a \var{domain}, identical to what
101-
\function{textdomain()} takes, and optionally a \var{localedir} (as in
102-
\function{bindtextdomain()}), and a list of languages. All arguments
103-
are strings.
101+
\function{textdomain()} takes. Optional \var{localedir} is as in
102+
\function{bindtextdomain()} Optional \var{languages} is a list of
103+
strings, where each string is a language code.
104104

105105
If \var{localedir} is not given, then the default system locale
106106
directory is used.\footnote{See the footnote for
107107
\function{bindtextdomain()} above.} If \var{languages} is not given,
108108
then the following environment variables are searched: \envvar{LANGUAGE},
109109
\envvar{LC_ALL}, \envvar{LC_MESSAGES}, and \envvar{LANG}. The first one
110110
returning a non-empty value is used for the \var{languages} variable.
111-
The environment variables can contain a colon separated list of
112-
languages, which will be split.
111+
The environment variables should contain a colon separated list of
112+
languages, which will be split on the colon to produce the expected
113+
list of language code strings.
113114

114115
\function{find()} then expands and normalizes the languages, and then
115116
iterates through them, searching for an existing file built of these

0 commit comments

Comments
 (0)