lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Re: lynx2.8.2dev.16


From: Leonid Pauzner
Subject: Re: lynx-dev Re: lynx2.8.2dev.16
Date: Tue, 9 Feb 1999 00:54:12 +0300 (MSK)

8-Feb-99 09:43 Kim DeVaughn wrote:
> On Mon, Feb 08, 1999, Jacob Poon (address@hidden) said:
> |
| >>   3. Replaces any embedded control chars with something printable
> |
> | This may cause trouble with multibyte encoded characters.  UCS-2, UCS-4,
> | and UTF-16 are affected by it.  But since Lynx does not support these
> | encodings (yet), these problem are not pervalent.  Nevertheless, the
> | documentation should issue a warning to people who want to add support for
> | the encodings in question, or when using external editors that depends on
> | unsupported encodings.

> From what I've seen of lynx's internals, supporting such multibyte char
> encodings would require huge changes in (most) all parts of the code.
Yes.

> However, I'll add a comment about it in the cited code to that effect,
> in a cleanup patch that I'm working on.

> I dunno the best place to document that "limitation" overall though ..
> .. perhaps in the README and/or ABOUT-NLS file(s).  Or maybe there

The proper place for this info seems an options help, the "editor" section
like this:

diff -u old/option_help.html ./option_help.html
--- old/option_help.html    Mon Jan 18 19:08:44 1999
+++ ./option_help.html      Tue Feb  9 00:44:32 1999
@@ -55,12 +55,16 @@
 <H1><A NAME="CK">Cookies</A></H1>

 This can be set to accept or reject all cookies or to ask each time.
-See the Users Guide (under `h'elp) for details of cookie usage.
+See the Users Guide for details of <A HREF="../Lynx_users_guide.html#Cookies"
+>cookie usage</A>.

 <H1><A NAME="ED">Editor</A></H1>

-If non-empty, it defines the editor to spawn when editing a local file
-or sending mail.  Any valid text editor may be entered here.
+The editor to be invoked when editing browsable files,
+sending mail or comments, or filling form's textarea (multiline input field).
+The full pathname of the editor command should be specified when possible.
+It is assumed the text editor supports the same character set
+you have for "display character set" in Lynx.

 <H1><A NAME="EM">Emacs keys</A></H1>

@@ -286,8 +290,10 @@

 <H1><A NAME="DV">X DISPLAY variable</A></H1>

-If non-empty, it specifies your <A HREF="xterm_help.html">X terminal</A>
-display address.
+This option is only relevant to X Window users, it specifies
+The DISPLAY (Unix) or DECW$DISPLAY (VMS) variable is picked up
+automatically from the environment if it has been previously set.


> should be some kind of INTERNALS file, for documenting such things
> (which would also include things about var/fn() naming conventions,
> macro usage (eg, FREE() vs. free()), "style, coding conventions, and
> the like).

> /kim



reply via email to

[Prev in Thread] Current Thread [Next in Thread]