External-event can have three fragments separated with period:
==============================================================

token.type.scope

For example, if Tokenizer met word "day", then it
submits event:

  day.w

which means that actual token of event is day and
type of event is "w". (Abbr. for "word".)

If tokenizer met a separator "(" in current position,
this event will be submitted:

  (.s

which means that token of event is "(" and
type is s. (Abbr. for "separator".)

There is a generalization:
event-pattern

  .10

is a declaration for separator "line feed".
Event pattern .65 is a declaration for separator "a".
Hence, number placed after period in event-pattern is
actually a declaration for character with ascii equal to
this number.

"\013" can be used instead of .13
"\013"..l makes this event local its state.


SCOPES  ...
------

have effect only in event-pattern. They defind situations when Tokenizer 
will ignore or recognize the event-pattern.
In action-event which is already "recognized", scopes are igonred.

scopes are:

g - global
l - local; tokenizer will recognize local separators if Compi is in the nest which 
	   allows this event.
u - unspecified; tokenizer's behaviour depends on what is Compi's perception: 
    if separators_are_global is set to true, then "u" is interpreted as "global".


More details are in: 
--------------------

  reserved_names_help.txt
  important_types_help.txt