From owner-freebsd-java Wed Oct 31 7:11:53 2001 Delivered-To: freebsd-java@freebsd.org Received: from smg.is.titech.ac.jp (smg.is.titech.ac.jp [131.112.35.1]) by hub.freebsd.org (Postfix) with ESMTP id 967A337B401 for ; Wed, 31 Oct 2001 07:11:48 -0800 (PST) Received: from tripper.private (smg [131.112.35.1]) by smg.is.titech.ac.jp (Postfix) with ESMTP id 5B9E719886; Thu, 1 Nov 2001 00:10:37 +0900 (JST) Date: Thu, 01 Nov 2001 00:15:31 +0900 Message-ID: <55r8rj3koc.wl@tripper.private> From: Fuyuhiko Maruyama To: daichi@int.ongs.gr.jp Cc: java@FreeBSD.ORG Subject: Re: Quick survey of XIM and JDK on FreeBSD In-Reply-To: <20011031090942.77568.qmail@int.ongs.gr.jp> References: <20011031090942.77568.qmail@int.ongs.gr.jp> User-Agent: Wanderlust/2.7.4 (Too Funky) on XEmacs/21.5.3 (asparagus) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thank you GOTO-san, I know what's happen with JDK 1.3.1 on FreeBSD pretty well. So, I try to write explanations on some issues. 1. I cannot write xwnmo handling codes at all because xwnmo have completely different semantics for on-spot-conversion(in XIM's word, XIMPreeditCallbacks) from other XIM servers(e.g. kinput2, vje and Solaris's htt). In early September 2001, I had been hacking JDK 1.3.1 to support xwnmo and found the difference, then I request OMRON, the vendor of xwnmo, to tell me the semantics of xwnmo but they don't give me any meaningful information. 2. My patches for OpenMotif isn't the one to fix XIM input problem but to fix OpenMotif's internal problem. Without patches, Java program using TextField like demo/applets/ArcTest causes Segmentation Fault soon when it run. 3. Your Notepad problem isn't enough clear for me to understand what's the problem because it works fine on my environment. In fact, I added codes to guess what window manager is running and it includes a heuristics to check fvwm2 running that can mis-guess other WMs as fvwm2. If zero sized Java window is appeared, it may be caused by such mis-guessing. I will fix the problem case-by-case, so please tell me what window manager you use. On 31 Oct 2001 09:09:42 -0000, daichi@int.ongs.gr.jp wrote: (mega snip) > > In addition, there is 1976-1 problem of watanabe/wadalab > font(/usr/ports/japanese/truetypefonts). I am trying to solve this > problem by adding a dummy 1976-1 font to it. However, it has not solved > yet. Please already wait for a while. (It seems that this font is added > in Solaris. But I donot have it) What's this? -- Fuyuhiko MARUYAMA Matsuoka laboratory, Department of Mathematical and Computing Sciences, Graduate School of Information Science and Engineering, Tokyo Institute of Technology. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message