lynx-dev
[Top][All Lists]
Advanced

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

Re: lynx-dev some proposed nit fixes in lynx.cfg


From: Larry W. Virden
Subject: Re: lynx-dev some proposed nit fixes in lynx.cfg
Date: Sat, 7 Nov 1998 18:20:48 -0500 (EST)

From: Doug Kaufman <address@hidden>

> Many changes here go from correct grammar to less correct
> formulations. I believe that following changes should not be

> On Sat, 7 Nov 1998, Larry W. Virden wrote:
> 
> > --- lynx.cfg-dist   Fri Nov  6 09:29:41 1998
> > +++ lynx.cfg-new    Sat Nov  7 11:07:49 1998
> > -# trailing white space will be trimmed, and a single space added by Lynx
> > +# trailing white space will be trimmed, and a single space is added by Lynx
> > ...

I disagree that was correct originally.

> > -# their actual URL's.  See the sample jumps files in the samples
> > +# their actual URL's.  See the jumps files in the lynx*/samples

In this case, URL's should be URLs.  Sorry - I started to make that change
(as well as a pass thru fixing all the incorrect uses of it's) and got
sidetracked by the kids needing to leave.  I also disagree that saying
sample jumps files in the samples directory is better than saying the
jumps files in the lynx*/samples directory.

> > ...
> > -# Additional, alternate jumps files can be defined and mapped to
> > +# Additional alternate jumps files can be defined and mapped to

My college English book indicated the comma in this case was a coin toss...

> > -# CHARACTER_SET defines the display character set, i.e., that assumed to be
> > +# CHARACTER_SET defines the display character set, i.e., assumed to be

I can't fathom how that "that" can be correct.

> The following need to be "Raw (CJK)" rather than "Raw CJK"

That's fine - trying to change the original "raw or CJK mode" was what I
was addressing.

> More lines that shouldn't be changed.
> 
> > -# that cpXXX codepages used by IBM PC compatible computers, and 
> > windows-xxxx
> > -# used by native MS-Windows apps.  We also note that cpXXX pages rerely 
> > found
> > -# on Internet but mostly for local needs on DOS.
> > +# the cpXXX codepages used by IBM PC compatible computers, and windows-xxxx
> > +# used by native MS-Windows apps.  We also note that cpXXX pages rarely are
> > ...
> > -# the sending of an unacceptable response is also allowed." (RFC2068) 
> > +# the sending of an unacceptable response is also allowed.  See RFC2068.

Hey!  Those quotation marks were removed before me - I just wanted to make
that RFC2068 a bit clearer.  Shrug.

> > -# Local execution links and scripts are completely disabled
> > -# in the source code unless they are enabled in the
> > -# userdefs.h file and the sources recompiled.  Please
> > -# see the Lynx source code distribution and the userdefs.h
> > +# Local execution links and scripts are by default completely disabled
> > +# unless a change is made to the userdefs.h file to enabled them.
> > +# See the Lynx source code distribution and the userdefs.h

Tom, if you don't like my wording, please consider reworking
the original wording, which was so torturous that even a native English
speaker had to reread it several times to figure out the point of the
lines.

> I think that this might be better as "It must be specified relative to
> the user's home directory"

That's how I started to write it - but I had just worked thru the META CHARSET
section and thought using the words prepended might be a bit easy for the
novice reader to figure out than the idea of relative pathnames.  Either
way works fine for me.

> > -#       an unknown editor that they can't get out of.  Users can
> > +#       an unknown editor that they can't exit.  Users can
> 
> This might be better as "an unknown editor from which they can't exit"

Good point - I should have caught that one myself.  Those "that" phrases
usually catch my attention but somehow escaped me this time.

> > -# seeking a valid '-->' terminator (note that white space can be present
> > +# seeking a valid '-->' terminator (white space can be present
> >  # between the '--' and '>' in valid terminators).  The compilation default

the original seemed too wordy too me - I don't see a change in meaning by
using less words.
-- 
Larry W. Virden                 INET: address@hidden
<URL:http://www.purl.org/NET/lvirden/> <*> O- "We are all Kosh."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.

reply via email to

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