Le Thu, Oct 02, 2008 at 09:53:17AM +0900, Atsuhito Kohda a écrit :
>
> -assume_charset=utf-8 fixed the problem with the current
> lynx-cur.
>
> I checked both lynx (2.8.5-2sarge2.2) and lynx (2.8.6-2)
> but they didn't provide any extra setting for ASSUME_CHARSET
> so I'm puzzled very much now.
Hi Charles,
On Mon, 29 Sep 2008 19:34:04 +0900 (JST), Atsuhito Kohda wrote:
> Okay, as I have so little knowledge on mojibake for french,
> I'll forward this to the upstream.
I noticed that discussions with you and Thomas were not
delivered to me and now I believe the main point is;
> I have th
On Mon, 29 Sep 2008 14:38:03 +0900, Charles Plessy wrote:
> Le Fri, Sep 26, 2008 at 01:19:37PM +0900, Atsuhito Kohda a écrit :
> >
> > Do you set CHARACTER_SET:utf-8 somewhere or with "Options Menu"?
> > If not, I'd like to know if the above setting fixes the problem
> > or not.
(snip)
> In the
Le Fri, Sep 26, 2008 at 01:19:37PM +0900, Atsuhito Kohda a écrit :
>
> Do you set CHARACTER_SET:utf-8 somewhere or with "Options Menu"?
> If not, I'd like to know if the above setting fixes the problem
> or not.
Hi,
I added it in /etc/lynx-cur/local.cfg, and as a result I get this:
anx159《tmp》
Hi Charles, and sorry for such delay.
On Mon, 15 Sep 2008 16:10:38 +0900, Charles Plessy wrote:
> I have severe problems when converting HTML messages with Lynx while
> using Mutt, and it seems to me that the reason is that the output
> encoding is broken. Here is a simple example:
Do you set CH
5 matches
Mail list logo
