Bug-report about pgaccess for kanji-use

Started by Yoshinori Ariieover 24 years ago2 messagespatches
Jump to latest
#1Yoshinori Ariie
PBA00250@nifty.com

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Yoshinori Ariie
Your email address : PBA00250@nifty.com

System Configuration
---------------------
Architecture (example: Intel Pentium) : Intel Cerelon

Operating System (example: Linux 2.0.26 ELF) : Linux 2.2.19

PostgreSQL version (example: PostgreSQL-7.1.1): PostgreSQL-7.2

Compiler used (example: gcc 2.95.2) : gcc 2.95.3

Please enter a FULL description of your problem:
------------------------------------------------
Failed exchange input-mode by <Control-Kanji> key to use kanji with pgaccess
This bug has been not fixed since 7.1.x

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
same as above

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
following patch solved the problem

*** /usr/local/pgsql/share/pgaccess/lib/tables.tcl.org	Sun Feb 17 20:27:00 2002
--- /usr/local/pgsql/share/pgaccess/lib/tables.tcl	Sun Feb 17 20:32:58 2002
***************
*** 815,821 ****
  	$wn.c bind q <Key> "Tables::editText $wn %A %K"
  	if {[info commands kanjiInput] == "kanjiInput"} then {
  		$wn.c bind q <Control-backslash> "pgaccess_kinput_start %W";
! 		$wn.c bind q <Control-Kanji> "pg_access_kinput_start %W";
  	}
  } else {
  	$wn.c bind q <Key> {}
--- 815,821 ----
  	$wn.c bind q <Key> "Tables::editText $wn %A %K"
  	if {[info commands kanjiInput] == "kanjiInput"} then {
  		$wn.c bind q <Control-backslash> "pgaccess_kinput_start %W";
! 		$wn.c bind q <Control-Kanji> "pgaccess_kinput_start %W";
  	}
  } else {
  	$wn.c bind q <Key> {}
#2Tatsuo Ishii
ishii@postgresql.org
In reply to: Yoshinori Ariie (#1)
Re: Bug-report about pgaccess for kanji-use

This has been already fixed in 7.2-stable and current.

Show quoted text

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Yoshinori Ariie
Your email address : PBA00250@nifty.com

System Configuration
---------------------
Architecture (example: Intel Pentium) : Intel Cerelon

Operating System (example: Linux 2.0.26 ELF) : Linux 2.2.19

PostgreSQL version (example: PostgreSQL-7.1.1): PostgreSQL-7.2

Compiler used (example: gcc 2.95.2) : gcc 2.95.3

Please enter a FULL description of your problem:
------------------------------------------------
Failed exchange input-mode by <Control-Kanji> key to use kanji with pgaccess
This bug has been not fixed since 7.1.x

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
same as above

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
following patch solved the problem

*** /usr/local/pgsql/share/pgaccess/lib/tables.tcl.org	Sun Feb 17 20:27:00 2002
--- /usr/local/pgsql/share/pgaccess/lib/tables.tcl	Sun Feb 17 20:32:58 2002
***************
*** 815,821 ****
$wn.c bind q <Key> "Tables::editText $wn %A %K"
if {[info commands kanjiInput] == "kanjiInput"} then {
$wn.c bind q <Control-backslash> "pgaccess_kinput_start %W";
! 		$wn.c bind q <Control-Kanji> "pg_access_kinput_start %W";
}
} else {
$wn.c bind q <Key> {}
--- 815,821 ----
$wn.c bind q <Key> "Tables::editText $wn %A %K"
if {[info commands kanjiInput] == "kanjiInput"} then {
$wn.c bind q <Control-backslash> "pgaccess_kinput_start %W";
! 		$wn.c bind q <Control-Kanji> "pgaccess_kinput_start %W";
}
} else {
$wn.c bind q <Key> {}

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)