🚀 go-pugleaf

$@2OLn(J@CSL.Sony$@$G$9!#$3$$$D$O6lO+$7$?$s$@(J...

At first, don't forget to put next line in site.def for (Non JLE) SUN OS.
#define StandardDefines   -DNOSTDHDRS -DX_WCHAR -DX_LOCALE 

In article <1992Sep11.220220.6376@u.washington.edu> , 
	dean2@tbone.biol.scarolina.edu (Dean Pentcheff) writes 
>1) I cannot get a successful build of contrib/lib/Xwchar or
>   contrib/lib/Xaw.  I think the problem is with my understanding
>   of the xmkmf/imake system. 

try
    xmkmf ../../mit `pwd`
and "make  includes" is necessary. It will replace X11/Xaw by i18n-Xaw's
include file in mit/X11 directory. If you don't like it, you can link
them by hand. For example create X11 directory in contrib/lib/Xaw/X11
and link all *.h file and add -I. in CFLAGS.
 
>2) I have tried to apply the contrib-fixes patches to many of
>   the contrib clients.  These patches appear to basically internationalize
>   some of the clients.  Although the patch program claims that the
>   patches ran OK, the resulting source code is incorrect and refuses
>   to compile (syntax errors, etc.).  Any suggestions?

If you omit "make includes", i18n client source use non-i18n Xaw include
files. You can use same tirck like  mkdir X11 and -I.

As far as I know, there are three versions of  i18n Xaw.
     Xaw     for Xsi      for xwmno   (this is what you have..)
     Xaw     for Ximp     for kinput2 or other kana-kanji converter
     Xaw     for kinput2
All three work but require three different entries in .Xdefaults.

BTW R4's Japanese Xaw is a replacement of Xaw, so it does not requires
client modification.  But R5's i18n Xaw is useless for non i18n clients.
But I find R4's Xaw still works with R5 clients.

---
Shinji Kono @           kono@csl.sony.co.jp
Sony Computer Science Laboratory, Inc,Japan