%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
default xkb_compatibility "xtest" { // Minimal set of symbol interpretations to provide // reasonable behavior for testing. // The X Test Suite assumes that it can set any modifier // by simulating a KeyPress and clear it by simulating a // KeyRelease. Because of the way that XKB implements // locking/latching modifiers, this approach fails in // some cases (typically the Lock or NumLock modifiers). // These symbol interpretations make all modifier keys // just set the corresponding modifier so that xtest // will see the behavior it expects. virtual_modifiers NumLock,AltGr; interpret.repeat= False; setMods.clearLocks= True; latchMods.clearLocks= True; latchMods.latchToLock= False; interpret Shift_Lock+AnyOf(Shift+Lock) { action= SetMods(modifiers=Shift); }; interpret Num_Lock+Any { virtualModifier= NumLock; action= SetMods(modifiers=NumLock); }; interpret Mode_switch { useModMapMods= level1; virtualModifier= AltGr; action= SetGroup(group=2); }; interpret Any + Any { action= SetMods(modifiers=modMapMods); }; group 2 = AltGr; group 3 = AltGr; group 4 = AltGr; indicator.allowExplicit= False; indicator "Caps Lock" { modifiers= Lock; }; indicator "Num Lock" { modifiers= NumLock; }; indicator "Shift Lock" { whichModState= Locked; modifiers= Shift; }; indicator.allowExplicit= True; };