lynx-dev
[Top][All Lists]
Advanced

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

Re: lynx-dev Tweaking LYNX


From: pAb-032871
Subject: Re: lynx-dev Tweaking LYNX
Date: Sun, 21 May 2000 02:54:17 -0700

In "lynx-dev Tweaking LYNX"
[20/May/2000 Sat 21:06:54]
Bob Izenberg wrote:

> [ Message from un-subscribed address address@hidden forwarded by
> moderator ]

A suggestion for this item:

> > -)      Because the screen is so small, we need to optimize the space used
> > in the browser.  However, it seems that the body of each HTML page is padded
> > with 3 spaces to the left and 5 spaces to the right.  This cuts a viewable
> > line from 20 chars to 12.   I've also looked through config files and code
> > but cannot seem to find the place that pads the page.
> > 
> > If anyone has a hint of what to do or where to look to tweak LYNX in this
> > way and environment, I would appreciate it.  Thanks.


Right.  I'm guessing your pages are purely local, and the Lynx
you have installed doen't interact with the web [there are VERY
few pages written for a 20x16-char screen].

One advantage is that you have a great deal of control over the
content of these pages, and can modify the HTML instead of tweaking
Lynx itself.

Lynx doesn't pad text inside a <PRE></PRE> block, so if you write
your HTML in PRE, hard-wrapping to 20-chars width, the pages should
work out okay.  This actually makes the authoring of these pages
simpler because you don't have to bother with <BR> and <P> tags:
actual carriage returns [or newlines, or DOS CR+LF line-breaks]
in the source will be shown instead of ignored.

Disadvantages:

1) - Lynx does a poor job of soft-wrapping text in PRE, "brea
     king" words at the end of each line [v2.7.1 did anyway], so
     you will need to hard-wrap your HTML text to the desired
     width.
1a)- Hard-wrapping might get a little tricky, because you want
     to wrap only VISIBLE characters to 20 cols and not wrap the
     ones inside HTML tags.

2) - Lynx renders ALL line-breaks inside a PRE block, even the
     ones you'd rather have it ignore.  You can "hide" returns
     inside a tag however, so this:

<PRE>Some <A HREF="/nowhere_special.html"
>text</A>.</PRE>

     will be rendered as:

Some text.

with "text" as a link to "nowhere_special.html"


Can't do much for you with regard to the other problems, but I
wish you luck.  Hope this suggestion proves useful to you.


                    Patrick
          <mailto:address@hidden>
 

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

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