Re: LYNX-DEV ac81 chartrans problems

[Klaus Weide]

On Tue, 14 Oct 1997, Leonid Pauzner wrote:

> > > 3) if I "print" the html source to local file,
> > > it saves in "current display charset",
> > > but META charset (if exist on the page) not changed.
> > > Therefore later I got messed up html file.
> >
> > Yes.  You have to change it by hand.
> > Of course if people would specify the charset in the HTTP header where it
> > belongs, instead of a META tag which is just a hack, this problem wouldn't
> > occur in this form...
> >
> > I have an idea how do work around that.  It probably won't be perfect.
> >
> > It's just a fact of life that, if you copy a HTML document to your local
> > disk, not everything will work as in the original context.  Especially
> > if you use 'P' instead of 'D'.  Another thing that needs adjustment after

Leonid,

  please try the following:

Decide on some new suffixes (file extensions) to use for files in specific
character encodings.  For example

   text/html;charset=koi8-r     k8html 
   text/plain;charset=koi8-r    k8txt
   text/html;charset=cp866      althtml 
   ...

Add these to your mime.types file or (in the appropriate SUFFIX syntax)
to your lynx.cfg.  (For DOS there obviously is a problem with the 8+3
filename restriction,  but it should also work for your Lynx386 version
if you make up short suffixes.)

Then when you save a file from the 'P'rint menu, change the proposed
filename to give it the right suffix.

When you later access the file with lynx, the explicit charset from the
suffix should override any charset from META (it is stronger, like charset
from HTTP headers is stronger).

This is nothing new, so it should work with your last Lynx386 binary.

        Klaus

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;