Re: I'd like to add Chiese/Japnese/Korea support to elinks

Kalle Olavi Niemitalo <[email protected]>
Newsgroups gmane.comp.web.links
Message-ID <[email protected]>
"ablo" <[email protected]> writes:

> I found that elinks is a good text browser, but it does not
> support good of Chiese languase. So I'd like to join the
> development team and want to make it more comfortable of
> mutibytes language.

ELinks 0.12.GIT already supports multibyte UTF-8, so it can
display <http://zh.wikipedia.org/>, for example.
You may want to implement some of the following:

- Support other multibyte charsets in HTTP.  (enhancement 891)

- Better text-wrapping rules for CJK characters.  Currently,
  ELinks assumes that the line can be broken wherever there is a
  fullwidth character.  Japanese has "kinsoku shori" rules that
  should preferably be followed.  I don't know if Chinese has
  something similar.

- Allow non-ASCII characters in key bindings.  (enhancement 825)

- po/zh.po.

- Internally support non-Unicode characters.  I think this should
  not be done without good reason.  The current Unicode support
  already makes the code annoyingly complex and still has some
  bugs.
 
- Support other multibyte charsets in terminal I/O.  This too
  seems like complexity best avoided.  One can already convert
  the terminal I/O to a different charset by running ELinks
  inside Screen.

- Ruby or furigana.

- Support other multibyte charsets in file names, external
  editors, and configuration files.

- Better support for combining characters.  0.12.GIT does not
  support them at all.  0.13.GIT has some experimental code.

- Unicode normalization, e.g. for searching.

So, I suggest you describe what you think is the most urgent
change, and I or someone else can then advise on how to best
implement that.

However, I do not personally want to add such features to ELinks
0.12.GIT.  It should already have been released a year ago and
there still are bugs blocking the release.  Changes like these
seem likely to cause new bugs, so they should go in 0.13.GIT
instead.  The po/zh.po would be an exception though.

_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev
signature.asc (application/pgp-signature, 188 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH8/tUHm9IGt60eMgRAqs/AJsHITjQdj7OGxPrY3IRiIo4EapJ4gCfTiTM
r7aIXqDKl2h7wuYorXWKaWI=
=LcEI
-----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.