Re: Chinese characters are not displayed when using charset gb2312/euc-cn

Thomas Dickey <[email protected]>
Newsgroups gmane.comp.web.lynx.devel
Message-ID <[email protected]>
On Tue, Jun 29, 2021 at 05:12:20PM -0400, Thomas Dickey wrote:
> On Mon, Jun 21, 2021 at 05:09:53PM +0200, Cédric Hannotier via Lynx-dev wrote:
> > Hi all,
> > 
> > I got an HTML email with gb3212 charset.
> s/3232/2312/
> 
> > It seems that lynx is unable to print some characters.
> 
> yes... I see that the problem is that lynx's conversion of euc-cn to utf-8
> is incomplete.  This is not a new issue as you can see here:
> 
> https://lists.nongnu.org/archive/cgi-bin/namazu.cgi?query=gb2312&submit=Search%21&idxname=lynx-dev&max=20&result=normal&sort=date%3Alate
> 
> > Changing the declared charset to euc-cn gives the same result.
> 
> gb2312 is equated to euc-cn internally.
> 
> > Using another browser works (qutebrowser).
> > First converting that file to utf-8 (using iconv) also works.
> 
> yes, lynx uses iconv after organizing the characters :-)
>  
> > Lynx build is from Debian testing:
> > 
> > Lynx Version 2.9.0dev.6 (05 Sep 2020)

I had some time today (which I'd intended working on another feature for lynx),
and implemented this as an experimental feature (which the packager may adopt
in dev.7 -- when I finish that other feature).

see

https://github.com/ThomasDickey/lynx-snapshots/commit/5111b5306b278cecb0b66166eb8338072fc713c6

-- 
Thomas E. Dickey <[email protected]>
https://invisible-island.net
ftp://ftp.invisible-island.net

_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
signature.asc (application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQTFIEjAwHSP7iJ9R6JwI1Pg9+SO2wUCYN0BhwAKCRBwI1Pg9+SO
2+6BAKDCtVdErxVDmxeLMQjVxAyMzqjtzgCfcXfY+r4566/x2LBSXZexzmCWQ6k=
=K4R+
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.