# alphabet -- xstroke alphabet configuration file # # xstroke is available from ftp://ftp.handhelds.org/pub/projects/xstroke # # Rather than hacking this file directly, you probably want to start # with a file ~/.xstroke/alphabet that consists of a single line: # # include "/etc/xstroke/alphabet" # # Then, you may add your custom strokes to that file, (you'll want to # add them before the include line so that your custom strokes take # precedence over the strokes defined in /etc/xstroke/alphabet). # Here is a summary of the syntax of this file: # Blank lines are ignored. # Lines beginning with a '#' character are comments and are ignored. # INCLUDE STATEMENTS: # # An include statement looks like this: include "/path/to/some/file" It # will open and read the file, which should have the same syntax as # this file. File may be included to arbitrarily deep levels, but no # checks are made to avoid infinite include loops, so Don't Do That. # MODE DEFINITIONS: # # The alphabet file consists of a series of mode definitions which # will have the following form: # # Mode [: , ... ]{ # # ... # } # # Where all mode names are quoted strings. # # xstroke always has one active mode, (whose name will be displayed in # the control window). The user may change the active mode by using # ModeShift and ModeLock strokes defined within the active mode, (or # one of its parents). # # There are two mode names that have special meaning: __GLOBAL__ and # __FALLBACK__. Strokes defined within the __GLOBAL__ mode take # precedence over any strokes defined within the active mode. Strokes # defined within __FALLBACK__ are available in all modes, but at a # precedence lower than any other stroke within the mode. # # The logic used to search for recognized strokes is as follows: When # the user enters a stroke, a probability is computed for each # candidate stroke definition. The stroke definition with the highest # probability is then returned. For the purpose of resolving stroke # definitions with equal probabilities, the first definition # encountered will be returned. Strokes within each mode are searched # in the same order they are processed within the alphabet file. Modes # are searched in the following order: the __GLOBAL__ mode, the active # mode, the parents of the active mode (and recursively, all of their # parents in depth-first order), and finally the __FALLBACK__ mode. # STROKE DEFINITIONS: # # The meat of the alphabet file is stroke definitions of the form: # # = # # where can be any of the following: # # Key # Button