This file is indexed.

/etc/X11/app-defaults/Kinput2 is in kinput2-common 3.1-13.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
! $Id: Kinput2.ad,v 1.24 1999/04/12 09:21:26 ishisone Exp $
!
!	app-defaults file for kinput2 version 2.0
!
!!
!! things you shouldn't change
!!
Kinput2.mappedWhenManaged: false
Kinput2.width: 1
Kinput2.height: 1
*converter.accelerators: <Key>: to-inputobj()
! AIX seems to need the following superfluous definition.
*ki2AppDefsLoaded: true
!!
!! title
!!
*SeparateConversion.title: Kana-Kanji Conversion
*selectionShell.title: Candidate Selection
*auxShell.title: Auxiliary Control

!! Don't give input focus to the windows of kinput2, they don't need input focus
!! it just causes problems if they get input focus.
!!
!! For example, if you use kinput2 with Canna and open the 'auxShell' window
!! by pressing the 'insert' key a window pops up where special symbols
!! can be selected. If this window gets focus, the selected symbol will not
!! appear in the application until the application gets focus again. This is
!! quite confusing.
!! And there are even some applications where the selected symbol will never appear,
!! not even when the application gets focus again. Gvim currently behaves
!! like that and XIM in Gvim may even become completely unusable after one of
!! the kinput2 windows got focus, making it necessary to restart Gvim to be able
!! to use XIM again.
!!
!! I found no reason why one of kinput2's windows should need input focus.
!! 
*SeparateConversion.input: false
*selectionShell.input: false
*auxShell.input: false

! if you're using mwm (Motif1.1), you can set kanji titles.
!*SeparateConversion.title: \033$(B$+$J4A;zJQ49
!*SeparateConversion.titleEncoding: COMPOUND_TEXT
!*selectionShell.title: \033$(BA*Br%Q%M%k
!*selectionShell.titleEncoding: COMPOUND_TEXT
!!
!! fonts to be used by root-window type conversion widget and
!! candidate selection widget
!!
*Font: -*-fixed-medium-r-normal--14-*-*-*-c-*-iso8859-1
*KanjiFont: -misc-fixed-medium-r-normal--14-*-*-*-c-*-jisx0208.1983-0
*KanaFont: -*-fixed-medium-r-normal--14-*-*-*-c-*-jisx0201.1976-0
!!
!!	Wnn setup
!!
*CcWnn.Jserver:	localhost
!*CcWnn.jserver2nd:	"secondary-jserver-host-if-any"
*CcWnn.ccdef:		ccdef.kinput2.egg
!*CcWnn.wnnEnvrc4:	"wnenvrc-file-for-Wnn4"
!*CcWnn.wnnEnvrc6:	"wnenvrc-file-for-Wnn6"
!!
!!	Canna setup for version 2.x, 3.x
!!
!*Canna.Cannahost:	"canna-host"
!*Canna.Cannafile:	"canna-initialization-file"
!!
!!	Sj3 setup
!*Sj3.sj3serv:		"primary-sj3serv-host"
!*Sj3.sj3serv2:		"secondary-sj3serv-host-if-any"
!!
!! candidate selection
!!
*selection.width: 500
*selectionShell.allowShellResize: True
*selection.cursor: left_ptr
!!
!! input style dependent resources
!!
! over-the-spot type input
*OverTheSpotConversion.AutoSpotForwarding: true
*OverTheSpotConversion.ShrinkWindow: true
*OverTheSpotConversion.modeLocation: tracktext
!*OverTheSpotConversion.modeLocation: bottomleft
*OverTheSpotConversion*modeShell.input: false
*OverTheSpotConversion*modeShell.allowShellResize: true
*OverTheSpotConversion*text.borderWidth: 0
*OverTheSpotConversion*modeShell.borderWidth: 2
! off-the-spot type input
*OffTheSpotConversion.input: false
*OffTheSpotConversion*modeShell.borderWidth: 0
*OffTheSpotConversion.text.borderWidth: 0
! root-window type input
*SeparateConversion*form*vertDistance: 3
*SeparateConversion*mode.left: chainleft
*SeparateConversion*mode.right: chainleft
*SeparateConversion*mode.top: chaintop
*SeparateConversion*mode.bottom: chaintop
*SeparateConversion*mode.width: 80
*SeparateConversion*mode.height: 20
*SeparateConversion*mode.resizable: true
*SeparateConversion*text.fromVert: mode
*SeparateConversion*text.left: chainleft
*SeparateConversion*text.right: chainright
*SeparateConversion*text.top: chaintop
*SeparateConversion*text.bottom: chainbottom
*SeparateConversion*text.width: 400
*SeparateConversion*text.height: 100
! status display string justification -- for over-the-spot and off-the-spot
!  "left" seems appropriate for most applications.
*modeShell.mode.justify: left
!!
!! conversion protocol dependent resources
!!
! KinputProtocol
*KinputProtocol.BackwardCompatible: true
*KinputProtocol.XlcConversionStartKey:	Shift<Key>space
! XimpProtocol
*XimpProtocol.ForceDefaultServer: true
! X Input Method Protocol
*IMProtocol.locales: ja_JP.SJIS, ja_JP.EUC, ja_JP, japanese, japan, ja
! common to XimpProtocol and IMProtocol
*defaultFontList: -misc-fixed-medium-r-normal--14-*-*-*-c-*
*ConversionStartKeys: \
	Shift<Key>space \n\
	Ctrl<Key>Kanji
!!
!! sending back unused keypress events
!!
*sendbackKeyPress: True
!!
!! title bar height of popup shells (candidate selection etc.)
!!
!*titlebarHeight: 24
!!
!! a work around for buggy window managers
!!
! If you encounter a strange phenomenon where kinput2's mode display
! window is flickering and you cannot type in any text, try enabling
! the following resource.  This phenomenon is caused by the incorrent
! focus management of your window manager, and this resource avoids
! it by making the window manager totally ignore the mode window.
*OverTheSpotConversion.UseOverrideShellForMode: True