On Wed, 22 Mar 2000, Klaus Weide wrote:

> On Mon, 20 Mar 100, T.E.Dickey wrote:
> > > On Sat, 19 Feb 2000, Hataguchi Takeshi wrote: 
> > >  
> > > >   o to define USE_TH_JP_AUTO_DETECT and CONV_JISX0201KANA_JISX0208KANA  
> > > >     without any configure options 
> > >  
> > > I had to define these macros in makefile to enable the routines I added. 
> > > I wanted to say that I want these are defined without any configure  
> > > options nor modification of makefile. 
> > > I want these are defined in a certain header file, but I don't know 
> > > where is the right place (in LYGlobalDefs.h?). 
> > 
> > HTUtils.h gets most of the definitions that don't have a better place
> > to put them.  It is included almost everywhere.
> 
> But if these are things a user may prefer to undefine - and I believe that
> is the case, at least for the second one - then they should go into
> userdefs.h.

Thanks for your advice. I wrote a patch to define them in userdefs.h.
I'm sorry it takes so long time to post this.

And I wrote a document, which shows some supplements for Japanese 
in Japanese. I wish this would be included in the next Lynx archive.
--
Takeshi Hataguchi
E-mail: [EMAIL PROTECTED]

%%% Created Tue Mar 28 20:01:04 JST 2000 by target lynx.patch. %%%
diff -bru orig/lynx2-8-3/userdefs.h lynx2-8-3/userdefs.h
--- orig/lynx2-8-3/userdefs.h   Mon Mar 27 12:14:00 2000
+++ lynx2-8-3/userdefs.h        Tue Mar 28 08:11:32 2000
@@ -1440,6 +1440,40 @@
 #endif /* DOSPATH */
 #endif /* VMS */
 
+/*****************************
+ * USE_TH_JP_AUTO_DETECT, CONV_JISX0201KANA_JISX0208KANA, 
+ * and KANJI_CODE_OVERRIDE are the macros for Japanese. - TH
+ */
+/*****************************
+ * USE_TH_JP_AUTO_DETECT enables a new Japanese charset detection routine.
+ * By old detection strategy, Lynx always thought the document may be
+ * written in mixed three kanji codes (JIS, EUC and SJIS).
+ * But by new one, Lynx first assume the document is written in one or 
+ * JIS + another kanji code (JIS, EUC, SJIS, EUC+JIS and SJIS+JIS).
+ * When it's found the assumption is wrong, Lynx thinks it's 
+ * written in mixed three kanji codes.
+ * The first assumption is usually correct.
+ * So I believe this makes Lynx is a better guesser.
+ */
+#define USE_TH_JP_AUTO_DETECT
+
+/*****************************
+ * If CONV_JISX0201KANA_JISX0208KANA is set, 
+ * Lynx will convert JIS X0201 Kana to JIS X0208 Kana, 
+ * i.e. convert half width kana to full width.
+ * I've not tested the case not to define this well.
+ */
+#define CONV_JISX0201KANA_JISX0208KANA
+
+/*****************************
+ * Uncomment this line to enable kanji code override routine. 
+ * The code can be changed by ^L.
+ * More precisely, this enables us to change the assumption kanji
+ * code for the document. This assumption overrides the charaset
+ * by META tag and HTTP responses.
+ */
+/*#define KANJI_CODE_OVERRIDE */
+
 
 /****************************************************************
  *  Section 4.  Things you MUST check only if you plan to use Lynx

README.jp

Reply via email to