[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev 1) placement of "README.jp" 2) is "--enable-cjk" necessary
From: |
Hataguchi Takeshi |
Subject: |
Re: lynx-dev 1) placement of "README.jp" 2) is "--enable-cjk" necessary |
Date: |
Sun, 9 Apr 2000 09:44:24 +0900 (JST) |
On Wed, 5 Apr 2000, Henry Nelson wrote:
> I think "README.jp" should go in the docs/ subdirectory rather than
> in the top directory.
I agree.
> With the recent Hataguchi changes, which seem to be on by default in
> userdefs.h, does it make sense to use the configure option "--enable-cjk"?
> What does "--enable-cjk" do that "USE_TH_JP_AUTO_DETECT, CONV_JISX0201KANA
> _JISX0208KANA, and KANJI_CODE_OVERRIDE" don't?
I'm sorry I don't know.
Klaus ever (13 Jan 2000) wrote like this:
| For the longest time I had thought that CJK_EX was basically just a
| porting device, or merging device: that is was used to mark some
| alternative sections of code, until somebody would review those sections
| and decide whether to keep them "for good" (and remove the #ifdef, and
| remove previous and now superseded code) or not. I've learned more
| recently that that, apparently, this isn't the case: CJK_EX is used to
| also control some real configuration choices. (At least: whether that
| extra toggle is provided; and whether X0201 kana should be converted to
| something else or not.) This is a bad overloading of this one symbol with
| multiple meanings. If there is a need to make those decisions
| configurable at compile-time, that should be provided for with separate
| symbols.
I agree with this and I believe you also do.
I've done this job partially. But I don't have time to do the rest now.
--
Takeshi Hataguchi
E-mail: address@hidden