lynx-dev
[Top][All Lists]
Advanced

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

Re: LYNX-DEV Re: MIME charset headers for mail


From: Klaus Weide
Subject: Re: LYNX-DEV Re: MIME charset headers for mail
Date: Sun, 13 Apr 1997 16:14:20 -0500 (CDT)

On Sun, 13 Apr 1997, Hynek Med wrote:

> OK, here's a patch that will make lynx add MIME headers for mailto: and
> printing via "Mail the file". It also adds "Content-Transfer-Encoding:
> 8bit" for printing HMTL documents via "Mail the file", and X-Mailer: 
> Lynx.. for this printing. It doesn't do the checks Klaus suggested - yet,
> and it doesn't take VMS into account.
> 
> BTW, Klaus, the printing of HTML source has something like
> 
>                     fprintf(outfile_fp, "Content-Type: text/html");
>                     if (HTLoadedDocumentCharset() != NULL) {
>                         fprintf(outfile_fp, "; charset=%s\n",
>                                             HTLoadedDocumentCharset());
>                     } else {
>                         fprintf(outfile_fp, "\n");
>                     }
> 
> Is this enough in the current chartrans patches context?

No, it isn't...

The HTLoadedDocumentCharset() returns only the original charset, and only
if it was explicitly given.  Since the document has been translated at the
point when it is mailed, this will be wrong if the display character set
differs from the original charset.

This would already give the wrong result in Lynx code without chartrans,
if the document was labelled with "charset=iso-8859-1" and 8-bit
characters were translated to some display character set where they are
different.

But if you change it (make it like for non-source mail), a charset given
in a META tage which was right before may now become wrong... Sigh.
Well there are good reasons for keeping meta-information *outside*
of a document...

  Klaus

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

reply via email to

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