Received: from flex.flex.ro (IDENT:root@[193.230.255.4]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA43030 for ; Thu, 12 Aug 1999 02:24:50 -0400 (EDT) (envelope-from teo@flex.ro) Received: from flex.ro (IDENT:teo@teo.flex.ro [193.230.255.3]) by flex.flex.ro (8.9.3/8.9.3) with ESMTP id JAA02377; Thu, 12 Aug 1999 09:24:58 +0300 Sender: teo@flex.flex.ro Message-ID: <37B26A09.64A57D9B@flex.ro> Date: Thu, 12 Aug 1999 06:30:33 +0000 From: Constantin Teodorescu Organization: FLEX Consulting Braila X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.9 i586) X-Accept-Language: en MIME-Version: 1.0 To: Hiroki Kataoka CC: PostgreSQL Interfaces Subject: Re: [INTERFACES] RE: PgAccess 0.97 - final preview References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hiroki Kataoka wrote: > > I think that better solution is to separate a source file of pgaccess to > main code and message catalog files. And message catalog files should be > supplied for each of all supported languages. The pgaccess main code > includes only english messages as default language, and supports to load one > message catalogue file at startup. That's exactly what I intend to do in the next version. But in order to grab together more translations and for the easy of use I choose to keep for the moment the Messages array in the main file. There will be separate *.lang files that will be used for different languages. Also , PgAccess will be sliced into separate files for each module. But related to japanese messages I have a question. If I will move the definition for Messages in a separate file, why would it help it? What "japanese Tcl" are you talking? Have you tried Tcl/Tk 8.1 or 8.2 beta? They (scriptics) are saying that it support Unicode. Maybe that's what you should use. -- Constantin Teodorescu FLEX Consulting Braila, ROMANIA