[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lynx-dev [2.8.2dev.8] Revised LYPrint and ENV VARS documentation patch (
|
From: |
Kim DeVaughn |
|
Subject: |
lynx-dev [2.8.2dev.8] Revised LYPrint and ENV VARS documentation patch (was: Env var documentation) |
|
Date: |
Wed, 9 Dec 1998 11:44:11 -0800 |
On Tue, Dec 08, 1998, Klaus Weide (address@hidden) said:
|
| On Sat, 5 Dec 1998, Kim DeVaughn wrote:
| >
| > I've also made a first attempt at adding an ENVIRONMENT section to the
| > man page. and in addition to the variables for the above, included the
| > more common (and some not-so-common) lynx-specific env vars, and a few
| > general ones, as well.
|
| Since you already went to to trouble, may I suggest some refinements and
| hope that you will generate patches? :)
Damn. I just *knew* I wouldn't get off that easy ... :-) ...!
Anyway, thanks for the excellent suggestions and corrections. I think that
I've incorporated all of them into the attached revised patch (which should
be applied over a clean 2.8.2dev.8, and NOT on top of my previous patches).
I've also incorporated the NLS section posted by Jim (with a few minor
formatting/stylistic changes, for consistency's sake), and added a few refs
to his "See Also" section (thanks, Jim). [BTW, the "N" in NLS stands for
"Native", according to the gettext docs.]
Again, the patch for the VMS "lynx.hlp" file, is a straight, literal embed-
ding of the nroff output of the UNIX .man file. I know *nothing* about VMS,
so if some of the vars, etc. don't apply to that platform, it will take a
VMS'er to vet the file.
| > +"http", "ftp", "gopher" or "wais". Most gateway servers have been
| > +discontinued, but "http://www.w3.org:8001"; is available for wais searches
|
| Is it true that http://www.w3.org:8001 sometimes works? AFAIK it has
| been dead for a long time.
I've NO idea. Never had anything to do with wais, so I just axed the ref.
It's still in the INSTALLATION doc however, if someone's thinking about
cleaning up that doc ...
Thanks also to the other folks who made suggestions!
/kim
Against a clean 2.8.2dev.8:
diff -uNr lynx-2.8.2-dev.8.orig/src/LYPrint.c lynx-2.8.2-dev.8+kd/src/LYPrint.c
--- lynx-2.8.2-dev.8.orig/src/LYPrint.c Thu Dec 3 10:28:20 1998
+++ lynx-2.8.2-dev.8+kd/src/LYPrint.c Thu Dec 3 16:52:25 1998
@@ -1160,31 +1160,75 @@
printf(PRINTING_FILE);
#ifdef VMS
/*
- * Set document's title as a VMS logical. - FM
+ * Set various bits of document information as VMS logicals,
+ * for external PRINTER: cmd use. - KED
*/
StrAllocCopy(envbuffer, HText_getTitle());
if (!(envbuffer && *envbuffer))
StrAllocCopy(envbuffer, "No Title");
Define_VMSLogical("LYNX_PRINT_TITLE", envbuffer);
+
+ StrAllocCopy(envbuffer, newdoc->address);
+ if (!(envbuffer && *envbuffer))
+ StrAllocCopy(envbuffer, "No URL");
+ Define_VMSLogical("LYNX_PRINT_URL", envbuffer);
+
+ StrAllocCopy(envbuffer, HText_getDate());
+ if (!(envbuffer && *envbuffer))
+ StrAllocCopy(envbuffer, "No Date");
+ Define_VMSLogical("LYNX_PRINT_DATE", envbuffer);
+
+ StrAllocCopy(envbuffer, HText_getLastModified());
+ if (!(envbuffer && *envbuffer))
+ StrAllocCopy(envbuffer, "No LastMod");
+ Define_VMSLogical("LYNX_PRINT_LASTMOD", envbuffer);
#else
/*
- * Set document's title as an environment variable. - JKT
+ * Set various bits of document information as environment
+ * variables, for use by external print scripts/etc. We
+ * assume there are values, and leave NULL value checking
+ * up to the external PRINTER: cmd/script. - KED
*/
StrAllocCopy(envbuffer, "LYNX_PRINT_TITLE=");
StrAllocCat(envbuffer, HText_getTitle());
putenv(envbuffer);
+
+ StrAllocCopy(envbuffer, "LYNX_PRINT_URL=");
+ StrAllocCat(envbuffer, newdoc->address);
+ putenv(envbuffer);
+
+ StrAllocCopy(envbuffer, "LYNX_PRINT_DATE=");
+ StrAllocCat(envbuffer, HText_getDate());
+ putenv(envbuffer);
+
+ StrAllocCopy(envbuffer, "LYNX_PRINT_LASTMOD=");
+ StrAllocCat(envbuffer, HText_getLastModified());
+ putenv(envbuffer);
#endif /* VMS */
LYSystem(buffer);
#ifdef VMS
/*
- * Remove LYNX_PRINT_TITLE logical. - FM
+ * Remove the various LYNX_PRINT_xxxx logicals. - KED
*/
Define_VMSLogical("LYNX_PRINT_TITLE", "");
+ Define_VMSLogical("LYNX_PRINT_URL", "");
+ Define_VMSLogical("LYNX_PRINT_DATE", "");
+ Define_VMSLogical("LYNX_PRINT_LASTMOD", "");
#else
/*
- * Remove LYNX_PRINT_TITLE value from environment. - KW
+ * Remove the LYNX_PRINT_xxxx values from environment. - KED
+ * [could use unsetenv(), but don't know if it's portable]
*/
- envbuffer[17] = '\0'; /* truncate after '=' */
+ StrAllocCopy(envbuffer, "LYNX_PRINT_TITLE=");
+ putenv(envbuffer);
+
+ StrAllocCopy(envbuffer, "LYNX_PRINT_URL=");
+ putenv(envbuffer);
+
+ StrAllocCopy(envbuffer, "LYNX_PRINT_DATE=");
+ putenv(envbuffer);
+
+ StrAllocCopy(envbuffer, "LYNX_PRINT_LASTMOD=");
putenv(envbuffer);
#endif /* VMS */
FREE(envbuffer);
diff -uNr lynx-2.8.2-dev.8.orig/lynx.hlp lynx-2.8.2-dev.8+kd/lynx.hlp
--- lynx-2.8.2-dev.8.orig/lynx.hlp Fri Nov 6 06:29:41 1998
+++ lynx-2.8.2-dev.8+kd/lynx.hlp Wed Dec 9 11:07:38 1998
@@ -475,6 +475,271 @@
o Type "H" or "?" for online help and descriptions of key-stroke commands.
o Type "K" for a complete list of the current key-stroke command mappings.
+2 ENVIRONMENT
+ In addition to various "standard" environment variables
+ such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx uti-
+ lizes several Lynx-specific environment variables, if they
+ exist.
+
+ Others may be created or modified by Lynx to pass data to
+ an external program, or for other reasons. These are
+ listed separately below.
+
+ See also the sections on SIMULATED CGI SUPPORT and NATIVE
+ LANGUAGE SUPPORT, below.
+
+ Note: Not all environment variables apply to all types of
+ platforms supported by Lynx, though most do. Feedback on
+ platform dependencies is solicited.
+
+ Environment Variables Used By Lynx:
+
+ COLORTERM If set, color capability for the ter-
+ minal is forced on at startup time.
+ The actual value assigned to the vari-
+ able is ignored. This variable is
+ only meaningful if Lynx was built
+ using the slang screen-handling
+ library.
+
+ LYNX_CFG This variable, if set, will override
+ the default location and name of the
+ global configuration file (normally,
+ lynx.cfg) that was defined by the
+ LYNX_CFG_FILE constant in the
+ userdefs.h file, during installation.
+ See the userdefs.h file for more
+ information.
+
+ LYNX_LSS This variable, if set, specifies the
+ location of the default Lynx character
+ style sheet file. [Currently only
+ meaningful if Lynx was built using
+ experimental color style support.]
+
+ LYNX_SAVE_SPACE This variable, if set, will override
+ the default path prefix for files
+ saved to disk that is defined in the
+ lynx.cfg SAVE_SPACE: statement. See
+ the lynx.cfg file for more informa-
+ tion.
+
+ LYNX_TEMP_SPACE This variable, if set, will override
+ the default path prefix for temporary
+ files that was defined during instal-
+ lation, as well as any value that may
+ be assigned to the TMPDIR variable.
+
+ MAIL This variable specifies the default
+ inbox Lynx will check for new mail, if
+ such checking is enabled in the
+ lynx.cfg file.
+
+ NEWS_ORGANIZATION This variable, if set, provides the
+ string used in the Organization:
+ header of USENET news postings. It
+ will override the setting of the ORGA-
+ NIZATION environment variable, if it
+ is also set (and, on UNIX, the con-
+ tents of an /etc/organization file, if
+ present).
+
+ NNTPSERVER If set, this variable specifies the
+ default NNTP server that will be used
+ for USENET news reading and posting
+ with Lynx, via news: URL's.
+
+ ORGANIZATION This variable, if set, provides the
+ string used in the Organization:
+ header of USENET news postings. On
+ UNIX, it will override the contents of
+ an /etc/organization file, if present.
+
+ PROTOCOL_proxy Lynx supports the use of proxy servers
+ that can act as firewall gateways and
+ caching servers. They are preferable
+ to the older gateway servers (see
+ WWW_access_GATEWAY, below). Each pro-
+ tocol used by Lynx, (http, ftp,
+ gopher, etc), can be mapped separately
+ by setting environment variables of
+ the form PROTOCOL_proxy (literally:
+ http_proxy, ftp_proxy, gopher_proxy,
+ etc), to
+ "http://some.server.dom:port/";. See
+ the INSTALLATION file in the Lynx dis-
+ tribution for additional details, and
+ examples.
+
+ WWW_access_GATEWAY Lynx still supports use of gateway
+ servers, with the servers specified
+ via "WWW_access_GATEWAY" variables
+ (where "access" is lower case and can
+ be "http", "ftp", "gopher" or "wais"),
+ however most gateway servers have been
+ discontinued. Note that you do not
+ include a terminal '/' for gateways,
+ but do for proxies specified by PROTO-
+ COL_proxy environment variables. See
+ the INSTALLATION file in the Lynx dis-
+ tribution for details.
+
+ WWW_HOME This variable, if set, will override
+ the default startup URL specified in
+ any of the Lynx configuration files.
+
+ Environment Variables Set or Modified By Lynx:
+
+ LYNX_PRINT_DATE This variable is set by the Lynx
+ p(rint) function, to the Date: string
+ seen in the document's "Information
+ about" page (= cmd), if any. It is
+ created for use by an external pro-
+ gram, as defined in a lynx.cfg
+ PRINTER: definition statement. If the
+ field does not exist for the document,
+ the variable is set to a null string
+ under UNIX, or "No Date" under VMS.
+
+ LYNX_PRINT_LASTMOD This variable is set by the Lynx
+ p(rint) function, to the Last Mod:
+ string seen in the document's "Infor-
+ mation about" page (= cmd), if any.
+ It is created for use by an external
+ program, as defined in a lynx.cfg
+ PRINTER: definition statement. If the
+ field does not exist for the document,
+ the variable is set to a null string
+ under UNIX, or "No LastMod" under VMS.
+
+ LYNX_PRINT_TITLE This variable is set by the Lynx
+ p(rint) function, to the Linkname:
+ string seen in the document's "Infor-
+ mation about" page (= cmd), if any.
+ It is created for use by an external
+ program, as defined in a lynx.cfg
+ PRINTER: definition statement. If the
+ field does not exist for the document,
+ the variable is set to a null string
+ under UNIX, or "No Title" under VMS.
+
+ LYNX_PRINT_URL This variable is set by the Lynx
+ p(rint) function, to the URL: string
+ seen in the document's "Information
+ about" page (= cmd), if any. It is
+ created for use by an external pro-
+ gram, as defined in a lynx.cfg
+ PRINTER: definition statement. If the
+ field does not exist for the document,
+ the variable is set to a null string
+ under UNIX, or "No URL" under VMS.
+
+ LYNX_VERSION This variable is always set by Lynx,
+ and may be used by an external program
+ to determine if it was invoked by
+ Lynx. See also the comments in the
+ distribution's sample mailcap file,
+ for notes on usage in such a file.
+
+ TERM Normally, this variable is used by
+ Lynx to determine the terminal type
+ being used to invoke Lynx. If, how-
+ ever, it is unset at startup time (or
+ has the value "unknown"), or if the
+ -term command-line option is used (see
+ OPTIONS section above), Lynx will set
+ or modify its value to the user speci-
+ fied terminal type (for the Lynx exe-
+ cution environment). Note: If
+ set/modified by Lynx, the values of
+ the LINES and/or COLUMNS environment
+ variables may also be changed.
+
+2 SIMULATED CGI SUPPORT
+ If built with the cgi-links option enabled, Lynx allows
+ access to a cgi script directly without the need for an
+ http daemon.
+
+ When executing such "lynxcgi scripts" (if enabled), the
+ following variables may be set for simulating a CGI envi-
+ ronment:
+
+ CONTENT_LENGTH
+
+ CONTENT_TYPE
+
+ DOCUMENT_ROOT
+
+ HTTP_ACCEPT_CHARSET
+
+ HTTP_ACCEPT_LANGUAGE
+
+ HTTP_USER_AGENT
+
+ PATH_INFO
+
+ PATH_TRANSLATED
+
+ QUERY_STRING
+
+ REMOTE_ADDR
+
+ REMOTE_HOST
+
+ REQUEST_METHOD
+
+ SERVER_SOFTWARE
+
+ Other environment variables are not inherited by the
+ script, unless they are provided via a LYNXCGI_ENVIRONMENT
+ statement in the configuration file. See the lynx.cfg
+ file, and the (draft) CGI 1.1 Specification
+ <http://Web.Golux.Com/coar/cgi/draft-coar-cgi-v11-00.txt>
+ for the definition and usage of these variables.
+
+ The CGI Specification, and other associated documentation,
+ should be consulted for general information on CGI script
+ programming.
+
+2 NATIVE LANGUAGE SUPPORT
+ If configured and installed with Native Language Support,
+ Lynx will display status and other messages in your local
+ language. See the file ABOUT_NLS in the source distribu-
+ tion, or at your local GNU site, for more information
+ about internationalization.
+
+ The following environment variables may be used to alter
+ default settings:
+
+ LANG This variable, if set, will override
+ the default message language. It is
+ an ISO 639 two-letter code identifying
+ the language. Language codes are NOT
+ the same as the country codes given in
+ ISO 3166.
+
+ LANGUAGE This variable, if set, will override
+ the default message language. This is
+ a GNU extension that has higher prior-
+ ity for setting the message catalog
+ than LANG or LC_ALL.
+
+ LC_ALL and
+
+ LC_MESSAGES These variables, if set, specify the
+ notion of native language formatting
+ style. They are POSIXly correct.
+
+ LINGUAS This variable, if set prior to config-
+ uration, limits the installed lan-
+ guages to specific values. It is a
+ space-separated list of two-letter
+ codes. Currently, it is hard-coded to
+ a wish list.
+
+ NLSPATH This variable, if set, is used as the
+ path prefix for message catalogs.
+
2 NOTES
This is the Lynx v2.8.1 Release
@@ -489,6 +754,10 @@
Unsubscribe by sending email to <address@hidden> with
"unsubscribe lynx-dev" as the only line in the body of your message.
Do not send the unsubscribe message to the lynx-dev list, itself.
+
+2 SEE ALSO
+ environ(7), execve(2), ftp(1), gettext(GNU), locale-
+ conv(3), setlocale(3), termcap(5), terminfo(5), wget(GNU)
2 ACKNOWLEDGMENTS
Lynx has incorporated code from a variety of sources along the way.
diff -uNr lynx-2.8.2-dev.8.orig/lynx.man lynx-2.8.2-dev.8+kd/lynx.man
--- lynx-2.8.2-dev.8.orig/lynx.man Tue Oct 27 18:08:12 1998
+++ lynx-2.8.2-dev.8+kd/lynx.man Wed Dec 9 11:02:52 1998
@@ -548,6 +548,222 @@
.br
o Type \fB"K"\fR for a complete list of the current key-stroke
command mappings.
+.SH ENVIRONMENT
+In addition to various "standard" environment variables such as
+\fBHOME\fR, \fBPATH\fR, \fBUSER\fR, \fBDISPLAY\fR, \fBTMPDIR\fR, \fBetc\fR,
+\fILynx\fR utilizes several Lynx-specific environment variables, if they
+exist.
+.PP
+Others may be created or modified by \fILynx\fR to pass data to an external
+program, or for other reasons. These are listed separately below.
+.PP
+See also the sections on \fBSIMULATED CGI SUPPORT\fR and
+\fBNATIVE LANGUAGE SUPPORT\fR, below.
+.PP
+Note: Not all environment variables apply to all types of platforms
+supported by \fILynx\fR, though most do. Feedback on platform
+dependencies is solicited.
+.PP
+Environment Variables Used By \fILynx\fR:
+.TP 20
+.B COLORTERM
+If set, color capability for the terminal is forced on at startup time.
+The actual value assigned to the variable is ignored. This variable is
+only meaningful if \fILynx\fR was built using the \fBslang\fR
+screen-handling library.
+.TP 20
+.B LYNX_CFG
+This variable, if set, will override the default location and name of
+the global configuration file (normally, \fBlynx.cfg\fR) that was defined
+by the LYNX_CFG_FILE constant in the userdefs.h file, during installation.
+See the userdefs.h file for more information.
+.TP 20
+.B LYNX_LSS
+This variable, if set, specifies the location of the default \fILynx\fR
+character style sheet file. [Currently only meaningful if \fILynx\fR was
+built using experimental color style support.]
+.TP 20
+.B LYNX_SAVE_SPACE
+This variable, if set, will override the default path prefix for files
+saved to disk that is defined in the \fBlynx.cfg SAVE_SPACE:\fR statement.
+See the \fBlynx.cfg\fR file for more information.
+.TP 20
+.B LYNX_TEMP_SPACE
+This variable, if set, will override the default path prefix for temporary
+files that was defined during installation, as well as any value that may
+be assigned to the \fBTMPDIR\fR variable.
+.TP 20
+.B MAIL
+This variable specifies the default inbox \fILynx\fR will check for new
+mail, if such checking is enabled in the \fBlynx.cfg\fR file.
+.TP 20
+.B NEWS_ORGANIZATION
+This variable, if set, provides the string used in the \fBOrganization:\fR
+header of \fBUSENET\fR news postings. It will override the setting of the
+ORGANIZATION environment variable, if it is also set (and, on \fBUNIX\fR,
+the contents of an /etc/organization file, if present).
+.TP 20
+.B NNTPSERVER
+If set, this variable specifies the default NNTP server that will be used
+for \fBUSENET\fR news reading and posting with \fILynx\fR, via news: URL's.
+.TP 20
+.B ORGANIZATION
+This variable, if set, provides the string used in the \fBOrganization:\fR
+header of \fBUSENET\fR news postings. On \fBUNIX\fR, it will override the
+contents of an /etc/organization file, if present.
+.TP 20
+.B PROTOCOL_proxy
+\fILynx\fR supports the use of proxy servers that can act as firewall
+gateways and caching servers. They are preferable to the older gateway
+servers (see WWW_access_GATEWAY, below). Each protocol used by \fILynx\fR,
+(http, ftp, gopher, etc), can be mapped separately by setting environment
+variables of the form PROTOCOL_proxy (literally: http_proxy, ftp_proxy,
+gopher_proxy, etc), to "http://some.server.dom:port/";.
+See the \fBINSTALLATION\fR file in the \fILynx\fR distribution for additional
+details, and examples.
+.TP 20
+.B WWW_access_GATEWAY
+\fILynx\fR still supports use of gateway servers, with the servers specified
+via "WWW_access_GATEWAY" variables (where "access" is lower case and can be
+"http", "ftp", "gopher" or "wais"), however most gateway servers have been
+discontinued. Note that you do not include a terminal '/' for gateways, but
+do for proxies specified by PROTOCOL_proxy environment variables.
+See the \fBINSTALLATION\fR file in the \fILynx\fR distribution for details.
+.TP 20
+.B WWW_HOME
+This variable, if set, will override the default startup URL specified
+in any of the \fILynx\fR configuration files.
+.PP
+Environment Variables \fBSet\fR or \fBModified\fR By \fILynx\fR:
+.TP 20
+.B LYNX_PRINT_DATE
+This variable is set by the \fILynx\fR p(rint) function, to the
+\fBDate:\fR
+string seen in the document's "\fBInformation about\fR" page (= cmd),
+if any.
+It is created for use by an external program, as defined in a
+\fBlynx.cfg PRINTER:\fR definition statement.
+If the field does not exist for the document, the variable is set to a
+null string under \fBUNIX\fR, or "No Date" under \fBVMS\fR.
+.TP 20
+.B LYNX_PRINT_LASTMOD
+This variable is set by the \fILynx\fR p(rint) function, to the
+\fBLast Mod:\fR
+string seen in the document's "\fBInformation about\fR" page (= cmd),
+if any.
+It is created for use by an external program, as defined in a
+\fBlynx.cfg PRINTER:\fR definition statement.
+If the field does not exist for the document, the variable is set to a
+null string under \fBUNIX\fR, or "No LastMod" under \fBVMS\fR.
+.TP 20
+.B LYNX_PRINT_TITLE
+This variable is set by the \fILynx\fR p(rint) function, to the
+\fBLinkname:\fR
+string seen in the document's "\fBInformation about\fR" page (= cmd),
+if any.
+It is created for use by an external program, as defined in a
+\fBlynx.cfg PRINTER:\fR definition statement.
+If the field does not exist for the document, the variable is set to a
+null string under \fBUNIX\fR, or "No Title" under \fBVMS\fR.
+.TP 20
+.B LYNX_PRINT_URL
+This variable is set by the \fILynx\fR p(rint) function, to the
+\fBURL:\fR
+string seen in the document's "\fBInformation about\fR" page (= cmd),
+if any.
+It is created for use by an external program, as defined in a
+\fBlynx.cfg PRINTER:\fR definition statement.
+If the field does not exist for the document, the variable is set to a
+null string under \fBUNIX\fR, or "No URL" under \fBVMS\fR.
+.TP 20
+.B LYNX_VERSION
+This variable is always set by \fILynx\fR, and may be used by an external
+program to determine if it was invoked by \fILynx\fR. See also the comments
+in the distribution's sample \fBmailcap\fR file, for notes on usage in such
+a file.
+.TP 20
+.B TERM
+Normally, this variable is used by \fILynx\fR to determine the terminal type
+being used to invoke \fILynx\fR. If, however, it is unset at startup time
+(or has the value "unknown"),
+or if the \fB-term\fR command-line option is used (see \fBOPTIONS\fR section
+above), \fILynx\fR will set or modify its value to the user specified
+terminal type (for the \fILynx\fR execution environment).
+Note: If set/modified by \fILynx\fR, the values of the \fBLINES\fR and/or
+\fBCOLUMNS\fR environment variables may also be changed.
+.SH SIMULATED CGI SUPPORT
+If built with the \fBcgi-links\fR option enabled, \fILynx\fR allows access
+to a cgi script directly without the need for an http daemon.
+.PP
+When executing such "lynxcgi scripts" (if enabled), the following variables
+may be set for simulating a CGI environment:
+.PP
+.B CONTENT_LENGTH
+.PP
+.B CONTENT_TYPE
+.PP
+.B DOCUMENT_ROOT
+.PP
+.B HTTP_ACCEPT_CHARSET
+.PP
+.B HTTP_ACCEPT_LANGUAGE
+.PP
+.B HTTP_USER_AGENT
+.PP
+.B PATH_INFO
+.PP
+.B PATH_TRANSLATED
+.PP
+.B QUERY_STRING
+.PP
+.B REMOTE_ADDR
+.PP
+.B REMOTE_HOST
+.PP
+.B REQUEST_METHOD
+.PP
+.B SERVER_SOFTWARE
+.PP
+Other environment variables are not inherited by the script, unless they
+are provided via a LYNXCGI_ENVIRONMENT statement in the configuration file.
+See the \fBlynx.cfg\fR file, and the (draft) CGI 1.1 Specification
+<http://Web.Golux.Com/coar/cgi/draft-coar-cgi-v11-00.txt> for the
+definition and usage of these variables.
+.PP
+The CGI Specification, and other associated documentation, should be consulted
+for general information on CGI script programming.
+.SH NATIVE LANGUAGE SUPPORT
+If configured and installed with \fBNative Language Support\fR, \fILynx\fR
+will display status and other messages in your local language. See the
+file \fBABOUT_NLS\fR in the source distribution, or at your local \fBGNU\fR
+site, for more information about internationalization.
+.PP
+The following environment variables may be used to alter default settings:
+.TP 20
+.B LANG
+This variable, if set, will override the default message language. It
+is an \fBISO 639\fR two-letter code identifying the language. Language
+codes are \fBNOT\fR the same as the country codes given in \fBISO 3166\fR.
+.TP 20
+.B LANGUAGE
+This variable, if set, will override the default message language.
+This is a \fBGNU\fR extension that has higher priority for setting
+the message catalog than \fBLANG\fR or \fBLC_ALL\fR.
+.TP 20
+.B LC_ALL
+and
+.TP 20
+.B LC_MESSAGES
+These variables, if set, specify the notion of native language
+formatting style. They are \fBPOSIXly\fR correct.
+.TP 20
+.B LINGUAS
+This variable, if set prior to configuration, limits the installed
+languages to specific values. It is a space-separated list of two-letter
+codes. Currently, it is hard-coded to a wish list.
+.TP 20
+.B NLSPATH
+This variable, if set, is used as the path prefix for message catalogs.
.SH NOTES
This is the Lynx v2.8.1 Release
.PP
@@ -562,6 +778,16 @@
Unsubscribe by sending email to <address@hidden> with
"unsubscribe lynx-dev" as the only line in the body of your message.
Do not send the unsubscribe message to the lynx-dev list, itself.
+.SH SEE ALSO
+\fIenviron\fR(7),
+\fIexecve\fR(2),
+\fIftp\fR(1),
+\fIgettext\fR(GNU),
+\fIlocaleconv\fR(3),
+\fIsetlocale\fR(3),
+\fItermcap\fR(5),
+\fIterminfo\fR(5),
+\fIwget\fR(GNU)
.SH ACKNOWLEDGMENTS
Lynx has incorporated code from a variety of sources along the way.
The earliest versions of Lynx included code from Earl Fogel of Computing
##--eof--##