This document describes about a variant of w3m with support for the following character encodings
The page which includes both UTF-8 encoded Unicode characters and ISO 2022 registered characters, is rendered without any problem, and can be viewed on kterm with ISO 2022, or on xterm with UTF-8. In case terminal emulator fails to find corresponding fonts, garbages may appear on screen, but they will disappear if missing fonts are supplied.
It is not tested at all whether line input routine can handle double width characters other than JIS X 0208. Right-to-left writing language is not considered at all. Terminal emulators used for test are kterm(-6.2.0), xterm(-165) with utf-8 support, and rxvt(-2.6.3) with euc-jp support.
If you will use character encoding extension part of this variant, you need first to get and install the support library. In most POSIX conforming environment, you just need to issue the following commands:
make install ; ldconfigI strongly recomend to use the latest version. Unless you will use character encoding extension part of this variant, you need not this library.
You may further need to install Boehm-GC library, unless you have already the library. Notice that you may need to install include file gc.h, and probably private/gc_private.h, in hand.
Then move to the directory where you extracted the tarball
w3mmee-p24-23.tar.gz (681KB, 2006-09-30 07:38:28)and follow the usual process:
configure ; make ; su -c 'make install'where, when you run configure, you need to answer "3" to the question
Which language do you prefer?if you want to enable character encoding extensions. Other enhancements are still included even if you answer 1 or 2.
When you invoke the installed executable, you need to assign the environment variable "W3MLANG" with the value
Here is a detailed description about run-time configuration.
You can view ChangeLog:
w3mmee-release-ChangeLog.txt (201KB, 2006-09-30 07:38:28)which is included the above tarball.
Here is the list of known problems in the latest release. They should be fixed in the latest snapshot of release branch in my CVS repository. Please consult ChangeLog of the snapshot for implementation details.
Different from the case of the release version, to make the latest snapshot, libmoe is mandatory.
User functions ``PREV'' and ``NEXT'' behave reversely.
Any questions or comments about this page are greatly appreciated.
Almost all contents in this site are written by Kiyokazu SUTO (i.e. me) unless especially noted. I want to put all of them into the PUBLIC DOMAIN, even though some lawyers mention that it is impossible in my country.