Re: lynx-dev bookmarks encoding

[Leonid Pauzner]

12-May-2003 18:37 Ilya Zakharevich wrote:
> Currently lynx

> a) creates the bookmark file with a "random" encoding (encoding of the
>    current doc or somesuch);

Not "random". Lynx create a bookmark file with "display charset" ecoding,
and writes the appropriate META header.

> b) writes bookmarks to the file in a "random" encoding.

also in "display charset".

> Why not write all the ascii entities in ascii, and the rest via &FOO;
> numeric escapes?

In this case the bookmark file will hardly be edited by hand,
so this is not a default behaviour.  If you change display charset
frequently (or automatically), there is a lynx.cfg flag (since 1998):


# NCR_IN_BOOKMARKS:TRUE allows you to save 8-bit characters in bookmark titles
# in the unicode format (NCR).  This may be useful if you need to switch
# display charsets frequently.  This is the case when you use Lynx on different
# platforms, e.g., on UNIX and from a remote PC, and want to keep the bookmarks
# file persistent.
# Another aspect is compatibility:  NCR is part of I18N and HTML4.0
# specifications supported starting with Lynx 2.7.2, Netscape 4.0 and MSIE 4.0.
# Older browser versions will fail so keep NCR_IN_BOOKMARKS:FALSE if you
# plan to use them.
#
#NCR_IN_BOOKMARKS:FALSE



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