Re: LYNX-DEV differences in 2.7

[Foteos Macrides]

Mark Westergaard <address@hidden> wrote:
>We noticed two differences between 2.6 and 2.7.  We run AIX 4.1 and 4.2. 
>I didn't see any discussion of these yet, but the first may have been
>covered in the discussion of bookmarks.
>
>Several of our folks reported that they couldn't open their bookmarks
>file.  I found that they had specified a full path instead of a
>relative path, which seems to be okay in 2.6:
>
>       bookmark_file=/home/username/lynx_bookmarks.html

        Yes.  As of v2.7, the bookmark files must be defined relative
to the home directory.  If in a subdirectory off home, the path must
begin with a dot-slash ("./"), for both Unix and VMS.  See the v2.7
lynx.cfg, and/or online 'h'elp, for more information.

        You also need this patch:

   Linkname: LYNX-DEV Update patch for the v2.7 LYMainLoop.c
        URL: http://www.flora.org/lynx-dev/html/month0297/msg00602.html

for the "historical" behavior of recognizing and handling a bookmark
file as such when accessed as a startfile URL (rather than via the -book
switch) to work when the bookmark file is in home, rather than in a
subdirectory off home (though, since you now can have up the 26 bookmark
files, it's anticipated that people will start putting their Lynx bookmark
file set in a subdirectory).


>We also had reports of problems with links that used to work.  It turns
>out the URLs had spaces in them.  For example, one of the reported pages 
>uses anchors like: 
>
>       <a href="#part 1">Part 1</a>
>        ...
>       <a name="part 1">...
>
>2.6 shows the link as "...#part 1" and 2.7 shows it as "...#part1".
>
>2.7 has been a big plus for us -- especially the cookie support.  

        White space is invalid in NAME attribute values, and should be
hex escaped in HREF attribute values that correspond to partial or
absolute URLs.  You've been relying on invalid behavior by earlier
versions of Lynx, and should correct your markup.

        Lynx v2.7 still does not require hex escaping of spaces (%20)
in HREF attribute values that correspond to lynxexec or lynxprog URLs,
but if you have such links in your pages, you should start correcting
those as well.  In all other cases, v2.7 assumes the spaces were
introduced by a wrap in the markup, and collapses them.

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;