Re: LYNX-DEV ac81 chartrans problems

[Leonid Pauzner]

Klaus,
your workaround isn't good looking,
since user should to do things manually and keep in mind all this staff.
I may still live without this, but my proposal was obvious:
just to remove META charset (if any) from the printing output.



> 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.
> > >
[...]
>
> 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.
;