pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedPgAccess 0.97 - final preview
4+ messages / 2 participants
[nested] [flat]
* PgAccess 0.97 - final preview
@ 1999-08-11 12:41 Constantin Teodorescu <teo@flex.ro>
0 siblings, 1 reply; 4+ messages in thread
From: Constantin Teodorescu @ 1999-08-11 12:41 UTC (permalink / raw)
To: pgsql-interfaces
The same URL
ftp://ftp.flex.ro/pub/pgaccess/pgaccess-0.97b.tcl.gz
This version should be used to add translations to other languages:
-french
-german
-italian
-spanish
or whatever language do you want. Volunteers should contact me directly
in order to set up a procedure for updating Messages for various
languages.
Also, this final preview version has other improvements:
-add new index/drop indexes through table Object/Information
-select desired language from Preferences form
-some forms are using combined pack/grid manager to position widgets in
order to accommodate the variable message length due to
internationalization
Waiting for volunteers for translation,
--
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA
^ permalink raw reply [nested|flat] 4+ messages in thread
* RE: PgAccess 0.97 - final preview
@ 1999-08-11 19:33 Hiroki Kataoka <kataoka@interwiz.koganei.tokyo.jp>
parent: Constantin Teodorescu <teo@flex.ro>
0 siblings, 1 reply; 4+ messages in thread
From: Hiroki Kataoka @ 1999-08-11 19:33 UTC (permalink / raw)
To: pgsql-interfaces
Hi all.
> Subject: [INTERFACES] PgAccess 0.97 - final preview
>
> The same URL
>
> ftp://ftp.flex.ro/pub/pgaccess/pgaccess-0.97b.tcl.gz
>
> This version should be used to add translations to other languages:
> -french
> -german
> -italian
> -spanish
> or whatever language do you want. Volunteers should contact me directly
> in order to set up a procedure for updating Messages for various
> languages.
I feel that this international version is very nice.
I have tried this beta version with additional japanese kanji messages. But
I have a problem.
In japan, we use usually the japanese kanji enhanced tcl. This tcl
understands all japanese kanji encodings and assumes that a 8 bits
character is a part of kanji character's multibyte. Above languages have 8
bits characters but these are not kanji. So, current international version
of pgaccess can not use on japanese tcl even if I include japanese messages.
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.
I want so much to complate to translate messages to japanese.
How do you think.
Thank you.
Hiroki Kataoka
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [INTERFACES] RE: PgAccess 0.97 - final preview
@ 1999-08-12 06:30 Constantin Teodorescu <teo@flex.ro>
parent: Hiroki Kataoka <kataoka@interwiz.koganei.tokyo.jp>
0 siblings, 1 reply; 4+ messages in thread
From: Constantin Teodorescu @ 1999-08-12 06:30 UTC (permalink / raw)
To: Hiroki Kataoka <kataoka@interwiz.koganei.tokyo.jp>; +Cc: pgsql-interfaces
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
^ permalink raw reply [nested|flat] 4+ messages in thread
* RE: PgAccess 0.97 - final preview
@ 1999-08-12 14:32 Hiroki Kataoka <kataoka@interwiz.koganei.tokyo.jp>
parent: Constantin Teodorescu <teo@flex.ro>
0 siblings, 0 replies; 4+ messages in thread
From: Hiroki Kataoka @ 1999-08-12 14:32 UTC (permalink / raw)
To: pgsql-interfaces
Constantin Teodorescu wrote:
>
> 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.
I understood your plan.
The japanese Tcl has some new functions; kanji encoding auto detection,
kanji encoding conversion, etc.. These encoding functions are needed for
japanese users, because japanese kanji texts are represented in many
encodings (JIS, ShiftJIS or EUC). But one text is not represented in more
than one encoding, because the kanji encoding auto detection is impossible
when a text is represented in more than one encoding.
I know that latest Tcl version is 8.1 and this version supports Unicode. But
using this version on japanese environment, we have a obstacle when using
kanji input method. I think that Tcl 8.1 can not use practically in japanese
environment for the time being. By the way, almost all japanese users are
using japanese enhanced Tcl7.6 and Tcl8.0.x.
Let us suppose that japanese users use Tcl8.1. Because Tcl8.1 assumes that
Tcl source file is written in running operating system's encoding, we can
not write source file in Mixed languages, either.
If one source file will include one language only, then both japanese Tcl
and international Tcl8.1 will load the Tcl source file successfully.
Thank you.
Hiroki Kataoka
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~1999-08-12 14:32 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-08-11 12:41 PgAccess 0.97 - final preview Constantin Teodorescu <teo@flex.ro>
1999-08-11 19:33 ` Hiroki Kataoka <kataoka@interwiz.koganei.tokyo.jp>
1999-08-12 06:30 ` Constantin Teodorescu <teo@flex.ro>
1999-08-12 14:32 ` Hiroki Kataoka <kataoka@interwiz.koganei.tokyo.jp>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox