Commit: 364df43e42395cfbb3b8a1b88d71fd0d3bb67b55 - xnee_doc_ja (git)

Commit MetaInfo

• Revision: 364df43e42395cfbb3b8a1b88d71fd0d3bb67b55 (tree)
• Time: 2011-03-06 15:44:35
• Author: nobody <nobody@exam...>
• Commiter: nobody

Log Message

オリジナルファイルも管理下に置く。

Change Summary

• add: original/AUTHORS
• add: original/COPYING
• add: original/ChangeLog
• add: original/Makefile.am
• add: original/Makefile.in
• add: original/NEWS
• add: original/README
• add: original/fdl.texi
• add: original/stamp-vti
• add: original/version.texi
• add: original/xndetail.dia
• add: original/xndetail.jpg
• add: original/xndetail.png
• add: original/xnee.dox
• add: original/xnee.html
• add: original/xnee.info
• add: original/xnee.pdf
• add: original/xnee.ps
• add: original/xnee.texi
• add: original/xnee.txt
• add: original/xnee_copying
• add: original/xnee_error.texi
• add: original/xnee_exampl.texi
• add: original/xnee_faq.texi
• add: original/xnee_func.texi
• add: original/xnee_general.texi
• add: original/xnee_install.texi
• add: original/xnee_intern.texi
• add: original/xnee_intro.texi
• add: original/xnee_progs.texi
• add: original/xnee_prot.texi
• add: original/xnee_req.texi
• add: original/xnee_start.texi
• add: original/xnee_synch.texi
• add: original/xnee_usage.texi
• add: original/xngener.dia
• add: original/xngener.jpg
• add: original/xngener.png
• add: original/xnrec.dia
• add: original/xnrec.jpg
• add: original/xnrec.png
• add: original/xnrep.dia
• add: original/xnrep.jpg
• add: original/xnrep.png
• add: original/xnswinp.dia
• add: original/xnswinp.jpg
• add: original/xnswinp.png

Incremental Difference

--- /dev/null
+++ b/original/AUTHORS
@@ -0,0 +1,22 @@
+Xnee / AUTHORS
+--------------------
+
+Authors:
+--------
+Henrik Sandklef    [e-mail]
+Jon-Erling Dahl    [e-mail]
+
+Contributors (code fixes, comments etc):
+---------------------------------------
+Janice Waddick 
+
+Juan F. Codagnone  
+Lars Brinkhoff
+Ton van Vliet 
+Nekrasov Alexander 
+Dr. Adrian Wrigley 	
+Conall McGleenan  
+Bianchi Roberto   
+Thomas Riga  
+Stuart Guthrie 
+Volker Stolz

--- /dev/null
+++ b/original/COPYING
@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year  name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.

--- /dev/null
+++ b/original/ChangeLog
@@ -0,0 +1,4 @@
[phone]  Henrik Sandklef  <hesa@laphroaig>
+
+	* pics/dia_gen.sh: added convertion to jpg
+

--- /dev/null
+++ b/original/Makefile.am
@@ -0,0 +1,142 @@
+docdir = $(datadir)/xnee
+
+xnee_TEXINFOS=xnee_error.texi xnee_prot.texi version.texi  xnee_error.texi xnee_exampl.texi xnee_faq.texi xnee_install.texi xnee_intro.texi xnee_req.texi xnee_synch.texi xnee_usage.texi xnee_general.texi xnee_start.texi  xnee_intern.texi xnee_copying fdl.texi xnee_func.texi xnee_progs.texi 
+IMG_DIA = xndetail.dia xngener.dia xnrec.dia xnrep.dia xnswinp.dia 
+IMG_EPS = xndetail.eps xngener.eps xnrec.eps xnrep.eps xnswinp.eps 
+IMG_PDF = xndetail.pdf xngener.pdf xnrec.pdf xnrep.pdf xnswinp.pdf 
+IMG_PNG = xndetail.png xngener.png xnrec.png xnrep.png xnswinp.png
+IMG_JPG = xndetail.jpg xngener.jpg xnrec.jpg xnrep.jpg xnswinp.jpg
+
+GEN_IMAGES = $(IMG_EPS) $(IMG_PDF) $(IMG_PNG) $(IMG_JPG)
+GEN_IMAGES_TO_INSTALL = $(IMG_PNG) $(IMG_JPG)
+MANUALS = xnee.html xnee.ps xnee.txt
+
+EXTRA_DIST = xnee_copying fdl.texi *.dia xnee.dox xnee.html xnee.pdf xnee.ps xnee.txt  \
+	$(GEN_IMAGES_TO_INSTALL) 
+#\
+#	$(MANUALS)
+
+if BUILDDOC
+DOC_DEP=$(GEN_IMAGES_TO_INSTALL) $(MANUALS)
+doc_DATA = $(MANUALS) $(GEN_IMAGES_TO_INSTALL)
+endif
+
+#MAKEINFO = @MAKEINFO@ --no-split
+#TEXI2HTML = texi2html
+#DVI2PS = dvi2ps
+#PS2PDF = ps2pdf
+###   TEXI2HTML_FLAGS = -split_chapter
+
+info_TEXINFOS = xnee.texi 
+
+CLEANFILES = xnee.acs  xnee.cvs  xnee.mss  xnee.prs \
+	     xnee.ats  xnee.evs  xnee.fns  xnee.ovs \
+             xnee.tmp  stamp-vti \
+             $(IMG_EPS) $(IMG_PDF) $(IMG_PNG) $(IMG_JPG) \
+             *.eps *.jpg *.png *.pdf *.html
+
+
+
+
+
+## ----------------------------- ##
+## Other documentation formats.  ##
+## ----------------------------- ##
+
+
+# HTML
+xnee.html: xnee.texi $(GEN_IMAGES)
+	$(TEXI2HTML) $(TEXI2HTML_FLAGS) $(srcdir)/xnee.texi
+
+
+# PDF for RedHat
+#xnee.pdf: xnee.texi 
+#	-$(TEXI2DVI) --pdf --batch $(srcdir)/xnee.texi
+
+# PDF for Debian
+#xnee.pdf: xnee.ps $(GEN_IMAGES)
+#	$(PS2PDF)  $(srcdir)/xnee.ps
+
+
+# DVI
+xnee.dvi: $(GEN_IMAGES)
+	$(TEXI2DVI) --batch $(srcdir)/xnee.texi
+
+
+# PS for RedHat
+#xnee.ps: xnee.pdf
+#	pdf2ps $(srcdir)/xnee.pdf
+
+# PS for Debian
+#xnee.ps: xnee.dvi $(GEN_IMAGES)
+#	$(DVI2PS) -c xnee.ps $(srcdir)/xnee.dvi
+#xnee.pdf: xnee.dvi $(GEN_IMAGES)
+#	$(DVIPDF) xnee.dvi xnee.pdf
+
+# PS for Debian
+#xnee.ps: xnee.pdf $(GEN_IMAGES)
+#	$(PDF2PS) $(srcdir)/xnee.pdf
+
+
+
+
+%.eps:%.dia
+	@echo "creating EPS"
+	$(DIA) --nosplash -e $@ $<
+
+%.pdf: %.texi
+	@echo "creating PDF"
+	$(TEXI2PDF)   $<
+
+%.pdf: %.eps
+	@echo "creating PDF"
+	$(EPSTOPDF) --outfile $@ $<
+
+%.png: %.eps
+	@echo "creating PNG"
+	$(CONVERT) -density 144x144 $< $@ 
+	( mv $@ `echo $@ | sed 's,\.png,_big\.png,g'` )
+	$(CONVERT) -density 32x32 $< $@ 
+	( mv $@ `echo $@ | sed 's,\.png,_small\.png,g'` )
+	$(CONVERT) -density 60x60 $< $@ 
+%.jpg: %.eps
+	echo "creating JPG"
+	$(CONVERT) -density 144x144 $< $@ 
+	( mv $@ `echo $@ | sed 's,\.jpg,_big\.jpg,g'` )
+	$(CONVERT) -density 32x32 $< $@ 
+	( mv $@ `echo $@ | sed 's,\.jpg,_small\.jpg,g'` )
+	$(CONVERT) -density 60x60 $< $@ 
+
+
+${IMG_EPS}: ${IMG_DIA}
+${IMG_PDF}: ${IMG_EPS} 
+${IMG_PNG}: ${IMG_EPS}
+${IMG_JPG}: ${IMG_EPS}
+
+install: 
+	mkdir -p $(DESTDIR)/$(docdir)
+	cp $(MANUALS) $(GEN_IMAGES_TO_INSTALL)  $(DESTDIR)$(docdir)/
+
+
+
+api-doc: xnee.dox 
+	\rm -fr alldocs/
+	-mkdir alldocs
+	-mkdir alldocs/devel
+	\rm -fr latex
+	$(DOXYGEN) xnee.dox 
+	cd latex && make ps && make pdf
+
+
+
+xnee.txt:
+	$(MAKEINFO) -o xnee.txt --no-headers --no-split --no-validate xnee.texi
+
+manual: $(MANUALS)
+all: $(DOC_DEP)
+default: all
+
+
+clean:  
+	-rm -f $(CLEANFILES)
+

--- /dev/null
+++ b/original/Makefile.in
@@ -0,0 +1,810 @@
+# Makefile.in generated by automake 1.11 from Makefile.am.
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008, 2009  Free Software Foundation,
+# Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+
+VPATH = @srcdir@
+pkgdatadir = $(datadir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkglibexecdir = $(libexecdir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+build_triplet = @build@
+host_triplet = @host@
+subdir = doc
+DIST_COMMON = README $(srcdir)/Makefile.am $(srcdir)/Makefile.in \
+	$(srcdir)/stamp-vti $(srcdir)/version.texi $(xnee_TEXINFOS) \
+	AUTHORS COPYING ChangeLog NEWS
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+	$(ACLOCAL_M4)
+mkinstalldirs = $(install_sh) -d
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+CONFIG_CLEAN_VPATH_FILES =
+SOURCES =
+DIST_SOURCES =
+INFO_DEPS = $(srcdir)/xnee.info
+TEXINFO_TEX = $(top_srcdir)/./autotools/texinfo.tex
+am__TEXINFO_TEX_DIR = $(top_srcdir)/./autotools
+DVIS = xnee.dvi
+PDFS = xnee.pdf
+PSS = xnee.ps
+HTMLS = xnee.html
+TEXINFOS = xnee.texi
+TEXI2DVI = texi2dvi
+MAKEINFOHTML = $(MAKEINFO) --html
+AM_MAKEINFOHTMLFLAGS = $(AM_MAKEINFOFLAGS)
+DVIPS = dvips
+am__installdirs = "$(DESTDIR)$(infodir)" "$(DESTDIR)$(docdir)"
+am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
+am__vpath_adj = case $$p in \
+    $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
+    *) f=$$p;; \
+  esac;
+am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
+am__install_max = 40
+am__nobase_strip_setup = \
+  srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
+am__nobase_strip = \
+  for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
+am__nobase_list = $(am__nobase_strip_setup); \
+  for p in $$list; do echo "$$p $$p"; done | \
+  sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
+  $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
+    if (++n[$$2] == $(am__install_max)) \
+      { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
+    END { for (dir in files) print dir, files[dir] }'
+am__base_list = \
+  sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
+  sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
+DATA = $(doc_DATA)
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+AR = @AR@
+AUTOCONF = @AUTOCONF@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+BASH = @BASH@
+CC = @CC@
+CCDEPMODE = @CCDEPMODE@
+CFLAGS = @CFLAGS@
+CLI_DIR = @CLI_DIR@
+CNEE_INFO = @CNEE_INFO@
+CONVERT = @CONVERT@
+CPP = @CPP@
+CPPFLAGS = @CPPFLAGS@
+CYGPATH_W = @CYGPATH_W@
+DEFS = @DEFS@
+DEPDIR = @DEPDIR@
+DIA = @DIA@
+DOC_DIR = @DOC_DIR@
+DOC_TARGETS = @DOC_TARGETS@
+DSYMUTIL = @DSYMUTIL@
+DUMPBIN = @DUMPBIN@
+DVIPDF = @DVIPDF@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+EGREP = @EGREP@
+EPSTOPDF = @EPSTOPDF@
+EXEEXT = @EXEEXT@
+FGREP = @FGREP@
+FOO_DIR = @FOO_DIR@
+GNOME_APPLET_DIR = @GNOME_APPLET_DIR@
+GREP = @GREP@
+GUI_DIR = @GUI_DIR@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+LD = @LD@
+LDFLAGS = @LDFLAGS@
+LIBDL = @LIBDL@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LIBSEMA = @LIBSEMA@
+LIBTOOL = @LIBTOOL@
+LIB_DIR = @LIB_DIR@
+LIPO = @LIPO@
+LN_S = @LN_S@
+LTLIBOBJS = @LTLIBOBJS@
+MAINT = @MAINT@
+MAKEFILES_TO_GEN = @MAKEFILES_TO_GEN@
+MAKEINFO = @MAKEINFO@
+MKDIR_P = @MKDIR_P@
+NM = @NM@
+NMEDIT = @NMEDIT@
+OBJDUMP = @OBJDUMP@
+OBJEXT = @OBJEXT@
+OTOOL = @OTOOL@
+OTOOL64 = @OTOOL64@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_URL = @PACKAGE_URL@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PANEL_APPLET_DIR = @PANEL_APPLET_DIR@
+PANEL_FLAGS = @PANEL_FLAGS@
+PANEL_LD_FLAGS = @PANEL_LD_FLAGS@
+PANEL_SERVER_DIR = @PANEL_SERVER_DIR@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+PDF2PS = @PDF2PS@
+PIXMAP_DIR = @PIXMAP_DIR@
+PKGCFG = @PKGCFG@
+PKG_CONFIG = @PKG_CONFIG@
+PS2PDF = @PS2PDF@
+RANLIB = @RANLIB@
+SED = @SED@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+TEXI2HTML = @TEXI2HTML@
+TEXI2PDF = @TEXI2PDF@
+VERSION = @VERSION@
+WANTED_LIBXNEE = @WANTED_LIBXNEE@
+X11_LIBS = @X11_LIBS@
+XMKMF = @XMKMF@
+XNEE_DOC_DIR = @XNEE_DOC_DIR@
+X_CFLAGS = @X_CFLAGS@
+X_EXTRA_LIBS = @X_EXTRA_LIBS@
+X_LIBS = @X_LIBS@
+X_PRE_LIBS = @X_PRE_LIBS@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+ac_ct_CC = @ac_ct_CC@
+ac_ct_DUMPBIN = @ac_ct_DUMPBIN@
+am__include = @am__include@
+am__leading_dot = @am__leading_dot@
+am__quote = @am__quote@
+am__tar = @am__tar@
+am__untar = @am__untar@
+bindir = @bindir@
+build = @build@
+build_alias = @build_alias@
+build_cpu = @build_cpu@
+build_os = @build_os@
+build_vendor = @build_vendor@
+builddir = @builddir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = $(datadir)/xnee
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+gtk_CFLAGS = @gtk_CFLAGS@
+gtk_LIBS = @gtk_LIBS@
+host = @host@
+host_alias = @host_alias@
+host_cpu = @host_cpu@
+host_os = @host_os@
+host_vendor = @host_vendor@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+libdir = @libdir@
+libexecdir = @libexecdir@
+libgnomeui_CFLAGS = @libgnomeui_CFLAGS@
+libgnomeui_LIBS = @libgnomeui_LIBS@
+localedir = @localedir@
+localstatedir = @localstatedir@
+lt_ECHO = @lt_ECHO@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+top_build_prefix = @top_build_prefix@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+xnee_TEXINFOS = xnee_error.texi xnee_prot.texi version.texi  xnee_error.texi xnee_exampl.texi xnee_faq.texi xnee_install.texi xnee_intro.texi xnee_req.texi xnee_synch.texi xnee_usage.texi xnee_general.texi xnee_start.texi  xnee_intern.texi xnee_copying fdl.texi xnee_func.texi xnee_progs.texi 
+IMG_DIA = xndetail.dia xngener.dia xnrec.dia xnrep.dia xnswinp.dia 
+IMG_EPS = xndetail.eps xngener.eps xnrec.eps xnrep.eps xnswinp.eps 
+IMG_PDF = xndetail.pdf xngener.pdf xnrec.pdf xnrep.pdf xnswinp.pdf 
+IMG_PNG = xndetail.png xngener.png xnrec.png xnrep.png xnswinp.png
+IMG_JPG = xndetail.jpg xngener.jpg xnrec.jpg xnrep.jpg xnswinp.jpg
+GEN_IMAGES = $(IMG_EPS) $(IMG_PDF) $(IMG_PNG) $(IMG_JPG)
+GEN_IMAGES_TO_INSTALL = $(IMG_PNG) $(IMG_JPG)
+MANUALS = xnee.html xnee.ps xnee.txt
+EXTRA_DIST = xnee_copying fdl.texi *.dia xnee.dox xnee.html xnee.pdf xnee.ps xnee.txt  \
+	$(GEN_IMAGES_TO_INSTALL) 
+
+#\
+#	$(MANUALS)
+@BUILDDOC_TRUE@DOC_DEP = $(GEN_IMAGES_TO_INSTALL) $(MANUALS)
+@BUILDDOC_TRUE@doc_DATA = $(MANUALS) $(GEN_IMAGES_TO_INSTALL)
+
+#MAKEINFO = @MAKEINFO@ --no-split
+#TEXI2HTML = texi2html
+#DVI2PS = dvi2ps
+#PS2PDF = ps2pdf
+###   TEXI2HTML_FLAGS = -split_chapter
+info_TEXINFOS = xnee.texi 
+CLEANFILES = xnee.acs  xnee.cvs  xnee.mss  xnee.prs \
+	     xnee.ats  xnee.evs  xnee.fns  xnee.ovs \
+             xnee.tmp  stamp-vti \
+             $(IMG_EPS) $(IMG_PDF) $(IMG_PNG) $(IMG_JPG) \
+             *.eps *.jpg *.png *.pdf *.html
+
+all: all-am
+
+.SUFFIXES:
+.SUFFIXES: .dvi .html .info .pdf .ps .texi
+$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am  $(am__configure_deps)
+	@for dep in $?; do \
+	  case '$(am__configure_deps)' in \
+	    *$$dep*) \
+	      ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \
+	        && { if test -f $@; then exit 0; else break; fi; }; \
+	      exit 1;; \
+	  esac; \
+	done; \
+	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu doc/Makefile'; \
+	$(am__cd) $(top_srcdir) && \
+	  $(AUTOMAKE) --gnu doc/Makefile
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+	@case '$?' in \
+	  *config.status*) \
+	    cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+	  *) \
+	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
+	    cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
+	esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps)
+	cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(am__aclocal_m4_deps):
+
+mostlyclean-libtool:
+	-rm -f *.lo
+
+clean-libtool:
+	-rm -rf .libs _libs
+
+.texi.info:
+	restore=: && backupdir="$(am__leading_dot)am$$$$" && \
+	am__cwd=`pwd` && $(am__cd) $(srcdir) && \
+	rm -rf $$backupdir && mkdir $$backupdir && \
+	if ($(MAKEINFO) --version) >/dev/null 2>&1; then \
+	  for f in $@ $@-[0-9] $@-[0-9][0-9] $(@:.info=).i[0-9] $(@:.info=).i[0-9][0-9]; do \
+	    if test -f $$f; then mv $$f $$backupdir; restore=mv; else :; fi; \
+	  done; \
+	else :; fi && \
+	cd "$$am__cwd"; \
+	if $(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I $(srcdir) \
+	 -o $@ $<; \
+	then \
+	  rc=0; \
+	  $(am__cd) $(srcdir); \
+	else \
+	  rc=$$?; \
+	  $(am__cd) $(srcdir) && \
+	  $$restore $$backupdir/* `echo "./$@" | sed 's|[^/]*$$||'`; \
+	fi; \
+	rm -rf $$backupdir; exit $$rc
+
+.texi.dvi:
+	TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
+	MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I $(srcdir)' \
+	$(TEXI2DVI) $<
+
+.texi.pdf:
+	TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
+	MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I $(srcdir)' \
+	$(TEXI2PDF) $<
+
+.texi.html:
+	rm -rf $(@:.html=.htp)
+	if $(MAKEINFOHTML) $(AM_MAKEINFOHTMLFLAGS) $(MAKEINFOFLAGS) -I $(srcdir) \
+	 -o $(@:.html=.htp) $<; \
+	then \
+	  rm -rf $@; \
+	  if test ! -d $(@:.html=.htp) && test -d $(@:.html=); then \
+	    mv $(@:.html=) $@; else mv $(@:.html=.htp) $@; fi; \
+	else \
+	  if test ! -d $(@:.html=.htp) && test -d $(@:.html=); then \
+	    rm -rf $(@:.html=); else rm -Rf $(@:.html=.htp) $@; fi; \
+	  exit 1; \
+	fi
+$(srcdir)/xnee.info: xnee.texi $(srcdir)/version.texi $(xnee_TEXINFOS)
+xnee.pdf: xnee.texi $(srcdir)/version.texi $(xnee_TEXINFOS)
+$(srcdir)/version.texi: @MAINTAINER_MODE_TRUE@ $(srcdir)/stamp-vti
+$(srcdir)/stamp-vti: xnee.texi $(top_srcdir)/configure
+	@(dir=.; test -f ./xnee.texi || dir=$(srcdir); \
+	set `$(SHELL) $(top_srcdir)/./autotools/mdate-sh $$dir/xnee.texi`; \
+	echo "@set UPDATED $$1 $$2 $$3"; \
+	echo "@set UPDATED-MONTH $$2 $$3"; \
+	echo "@set EDITION $(VERSION)"; \
+	echo "@set VERSION $(VERSION)") > vti.tmp
+	@cmp -s vti.tmp $(srcdir)/version.texi \
+	  || (echo "Updating $(srcdir)/version.texi"; \
+	      cp vti.tmp $(srcdir)/version.texi)
+	-@rm -f vti.tmp
+	@cp $(srcdir)/version.texi $@
+
+mostlyclean-vti:
+	-rm -f vti.tmp
+
+maintainer-clean-vti:
+@MAINTAINER_MODE_TRUE@	-rm -f $(srcdir)/stamp-vti $(srcdir)/version.texi
+.dvi.ps:
+	TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
+	$(DVIPS) -o $@ $<
+
+uninstall-dvi-am:
+	@$(NORMAL_UNINSTALL)
+	@list='$(DVIS)'; test -n "$(dvidir)" || list=; \
+	for p in $$list; do \
+	  $(am__strip_dir) \
+	  echo " rm -f '$(DESTDIR)$(dvidir)/$$f'"; \
+	  rm -f "$(DESTDIR)$(dvidir)/$$f"; \
+	done
+
+uninstall-html-am:
+	@$(NORMAL_UNINSTALL)
+	@list='$(HTMLS)'; test -n "$(htmldir)" || list=; \
+	for p in $$list; do \
+	  $(am__strip_dir) \
+	  echo " rm -rf '$(DESTDIR)$(htmldir)/$$f'"; \
+	  rm -rf "$(DESTDIR)$(htmldir)/$$f"; \
+	done
+
+uninstall-info-am:
+	@$(PRE_UNINSTALL)
+	@if test -d '$(DESTDIR)$(infodir)' && \
+	    (install-info --version && \
+	     install-info --version 2>&1 | sed 1q | grep -i -v debian) >/dev/null 2>&1; then \
+	  list='$(INFO_DEPS)'; \
+	  for file in $$list; do \
+	    relfile=`echo "$$file" | sed 's|^.*/||'`; \
+	    echo " install-info --info-dir='$(DESTDIR)$(infodir)' --remove '$(DESTDIR)$(infodir)/$$relfile'"; \
+	    if install-info --info-dir="$(DESTDIR)$(infodir)" --remove "$(DESTDIR)$(infodir)/$$relfile"; \
+	    then :; else test ! -f "$(DESTDIR)$(infodir)/$$relfile" || exit 1; fi; \
+	  done; \
+	else :; fi
+	@$(NORMAL_UNINSTALL)
+	@list='$(INFO_DEPS)'; \
+	for file in $$list; do \
+	  relfile=`echo "$$file" | sed 's|^.*/||'`; \
+	  relfile_i=`echo "$$relfile" | sed 's|\.info$$||;s|$$|.i|'`; \
+	  (if test -d "$(DESTDIR)$(infodir)" && cd "$(DESTDIR)$(infodir)"; then \
+	     echo " cd '$(DESTDIR)$(infodir)' && rm -f $$relfile $$relfile-[0-9] $$relfile-[0-9][0-9] $$relfile_i[0-9] $$relfile_i[0-9][0-9]"; \
+	     rm -f $$relfile $$relfile-[0-9] $$relfile-[0-9][0-9] $$relfile_i[0-9] $$relfile_i[0-9][0-9]; \
+	   else :; fi); \
+	done
+
+uninstall-pdf-am:
+	@$(NORMAL_UNINSTALL)
+	@list='$(PDFS)'; test -n "$(pdfdir)" || list=; \
+	for p in $$list; do \
+	  $(am__strip_dir) \
+	  echo " rm -f '$(DESTDIR)$(pdfdir)/$$f'"; \
+	  rm -f "$(DESTDIR)$(pdfdir)/$$f"; \
+	done
+
+uninstall-ps-am:
+	@$(NORMAL_UNINSTALL)
+	@list='$(PSS)'; test -n "$(psdir)" || list=; \
+	for p in $$list; do \
+	  $(am__strip_dir) \
+	  echo " rm -f '$(DESTDIR)$(psdir)/$$f'"; \
+	  rm -f "$(DESTDIR)$(psdir)/$$f"; \
+	done
+
+dist-info: $(INFO_DEPS)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; \
+	list='$(INFO_DEPS)'; \
+	for base in $$list; do \
+	  case $$base in \
+	    $(srcdir)/*) base=`echo "$$base" | sed "s|^$$srcdirstrip/||"`;; \
+	  esac; \
+	  if test -f $$base; then d=.; else d=$(srcdir); fi; \
+	  base_i=`echo "$$base" | sed 's|\.info$$||;s|$$|.i|'`; \
+	  for file in $$d/$$base $$d/$$base-[0-9] $$d/$$base-[0-9][0-9] $$d/$$base_i[0-9] $$d/$$base_i[0-9][0-9]; do \
+	    if test -f $$file; then \
+	      relfile=`expr "$$file" : "$$d/\(.*\)"`; \
+	      test -f "$(distdir)/$$relfile" || \
+		cp -p $$file "$(distdir)/$$relfile"; \
+	    else :; fi; \
+	  done; \
+	done
+
+mostlyclean-aminfo:
+	-rm -rf xnee.aux xnee.cp xnee.cps xnee.fn xnee.ky xnee.log xnee.pg xnee.tmp \
+	  xnee.toc xnee.tp xnee.tps xnee.vr
+
+clean-aminfo:
+	-test -z "xnee.dvi xnee.pdf xnee.ps xnee.html" \
+	|| rm -rf xnee.dvi xnee.pdf xnee.ps xnee.html
+
+maintainer-clean-aminfo:
+	@list='$(INFO_DEPS)'; for i in $$list; do \
+	  i_i=`echo "$$i" | sed 's|\.info$$||;s|$$|.i|'`; \
+	  echo " rm -f $$i $$i-[0-9] $$i-[0-9][0-9] $$i_i[0-9] $$i_i[0-9][0-9]"; \
+	  rm -f $$i $$i-[0-9] $$i-[0-9][0-9] $$i_i[0-9] $$i_i[0-9][0-9]; \
+	done
+install-docDATA: $(doc_DATA)
+	@$(NORMAL_INSTALL)
+	test -z "$(docdir)" || $(MKDIR_P) "$(DESTDIR)$(docdir)"
+	@list='$(doc_DATA)'; test -n "$(docdir)" || list=; \
+	for p in $$list; do \
+	  if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
+	  echo "$$d$$p"; \
+	done | $(am__base_list) | \
+	while read files; do \
+	  echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(docdir)'"; \
+	  $(INSTALL_DATA) $$files "$(DESTDIR)$(docdir)" || exit $$?; \
+	done
+
+uninstall-docDATA:
+	@$(NORMAL_UNINSTALL)
+	@list='$(doc_DATA)'; test -n "$(docdir)" || list=; \
+	files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
+	test -n "$$files" || exit 0; \
+	echo " ( cd '$(DESTDIR)$(docdir)' && rm -f" $$files ")"; \
+	cd "$(DESTDIR)$(docdir)" && rm -f $$files
+tags: TAGS
+TAGS:
+
+ctags: CTAGS
+CTAGS:
+
+
+distdir: $(DISTFILES)
+	@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+	list='$(DISTFILES)'; \
+	  dist_files=`for file in $$list; do echo $$file; done | \
+	  sed -e "s|^$$srcdirstrip/||;t" \
+	      -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+	case $$dist_files in \
+	  */*) $(MKDIR_P) `echo "$$dist_files" | \
+			   sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+			   sort -u` ;; \
+	esac; \
+	for file in $$dist_files; do \
+	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+	  if test -d $$d/$$file; then \
+	    dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+	    if test -d "$(distdir)/$$file"; then \
+	      find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
+	    fi; \
+	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+	      cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
+	      find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
+	    fi; \
+	    cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
+	  else \
+	    test -f "$(distdir)/$$file" \
+	    || cp -p $$d/$$file "$(distdir)/$$file" \
+	    || exit 1; \
+	  fi; \
+	done
+	$(MAKE) $(AM_MAKEFLAGS) \
+	  top_distdir="$(top_distdir)" distdir="$(distdir)" \
+	  dist-info
+check-am: all-am
+check: check-am
+all-am: Makefile $(INFO_DEPS) $(DATA)
+installdirs:
+	for dir in "$(DESTDIR)$(infodir)" "$(DESTDIR)$(docdir)"; do \
+	  test -z "$$dir" || $(MKDIR_P) "$$dir"; \
+	done
+install-exec: install-exec-am
+install-data: install-data-am
+uninstall: uninstall-am
+
+install-am: all-am
+	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-am
+install-strip:
+	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+	  `test -z '$(STRIP)' || \
+	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+	-test -z "$(CLEANFILES)" || rm -f $(CLEANFILES)
+
+distclean-generic:
+	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+	-test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES)
+
+maintainer-clean-generic:
+	@echo "This command is intended for maintainers to use"
+	@echo "it deletes files that may require special tools to rebuild."
+clean-am: clean-aminfo clean-generic clean-libtool mostlyclean-am
+
+distclean: distclean-am
+	-rm -f Makefile
+distclean-am: clean-am distclean-generic
+
+dvi: dvi-am
+
+dvi-am: $(DVIS)
+
+html: html-am
+
+html-am: $(HTMLS)
+
+info: info-am
+
+info-am: $(INFO_DEPS)
+
+install-data-am: install-docDATA install-info-am
+
+install-dvi: install-dvi-am
+
+install-dvi-am: $(DVIS)
+	@$(NORMAL_INSTALL)
+	test -z "$(dvidir)" || $(MKDIR_P) "$(DESTDIR)$(dvidir)"
+	@list='$(DVIS)'; test -n "$(dvidir)" || list=; \
+	for p in $$list; do \
+	  if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
+	  echo "$$d$$p"; \
+	done | $(am__base_list) | \
+	while read files; do \
+	  echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(dvidir)'"; \
+	  $(INSTALL_DATA) $$files "$(DESTDIR)$(dvidir)" || exit $$?; \
+	done
+install-exec-am:
+
+install-html: install-html-am
+
+install-html-am: $(HTMLS)
+	@$(NORMAL_INSTALL)
+	test -z "$(htmldir)" || $(MKDIR_P) "$(DESTDIR)$(htmldir)"
+	@list='$(HTMLS)'; list2=; test -n "$(htmldir)" || list=; \
+	for p in $$list; do \
+	  if test -f "$$p" || test -d "$$p"; then d=; else d="$(srcdir)/"; fi; \
+	  $(am__strip_dir) \
+	  if test -d "$$d$$p"; then \
+	    echo " $(MKDIR_P) '$(DESTDIR)$(htmldir)/$$f'"; \
+	    $(MKDIR_P) "$(DESTDIR)$(htmldir)/$$f" || exit 1; \
+	    echo " $(INSTALL_DATA) '$$d$$p'/* '$(DESTDIR)$(htmldir)/$$f'"; \
+	    $(INSTALL_DATA) "$$d$$p"/* "$(DESTDIR)$(htmldir)/$$f" || exit $$?; \
+	  else \
+	    list2="$$list2 $$d$$p"; \
+	  fi; \
+	done; \
+	test -z "$$list2" || { echo "$$list2" | $(am__base_list) | \
+	while read files; do \
+	  echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(htmldir)'"; \
+	  $(INSTALL_DATA) $$files "$(DESTDIR)$(htmldir)" || exit $$?; \
+	done; }
+install-info: install-info-am
+
+install-info-am: $(INFO_DEPS)
+	@$(NORMAL_INSTALL)
+	test -z "$(infodir)" || $(MKDIR_P) "$(DESTDIR)$(infodir)"
+	@srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; \
+	list='$(INFO_DEPS)'; test -n "$(infodir)" || list=; \
+	for file in $$list; do \
+	  case $$file in \
+	    $(srcdir)/*) file=`echo "$$file" | sed "s|^$$srcdirstrip/||"`;; \
+	  esac; \
+	  if test -f $$file; then d=.; else d=$(srcdir); fi; \
+	  file_i=`echo "$$file" | sed 's|\.info$$||;s|$$|.i|'`; \
+	  for ifile in $$d/$$file $$d/$$file-[0-9] $$d/$$file-[0-9][0-9] \
+	               $$d/$$file_i[0-9] $$d/$$file_i[0-9][0-9] ; do \
+	    if test -f $$ifile; then \
+	      echo "$$ifile"; \
+	    else : ; fi; \
+	  done; \
+	done | $(am__base_list) | \
+	while read files; do \
+	  echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(infodir)'"; \
+	  $(INSTALL_DATA) $$files "$(DESTDIR)$(infodir)" || exit $$?; done
+	@$(POST_INSTALL)
+	@if (install-info --version && \
+	     install-info --version 2>&1 | sed 1q | grep -i -v debian) >/dev/null 2>&1; then \
+	  list='$(INFO_DEPS)'; test -n "$(infodir)" || list=; \
+	  for file in $$list; do \
+	    relfile=`echo "$$file" | sed 's|^.*/||'`; \
+	    echo " install-info --info-dir='$(DESTDIR)$(infodir)' '$(DESTDIR)$(infodir)/$$relfile'";\
+	    install-info --info-dir="$(DESTDIR)$(infodir)" "$(DESTDIR)$(infodir)/$$relfile" || :;\
+	  done; \
+	else : ; fi
+install-man:
+
+install-pdf: install-pdf-am
+
+install-pdf-am: $(PDFS)
+	@$(NORMAL_INSTALL)
+	test -z "$(pdfdir)" || $(MKDIR_P) "$(DESTDIR)$(pdfdir)"
+	@list='$(PDFS)'; test -n "$(pdfdir)" || list=; \
+	for p in $$list; do \
+	  if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
+	  echo "$$d$$p"; \
+	done | $(am__base_list) | \
+	while read files; do \
+	  echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(pdfdir)'"; \
+	  $(INSTALL_DATA) $$files "$(DESTDIR)$(pdfdir)" || exit $$?; done
+install-ps: install-ps-am
+
+install-ps-am: $(PSS)
+	@$(NORMAL_INSTALL)
+	test -z "$(psdir)" || $(MKDIR_P) "$(DESTDIR)$(psdir)"
+	@list='$(PSS)'; test -n "$(psdir)" || list=; \
+	for p in $$list; do \
+	  if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
+	  echo "$$d$$p"; \
+	done | $(am__base_list) | \
+	while read files; do \
+	  echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(psdir)'"; \
+	  $(INSTALL_DATA) $$files "$(DESTDIR)$(psdir)" || exit $$?; done
+installcheck-am:
+
+maintainer-clean: maintainer-clean-am
+	-rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-aminfo \
+	maintainer-clean-generic maintainer-clean-vti
+
+mostlyclean: mostlyclean-am
+
+mostlyclean-am: mostlyclean-aminfo mostlyclean-generic \
+	mostlyclean-libtool mostlyclean-vti
+
+pdf: pdf-am
+
+pdf-am: $(PDFS)
+
+ps: ps-am
+
+ps-am: $(PSS)
+
+uninstall-am: uninstall-docDATA uninstall-dvi-am uninstall-html-am \
+	uninstall-info-am uninstall-pdf-am uninstall-ps-am
+
+.MAKE: install-am install-strip
+
+.PHONY: all all-am check check-am clean clean-aminfo clean-generic \
+	clean-libtool dist-info distclean distclean-generic \
+	distclean-libtool distdir dvi dvi-am html html-am info info-am \
+	install install-am install-data install-data-am \
+	install-docDATA install-dvi install-dvi-am install-exec \
+	install-exec-am install-html install-html-am install-info \
+	install-info-am install-man install-pdf install-pdf-am \
+	install-ps install-ps-am install-strip installcheck \
+	installcheck-am installdirs maintainer-clean \
+	maintainer-clean-aminfo maintainer-clean-generic \
+	maintainer-clean-vti mostlyclean mostlyclean-aminfo \
+	mostlyclean-generic mostlyclean-libtool mostlyclean-vti pdf \
+	pdf-am ps ps-am uninstall uninstall-am uninstall-docDATA \
+	uninstall-dvi-am uninstall-html-am uninstall-info-am \
+	uninstall-pdf-am uninstall-ps-am
+
+
+# HTML
+xnee.html: xnee.texi $(GEN_IMAGES)
+	$(TEXI2HTML) $(TEXI2HTML_FLAGS) $(srcdir)/xnee.texi
+
+# PDF for RedHat
+#xnee.pdf: xnee.texi 
+#	-$(TEXI2DVI) --pdf --batch $(srcdir)/xnee.texi
+
+# PDF for Debian
+#xnee.pdf: xnee.ps $(GEN_IMAGES)
+#	$(PS2PDF)  $(srcdir)/xnee.ps
+
+# DVI
+xnee.dvi: $(GEN_IMAGES)
+	$(TEXI2DVI) --batch $(srcdir)/xnee.texi
+
+# PS for RedHat
+#xnee.ps: xnee.pdf
+#	pdf2ps $(srcdir)/xnee.pdf
+
+# PS for Debian
+#xnee.ps: xnee.dvi $(GEN_IMAGES)
+#	$(DVI2PS) -c xnee.ps $(srcdir)/xnee.dvi
+#xnee.pdf: xnee.dvi $(GEN_IMAGES)
+#	$(DVIPDF) xnee.dvi xnee.pdf
+
+# PS for Debian
+#xnee.ps: xnee.pdf $(GEN_IMAGES)
+#	$(PDF2PS) $(srcdir)/xnee.pdf
+
+%.eps:%.dia
+	@echo "creating EPS"
+	$(DIA) --nosplash -e $@ $<
+
+%.pdf: %.texi
+	@echo "creating PDF"
+	$(TEXI2PDF)   $<
+
+%.pdf: %.eps
+	@echo "creating PDF"
+	$(EPSTOPDF) --outfile $@ $<
+
+%.png: %.eps
+	@echo "creating PNG"
+	$(CONVERT) -density 144x144 $< $@ 
+	( mv $@ `echo $@ | sed 's,\.png,_big\.png,g'` )
+	$(CONVERT) -density 32x32 $< $@ 
+	( mv $@ `echo $@ | sed 's,\.png,_small\.png,g'` )
+	$(CONVERT) -density 60x60 $< $@ 
+%.jpg: %.eps
+	echo "creating JPG"
+	$(CONVERT) -density 144x144 $< $@ 
+	( mv $@ `echo $@ | sed 's,\.jpg,_big\.jpg,g'` )
+	$(CONVERT) -density 32x32 $< $@ 
+	( mv $@ `echo $@ | sed 's,\.jpg,_small\.jpg,g'` )
+	$(CONVERT) -density 60x60 $< $@ 
+
+${IMG_EPS}: ${IMG_DIA}
+${IMG_PDF}: ${IMG_EPS} 
+${IMG_PNG}: ${IMG_EPS}
+${IMG_JPG}: ${IMG_EPS}
+
+install: 
+	mkdir -p $(DESTDIR)/$(docdir)
+	cp $(MANUALS) $(GEN_IMAGES_TO_INSTALL)  $(DESTDIR)$(docdir)/
+
+api-doc: xnee.dox 
+	\rm -fr alldocs/
+	-mkdir alldocs
+	-mkdir alldocs/devel
+	\rm -fr latex
+	$(DOXYGEN) xnee.dox 
+	cd latex && make ps && make pdf
+
+xnee.txt:
+	$(MAKEINFO) -o xnee.txt --no-headers --no-split --no-validate xnee.texi
+
+manual: $(MANUALS)
+all: $(DOC_DEP)
+default: all
+
+clean:  
+	-rm -f $(CLEANFILES)
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:

--- /dev/null
+++ b/original/NEWS
@@ -0,0 +1,200 @@
+libxnee / NEWS 
+----------------------------
+  This file contains major news about cnee which is a part
+  of the Xnee project.
+
+  For more information about Xnee, http://www.gnu.org
+
+
+
+All text below concerns the old structure of Xnee
+------------------------------------------------------------------------------
+
+
+
+xnee / NEWS 
+----------------------------
+
+Changes in 
+	- new options:
+	   '--data-to-record'
+	   '--events-to-record'
+	   '--time-to-record'
+	   '--event-range'
+
+
+Changes in 1.08
+	- new options:
+	   '--write-settings'      writes a resource file from settings done
+	   '--mouse'               sets up ranges for all mouse events
+	   '--keyboard'            sets up ranges for all keynoard events
+	   '--recorded-resolution' resolution used when recording
+	   '--replay-resolution'   resolution to use when replaying
+	   '--no-resolution-adjustment'   Don't use resolution adjustment
+	   '--speed-percent [percent]'   change the replaying speed
+	   '--pause-key [k m]'         key+modifier pauses xnee's current action
+	   '--pause-key [k m]'         key+modifier resume xnee's paused action
+	   '--insert-key [k m]'        key+modifier inserts a meta mark in the log file
+	   '--max-threshold [nr]'      sets the maximum threshold during sync
+	   '--min-threshold [nr]'      sets the maximum threshold during sync
+	   '--tot-threshold [nr]'      sets the total threshold during sync
+	   '--retype-file [file]'      retype the contents of file
+	   '--retype-help '            retype the help printout
+        - synchronisation rewritten 
+
+Changes in 1.07
+	- version numbering changed (x.yz is used instead of x.y.z)
+	- plugin functionality renamed to resource
+	- plugin functionality added (plug in dynamic libs)
+	- synchronization rewritten
+	- force-replay option added
+	- replay delay rewritten
+	- Xnee can be configured (during configure) to:
+	  + exclude buffer verbose
+	- print functions replaced by function pointers
+	  in dispatch functions, 
+	- Added modifier+key binding to pause, resume 
+	
+Changes in 1.0.6
+	- data names can now be more then 10 chars long ... errrh
+	- Xnee can be configured to:
+	  + exclude verbose mode
+	  + gcov compilation
+	  + grpof compilation
+	- new or modified options:
+	  '--print-event-names'   prints all event names and number
+	  '--print-request-names' prints all request names and number
+	  '--print-event-names'   prints event name or  number
+	  '--print-request-names' prints request names or number
+
+Changes in 1.0.6pre1
+	- multiple modifiers added
+	- data names can be used when setting ranges
+	- docs updated with the above changes
+	- range setting (when replaying) bug corrected
+	- speed increased (removed recording of device event when replying)
+	- Xnee is now a GNU package
+
+Changes in 1.0.5
+	- Typos corrected in doc/ & README (after GNU review)
+	- Fiex parser error (--no_sync ----> --no-sync )
+	- Manual corrected (after GNU review)
+	- new options added to ease up usage a bit:
+	   '--print-event-name' 
+	   '--print-error-name' 
+	   '--print-reply-name' 
+	   '--print-request-name' 
+	   '--print-data-name' 
+	- info, manuals updated
+
+Changes in 1.0.4
+	- changed printout for --help and --version
+	- made ChangeLog what is supposed to be 	
+	  build.sh doesn't copy NEWS to ChangeLog anymore
+	- xnee manual is now under FDL
+	- xnee developer manual is now under FDL
+	- TODO updated with GNU Coding Standard todos
+	- doc (texi) files updated with index refs
+	- doc (texi) files updated to make info pages nice
+	- build_web.sh added to CVS
+	- fixed one sigbus & one sigsegv on non-glibc platforms (thanks freeBSD)
+		
+Changes in 1.0.3
+	- fixed parse error (mainor_range  ---> minor_range )
+	- switched to CLI options syntax as recommended by the GNU Coding Standards 
+	- fixed a seg fault when closing down recording
+
+Changes in 1.0.2
+	- stop_key is now correctly parsed (man page updated)
+	- CPU consuming calls to XRecordProcessReplies removed
+	- Async recording is not used anymore
+	- Fixed memory leak (a few bytes when closing down)
+	- man page corrected
+	- help printout corrected
+
+Changes in 1.0.1
+	- Fixed memory leak
+
+Changes in 1.0
+	- Added --stop_key option to CLI and plugin files and record file
+	- Added --future_clients option to CLI
+	- Manual in pdf has moved to Documentation package
+	- Manual updated
+	- Example session included
+	- Source code is documented (using doxygen)
+	- man pages are generated from xnee binary
+	- Xnee now comes in two packages Program and Documentation
+
+Changes in 0.9
+	- new command line options:
+		--print_settings
+	- xnee reads (and uses) settings from recorded file
+	- added texi files (pdf, html, txt manuals)
+	- added man page
+	- EXAMPLES file updated 
+	- redhat specs updated
+
+Changes in 0.9beta
+	- ugly printout when using delayed startup removed
+	- MANUAL added
+
+Changes in 0.9alpha
+	- synchronisation works .... at last  :)
+	- removed a lot of duplicated code
+	- The following option has been updated
+	 1) help 
+	 2) binary 
+	 3) out "stdout" in plugin scripts is treated  
+	    as stdout (not creating a file called stdout)
+	 4) err "stderr" in plugin scripts is treated
+	    as stderr (not creating a file called stderr)
+	- DESCRIPTION, EXAMPLES, FAQ, README, TODO updated
+	- DEVELOPMENT added
+
+Changes in 0.8.1
+	- fixed a hanging (not on all platforms) xnee when finished replaying
+	- fixed dependency to libxnee for the xnee binary in the generated Makefiles
+	- fiexd missing newline in help text
+
+Changes in 0.8
+	- minor bugfixes
+	- copyright years added 
+	- the depcomp script have been added. 
+	- It compiles and runs on Solaris8 (intel) and Windows98/Cygwin/Xfree86. 
+	- The order of libs to be linked has changed. 
+
+Changes in 0.8beta
+	- --time  options now works 
+	- Pressing Ctrl-C will stop Xnee but __NOT__ remove the recorded file
+
+Changes in 0.8alpha
+	- worked around the bug* that crashed the X server when recording
+	delivered events.
+	
+	*) I still do not know where the bug is located (e.g xnee, X, RECORD)
+
+
+Changes in 0.7.2
+	- "plugins / xnee settings" is from now on only called plugin .. sorry about the fuzz
+	- Support for RedHat RPM/SRPMS is included is distribution
+	- build.sh is extended to build from clean dist to RPMs
+
+Changes in 0.7.1
+	- Support for plugins / xnee settings file is corrected
+
+Changes in 0.7
+	- Delay works fine 
+	- System info printing is back ... never missed it really since replay doesn't use it .. yet
+	- Support for plugins / xnee settings file is added
+
+
+Changes in 0.7alpha_2
+	- Xnee can now record delivered events (used FutureClients)
+	  without crashing
+	- First event not recorded (thank to Ton van Vliet)
+
+Changes in 0.7alpha_1
+	- Seg. fault on debian fixed
+	- Mem fault on OpenBSD fixed
+	- Xnee is now (at last) "autoconfed"
+

--- /dev/null
+++ b/original/README
@@ -0,0 +1,26 @@
+Xnee / README
+-------------
+
+Xnee is a GNU package. For more information about GNU, please visit 
+	http://www.gnu.org
+
+
+
+
+The following files contains information about Xnee
+
+Name		Description
+---------------------------
+AUTHORS		List of authors, contributors etc 
+BUGS		Known bugs and limitations
+Changelog	Log of source code changes
+COPYING		Contains the Xnee license
+DESCRIPTION	Obsolete*
+DEVELOPMENT	Obsolete*
+EXAMPLES	Obsolete*
+FAQ		Obsolete*
+INSTALL		Contains information about how to build and install Xnee
+NEWS		Contains information about what is new in "this" release
+README		This file
+TODO		List of features, fixes, docs,  ... to implement 
+USAGE		A printout of Xnee's built in doc, 'xnee --help'

--- /dev/null
+++ b/original/fdl.texi
@@ -0,0 +1,411 @@
+@appendixsec GNU Free Documentation License
+
+@cindex FDL, GNU Free Documentation License
+@center Version 1.2, November 2002
+
+@display
+Copyright @copyright{} 2000,2001,2002 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+@end display
+
+@enumerate 0
+@item
+PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document @dfn{free} in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+
+This License is a kind of ``copyleft'', which means that derivative
+works of the document must themselves be free in the same sense.  It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does.  But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book.  We recommend this License
+principally for works whose purpose is instruction or reference.
+
+@item
+APPLICABILITY AND DEFINITIONS
+
+This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License.  Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein.  The ``Document'', below,
+refers to any such manual or work.  Any member of the public is a
+licensee, and is addressed as ``you''.  You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+A ``Modified Version'' of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+A ``Secondary Section'' is a named appendix or a front-matter section
+of the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall
+subject (or to related matters) and contains nothing that could fall
+directly within that overall subject.  (Thus, if the Document is in
+part a textbook of mathematics, a Secondary Section may not explain
+any mathematics.)  The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+The ``Invariant Sections'' are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License.  If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant.  The Document may contain zero
+Invariant Sections.  If the Document does not identify any Invariant
+Sections then there are none.
+
+The ``Cover Texts'' are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License.  A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+A ``Transparent'' copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters.  A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text.  A copy that is not ``Transparent'' is called ``Opaque''.
+
+Examples of suitable formats for Transparent copies include plain
+@sc{ascii} without markup, Texinfo input format, La@TeX{} input
+format, @acronym{SGML} or @acronym{XML} using a publicly available
+@acronym{DTD}, and standard-conforming simple @acronym{HTML},
+PostScript or @acronym{PDF} designed for human modification.  Examples
+of transparent image formats include @acronym{PNG}, @acronym{XCF} and
+@acronym{JPG}.  Opaque formats include proprietary formats that can be
+read and edited only by proprietary word processors, @acronym{SGML} or
+@acronym{XML} for which the @acronym{DTD} and/or processing tools are
+not generally available, and the machine-generated @acronym{HTML},
+PostScript or @acronym{PDF} produced by some word processors for
+output purposes only.
+
+The ``Title Page'' means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page.  For works in
+formats which do not have any title page as such, ``Title Page'' means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+A section ``Entitled XYZ'' means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language.  (Here XYZ stands for a
+specific section name mentioned below, such as ``Acknowledgements'',
+``Dedications'', ``Endorsements'', or ``History''.)  To ``Preserve the Title''
+of such a section when you modify the Document means that it remains a
+section ``Entitled XYZ'' according to this definition.
+
+The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document.  These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+
+@item
+VERBATIM COPYING
+
+You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License.  You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute.  However, you may accept
+compensation in exchange for copies.  If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+@item
+COPYING IN QUANTITY
+
+If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover.  Both covers must also clearly and legibly identify
+you as the publisher of these copies.  The front cover must present
+the full title with all words of the title equally prominent and
+visible.  You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+
+@item
+MODIFICATIONS
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it.  In addition, you must do these things in the Modified Version:
+
+@enumerate A
+@item
+Use in the Title Page (and on the covers, if any) a title distinct
+from that of the Document, and from those of previous versions
+(which should, if there were any, be listed in the History section
+of the Document).  You may use the same title as a previous version
+if the original publisher of that version gives permission.
+
+@item
+List on the Title Page, as authors, one or more persons or entities
+responsible for authorship of the modifications in the Modified
+Version, together with at least five of the principal authors of the
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.
+
+@item
+State on the Title page the name of the publisher of the
+Modified Version, as the publisher.
+
+@item
+Preserve all the copyright notices of the Document.
+
+@item
+Add an appropriate copyright notice for your modifications
+adjacent to the other copyright notices.
+
+@item
+Include, immediately after the copyright notices, a license notice
+giving the public permission to use the Modified Version under the
+terms of this License, in the form shown in the Addendum below.
+
+@item
+Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document's license notice.
+
+@item
+Include an unaltered copy of this License.
+
+@item
+Preserve the section Entitled ``History'', Preserve its Title, and add
+to it an item stating at least the title, year, new authors, and
+publisher of the Modified Version as given on the Title Page.  If
+there is no section Entitled ``History'' in the Document, create one
+stating the title, year, authors, and publisher of the Document as
+given on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.
+
+@item
+Preserve the network location, if any, given in the Document for
+public access to a Transparent copy of the Document, and likewise
+the network locations given in the Document for previous versions
+it was based on.  These may be placed in the ``History'' section.
+You may omit a network location for a work that was published at
+least four years before the Document itself, or if the original
+publisher of the version it refers to gives permission.
+
+@item
+For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
+the Title of the section, and preserve in the section all the
+substance and tone of each of the contributor acknowledgements and/or
+dedications given therein.
+
+@item
+Preserve all the Invariant Sections of the Document,
+unaltered in their text and in their titles.  Section numbers
+or the equivalent are not considered part of the section titles.
+
+@item
+Delete any section Entitled ``Endorsements''.  Such a section
+may not be included in the Modified Version.
+
+@item
+Do not retitle any existing section to be Entitled ``Endorsements'' or
+to conflict in title with any Invariant Section.
+
+@item
+Preserve any Warranty Disclaimers.
+@end enumerate
+
+If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant.  To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+You may add a section Entitled ``Endorsements'', provided it contains
+nothing but endorsements of your Modified Version by various
+parties---for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version.  Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity.  If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
+@item
+COMBINING DOCUMENTS
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+
+The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy.  If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+In the combination, you must combine any sections Entitled ``History''
+in the various original documents, forming one section Entitled
+``History''; likewise combine any sections Entitled ``Acknowledgements'',
+and any sections Entitled ``Dedications''.  You must delete all
+sections Entitled ``Endorsements.''
+
+@item
+COLLECTIONS OF DOCUMENTS
+
+You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+
+You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+
+@item
+AGGREGATION WITH INDEPENDENT WORKS
+
+A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an ``aggregate'' if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+
+@item
+TRANSLATION
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections.  You may include a
+translation of this License, and all the license notices in the
+Document, and any Warrany Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers.  In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+If a section in the Document is Entitled ``Acknowledgements'',
+``Dedications'', or ``History'', the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+
+@item
+TERMINATION
+
+You may not copy, modify, sublicense, or distribute the Document except
+as expressly provided for under this License.  Any other attempt to
+copy, modify, sublicense or distribute the Document is void, and will
+automatically terminate your rights under this License.  However,
+parties who have received copies, or rights, from you under this
+License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+@item
+FUTURE REVISIONS OF THIS LICENSE
+
+The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation License from time to time.  Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.  See
+@uref{http://www.gnu.org/copyleft/}.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License ``or any later version'' applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation.  If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation.
+@end enumerate
+
+@page
+
+
+

--- /dev/null
+++ b/original/stamp-vti
@@ -0,0 +1,4 @@
+@set UPDATED 26 May 2009
+@set UPDATED-MONTH May 2009
+@set EDITION 3.05
+@set VERSION 3.05

--- /dev/null
+++ b/original/version.texi
@@ -0,0 +1,4 @@
+@set UPDATED 26 May 2009
+@set UPDATED-MONTH May 2009
+@set EDITION 3.05
+@set VERSION 3.05

Binary files /dev/null and b/original/xndetail.dia differ

Binary files /dev/null and b/original/xndetail.jpg differ

Binary files /dev/null and b/original/xndetail.png differ

--- /dev/null
+++ b/original/xnee.dox
@@ -0,0 +1,993 @@
+# Doxyfile 1.2.18
+
+# This file describes the settings to be used by the documentation system
+# doxygen (www.doxygen.org) for a project
+#
+# All text after a hash (#) is considered a comment and will be ignored
+# The format is:
+#       TAG = value [value, ...]
+# For lists items can also be appended using:
+#       TAG += value [value, ...]
+# Values that contain spaces should be placed between quotes (" ")
+
+#---------------------------------------------------------------------------
+# General configuration options
+#---------------------------------------------------------------------------
+
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
+# by quotes) that should identify the project.
+
+PROJECT_NAME           = Xnee
+
+# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
+# This could be handy for archiving the generated documentation or 
+# if some version control system is used.
+
+PROJECT_NUMBER         = 
+
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
+# base path where the generated documentation will be put. 
+# If a relative path is entered, it will be relative to the location 
+# where doxygen was started. If left blank the current directory will be used.
+
+OUTPUT_DIRECTORY       = 
+
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
+# documentation generated by doxygen is written. Doxygen will use this 
+# information to generate all constant output in the proper language. 
+# The default language is English, other supported languages are: 
+# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, 
+# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en 
+# (Japanese with english messages), Korean, Norwegian, Polish, Portuguese, 
+# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish and Ukrainian.
+
+OUTPUT_LANGUAGE        = English
+
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
+# documentation are documented, even if no documentation was available. 
+# Private class members and static file members will be hidden unless 
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
+
+EXTRACT_ALL            = YES
+
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
+# will be included in the documentation.
+
+EXTRACT_PRIVATE        = NO
+
+# If the EXTRACT_STATIC tag is set to YES all static members of a file 
+# will be included in the documentation.
+
+EXTRACT_STATIC         = NO
+
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
+# defined locally in source files will be included in the documentation. 
+# If set to NO only classes defined in header files are included.
+
+EXTRACT_LOCAL_CLASSES  = YES
+
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
+# undocumented members of documented classes, files or namespaces. 
+# If set to NO (the default) these members will be included in the 
+# various overviews, but no documentation section is generated. 
+# This option has no effect if EXTRACT_ALL is enabled.
+
+HIDE_UNDOC_MEMBERS     = NO
+
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
+# undocumented classes that are normally visible in the class hierarchy. 
+# If set to NO (the default) these class will be included in the various 
+# overviews. This option has no effect if EXTRACT_ALL is enabled.
+
+HIDE_UNDOC_CLASSES     = NO
+
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
+# friend (class|struct|union) declarations. 
+# If set to NO (the default) these declarations will be included in the 
+# documentation.
+
+HIDE_FRIEND_COMPOUNDS  = NO
+
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
+# include brief member descriptions after the members that are listed in 
+# the file and class documentation (similar to JavaDoc). 
+# Set to NO to disable this.
+
+BRIEF_MEMBER_DESC      = YES
+
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
+# the brief description of a member or function before the detailed description. 
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
+# brief descriptions will be completely suppressed.
+
+REPEAT_BRIEF           = YES
+
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
+# Doxygen will generate a detailed section even if there is only a brief 
+# description.
+
+ALWAYS_DETAILED_SEC    = NO
+
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited 
+# members of a class in the documentation of that class as if those members were 
+# ordinary class members. Constructors, destructors and assignment operators of 
+# the base classes will not be shown.
+
+INLINE_INHERITED_MEMB  = NO
+
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
+# path before files name in the file list and in the header files. If set 
+# to NO the shortest path that makes the file name unique will be used.
+
+FULL_PATH_NAMES        = NO
+
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
+# can be used to strip a user defined part of the path. Stripping is 
+# only done if one of the specified strings matches the left-hand part of 
+# the path. It is allowed to use relative paths in the argument list.
+
+STRIP_FROM_PATH        = 
+
+# The INTERNAL_DOCS tag determines if documentation 
+# that is typed after a \internal command is included. If the tag is set 
+# to NO (the default) then the documentation will be excluded. 
+# Set it to YES to include the internal documentation.
+
+INTERNAL_DOCS          = NO
+
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
+# doxygen to hide any special comment blocks from generated source code 
+# fragments. Normal C and C++ comments will always remain visible.
+
+STRIP_CODE_COMMENTS    = YES
+
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
+# file names in lower case letters. If set to YES upper case letters are also 
+# allowed. This is useful if you have classes or files whose names only differ 
+# in case and if your file system supports case sensitive file names. Windows 
+# users are adviced to set this option to NO.
+
+CASE_SENSE_NAMES       = YES
+
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
+# (but less readable) file names. This can be useful is your file systems 
+# doesn't support long names like on DOS, Mac, or CD-ROM.
+
+SHORT_NAMES            = NO
+
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
+# will show members with their full class and namespace scopes in the 
+# documentation. If set to YES the scope will be hidden.
+
+HIDE_SCOPE_NAMES       = NO
+
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
+# will generate a verbatim copy of the header file for each class for 
+# which an include is specified. Set to NO to disable this.
+
+VERBATIM_HEADERS       = YES
+
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
+# will put list of the files that are included by a file in the documentation 
+# of that file.
+
+SHOW_INCLUDE_FILES     = YES
+
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
+# will interpret the first line (until the first dot) of a JavaDoc-style 
+# comment as the brief description. If set to NO, the JavaDoc 
+# comments  will behave just like the Qt-style comments (thus requiring an 
+# explict @brief command for a brief description.
+
+JAVADOC_AUTOBRIEF      = NO
+
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
+# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
+# comments) as a brief description. This used to be the default behaviour. 
+# The new default is to treat a multi-line C++ comment block as a detailed 
+# description. Set this tag to YES if you prefer the old behaviour instead.
+
+MULTILINE_CPP_IS_BRIEF = NO
+
+# If the DETAILS_AT_TOP tag is set to YES then Doxygen 
+# will output the detailed description near the top, like JavaDoc.
+# If set to NO, the detailed description appears after the member 
+# documentation.
+
+DETAILS_AT_TOP         = NO
+
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
+# member inherits the documentation from any documented member that it 
+# reimplements.
+
+INHERIT_DOCS           = YES
+
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
+# is inserted in the documentation for inline members.
+
+INLINE_INFO            = YES
+
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
+# will sort the (detailed) documentation of file and class members 
+# alphabetically by member name. If set to NO the members will appear in 
+# declaration order.
+
+SORT_MEMBER_DOCS       = YES
+
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
+# tag is set to YES, then doxygen will reuse the documentation of the first 
+# member in the group (if any) for the other members of the group. By default 
+# all members of a group must be documented explicitly.
+
+DISTRIBUTE_GROUP_DOC   = NO
+
+# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
+# Doxygen uses this value to replace tabs by spaces in code fragments.
+
+TAB_SIZE               = 8
+
+# The GENERATE_TODOLIST tag can be used to enable (YES) or 
+# disable (NO) the todo list. This list is created by putting \todo 
+# commands in the documentation.
+
+GENERATE_TODOLIST      = YES
+
+# The GENERATE_TESTLIST tag can be used to enable (YES) or 
+# disable (NO) the test list. This list is created by putting \test 
+# commands in the documentation.
+
+GENERATE_TESTLIST      = YES
+
+# The GENERATE_BUGLIST tag can be used to enable (YES) or 
+# disable (NO) the bug list. This list is created by putting \bug 
+# commands in the documentation.
+
+GENERATE_BUGLIST       = YES
+
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
+# disable (NO) the deprecated list. This list is created by putting \deprecated commands in the documentation.
+
+GENERATE_DEPRECATEDLIST= YES
+
+# This tag can be used to specify a number of aliases that acts 
+# as commands in the documentation. An alias has the form "name=value". 
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
+# put the command \sideeffect (or @sideeffect) in the documentation, which 
+# will result in a user defined paragraph with heading "Side Effects:". 
+# You can put \n's in the value part of an alias to insert newlines.
+
+ALIASES                = 
+
+# The ENABLED_SECTIONS tag can be used to enable conditional 
+# documentation sections, marked by \if sectionname ... \endif.
+
+ENABLED_SECTIONS       = 
+
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
+# the initial value of a variable or define consist of for it to appear in 
+# the documentation. If the initializer consists of more lines than specified 
+# here it will be hidden. Use a value of 0 to hide initializers completely. 
+# The appearance of the initializer of individual variables and defines in the 
+# documentation can be controlled using \showinitializer or \hideinitializer 
+# command in the documentation regardless of this setting.
+
+MAX_INITIALIZER_LINES  = 30
+
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources 
+# only. Doxygen will then generate output that is more tailored for C. 
+# For instance some of the names that are used will be different. The list 
+# of all members will be omitted, etc.
+
+OPTIMIZE_OUTPUT_FOR_C  = YES
+
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources 
+# only. Doxygen will then generate output that is more tailored for Java. 
+# For instance namespaces will be presented as packages, qualified scopes 
+# will look different, etc.
+
+OPTIMIZE_OUTPUT_JAVA   = NO
+
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
+# at the bottom of the documentation of classes and structs. If set to YES the 
+# list will mention the files that were used to generate the documentation.
+
+SHOW_USED_FILES        = YES
+
+#---------------------------------------------------------------------------
+# configuration options related to warning and progress messages
+#---------------------------------------------------------------------------
+
+# The QUIET tag can be used to turn on/off the messages that are generated 
+# by doxygen. Possible values are YES and NO. If left blank NO is used.
+
+QUIET                  = NO
+
+# The WARNINGS tag can be used to turn on/off the warning messages that are 
+# generated by doxygen. Possible values are YES and NO. If left blank 
+# NO is used.
+
+WARNINGS               = YES
+
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
+# automatically be disabled.
+
+WARN_IF_UNDOCUMENTED   = YES
+
+# The WARN_FORMAT tag determines the format of the warning messages that 
+# doxygen can produce. The string should contain the $file, $line, and $text 
+# tags, which will be replaced by the file and line number from which the 
+# warning originated and the warning text.
+
+WARN_FORMAT            = "$file:$line: $text"
+
+# The WARN_LOGFILE tag can be used to specify a file to which warning 
+# and error messages should be written. If left blank the output is written 
+# to stderr.
+
+WARN_LOGFILE           = 
+
+#---------------------------------------------------------------------------
+# configuration options related to the input files
+#---------------------------------------------------------------------------
+
+# The INPUT tag can be used to specify the files and/or directories that contain 
+# documented source files. You may enter file names like "myfile.cpp" or 
+# directories like "/usr/src/myproject". Separate the files or directories 
+# with spaces.
+
+INPUT                  = ../libxnee/include/libxnee/
+
+# If the value of the INPUT tag contains directories, you can use the 
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
+# and *.h) to filter out the source-files in the directories. If left 
+# blank the following patterns are tested: 
+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp 
+# *.h++ *.idl *.odl
+
+FILE_PATTERNS          = *.h
+
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
+# should be searched for input files as well. Possible values are YES and NO. 
+# If left blank NO is used.
+
+RECURSIVE              = NO
+
+# The EXCLUDE tag can be used to specify files and/or directories that should 
+# excluded from the INPUT source files. This way you can easily exclude a 
+# subdirectory from a directory tree whose root is specified with the INPUT tag.
+
+EXCLUDE                = 
+
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories 
+# that are symbolic links (a Unix filesystem feature) are excluded from the input.
+
+EXCLUDE_SYMLINKS       = NO
+
+# If the value of the INPUT tag contains directories, you can use the 
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
+# certain files from those directories.
+
+EXCLUDE_PATTERNS       = 
+
+# The EXAMPLE_PATH tag can be used to specify one or more files or 
+# directories that contain example code fragments that are included (see 
+# the \include command).
+
+EXAMPLE_PATH           = 
+
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
+# and *.h) to filter out the source-files in the directories. If left 
+# blank all files are included.
+
+EXAMPLE_PATTERNS       = 
+
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
+# searched for input files to be used with the \include or \dontinclude 
+# commands irrespective of the value of the RECURSIVE tag. 
+# Possible values are YES and NO. If left blank NO is used.
+
+EXAMPLE_RECURSIVE      = NO
+
+# The IMAGE_PATH tag can be used to specify one or more files or 
+# directories that contain image that are included in the documentation (see 
+# the \image command).
+
+IMAGE_PATH             = 
+
+# The INPUT_FILTER tag can be used to specify a program that doxygen should 
+# invoke to filter for each input file. Doxygen will invoke the filter program 
+# by executing (via popen()) the command <filter> <input-file>, where <filter> 
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
+# input file. Doxygen will then use the output that the filter program writes 
+# to standard output.
+
+INPUT_FILTER           = 
+
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
+# INPUT_FILTER) will be used to filter the input files when producing source 
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).
+
+FILTER_SOURCE_FILES    = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to source browsing
+#---------------------------------------------------------------------------
+
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
+# be generated. Documented entities will be cross-referenced with these sources.
+
+SOURCE_BROWSER         = NO
+
+# Setting the INLINE_SOURCES tag to YES will include the body 
+# of functions and classes directly in the documentation.
+
+INLINE_SOURCES         = NO
+
+# If the REFERENCED_BY_RELATION tag is set to YES (the default) 
+# then for each documented function all documented 
+# functions referencing it will be listed.
+
+REFERENCED_BY_RELATION = YES
+
+# If the REFERENCES_RELATION tag is set to YES (the default) 
+# then for each documented function all documented entities 
+# called/used by that function will be listed.
+
+REFERENCES_RELATION    = YES
+
+#---------------------------------------------------------------------------
+# configuration options related to the alphabetical class index
+#---------------------------------------------------------------------------
+
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
+# of all compounds will be generated. Enable this if the project 
+# contains a lot of classes, structs, unions or interfaces.
+
+ALPHABETICAL_INDEX     = NO
+
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
+# in which this list will be split (can be a number in the range [1..20])
+
+COLS_IN_ALPHA_INDEX    = 5
+
+# In case all classes in a project start with a common prefix, all 
+# classes will be put under the same header in the alphabetical index. 
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
+# should be ignored while generating the index headers.
+
+IGNORE_PREFIX          = 
+
+#---------------------------------------------------------------------------
+# configuration options related to the HTML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
+# generate HTML output.
+
+GENERATE_HTML          = YES
+
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
+# put in front of it. If left blank `html' will be used as the default path.
+
+HTML_OUTPUT            = html
+
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
+# doxygen will generate files with .html extension.
+
+HTML_FILE_EXTENSION    = .html
+
+# The HTML_HEADER tag can be used to specify a personal HTML header for 
+# each generated HTML page. If it is left blank doxygen will generate a 
+# standard header.
+
+HTML_HEADER            = 
+
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
+# each generated HTML page. If it is left blank doxygen will generate a 
+# standard footer.
+
+HTML_FOOTER            = 
+
+# The HTML_STYLESHEET tag can be used to specify a user defined cascading 
+# style sheet that is used by each HTML page. It can be used to 
+# fine-tune the look of the HTML output. If the tag is left blank doxygen 
+# will generate a default style sheet
+
+HTML_STYLESHEET        = 
+
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
+# files or namespaces will be aligned in HTML using tables. If set to 
+# NO a bullet list will be used.
+
+HTML_ALIGN_MEMBERS     = YES
+
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
+# will be generated that can be used as input for tools like the 
+# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) 
+# of the generated HTML documentation.
+
+GENERATE_HTMLHELP      = NO
+
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
+# be used to specify the file name of the resulting .chm file. You 
+# can add a path in front of the file if the result should not be 
+# written to the html output dir.
+
+CHM_FILE               = 
+
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
+# be used to specify the location (absolute path including file name) of 
+# the HTML help compiler (hhc.exe). If non empty doxygen will try to run 
+# the html help compiler on the generated index.hhp.
+
+HHC_LOCATION           = 
+
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
+# controls if a separate .chi index file is generated (YES) or that 
+# it should be included in the master .chm file (NO).
+
+GENERATE_CHI           = NO
+
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
+# controls whether a binary table of contents is generated (YES) or a 
+# normal table of contents (NO) in the .chm file.
+
+BINARY_TOC             = NO
+
+# The TOC_EXPAND flag can be set to YES to add extra items for group members 
+# to the contents of the Html help documentation and to the tree view.
+
+TOC_EXPAND             = NO
+
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
+# top of each HTML page. The value NO (the default) enables the index and 
+# the value YES disables it.
+
+DISABLE_INDEX          = NO
+
+# This tag can be used to set the number of enum values (range [1..20]) 
+# that doxygen will group on one line in the generated HTML documentation.
+
+ENUM_VALUES_PER_LINE   = 4
+
+# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
+# generated containing a tree-like index structure (just like the one that 
+# is generated for HTML Help). For this to work a browser that supports 
+# JavaScript and frames is required (for instance Mozilla, Netscape 4.0+, 
+# or Internet explorer 4.0+). Note that for large projects the tree generation 
+# can take a very long time. In such cases it is better to disable this feature. 
+# Windows users are probably better off using the HTML help feature.
+
+GENERATE_TREEVIEW      = YES
+
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
+# used to set the initial width (in pixels) of the frame in which the tree 
+# is shown.
+
+TREEVIEW_WIDTH         = 250
+
+#---------------------------------------------------------------------------
+# configuration options related to the LaTeX output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
+# generate Latex output.
+
+GENERATE_LATEX         = YES
+
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
+# put in front of it. If left blank `latex' will be used as the default path.
+
+LATEX_OUTPUT           = latex
+
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be invoked. If left blank `latex' will be used as the default command name.
+
+LATEX_CMD_NAME         = latex
+
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
+# generate index for LaTeX. If left blank `makeindex' will be used as the 
+# default command name.
+
+MAKEINDEX_CMD_NAME     = makeindex
+
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
+# LaTeX documents. This may be useful for small projects and may help to 
+# save some trees in general.
+
+COMPACT_LATEX          = NO
+
+# The PAPER_TYPE tag can be used to set the paper type that is used 
+# by the printer. Possible values are: a4, a4wide, letter, legal and 
+# executive. If left blank a4wide will be used.
+
+PAPER_TYPE             = a4wide
+
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
+# packages that should be included in the LaTeX output.
+
+EXTRA_PACKAGES         = 
+
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
+# the generated latex document. The header should contain everything until 
+# the first chapter. If it is left blank doxygen will generate a 
+# standard header. Notice: only use this tag if you know what you are doing!
+
+LATEX_HEADER           = 
+
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
+# contain links (just like the HTML output) instead of page references 
+# This makes the output suitable for online browsing using a pdf viewer.
+
+PDF_HYPERLINKS         = NO
+
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
+# plain latex in the generated Makefile. Set this option to YES to get a 
+# higher quality PDF documentation.
+
+USE_PDFLATEX           = NO
+
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
+# command to the generated LaTeX files. This will instruct LaTeX to keep 
+# running if errors occur, instead of asking the user for help. 
+# This option is also used when generating formulas in HTML.
+
+LATEX_BATCHMODE        = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the RTF output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
+# The RTF output is optimised for Word 97 and may not look very pretty with 
+# other RTF readers or editors.
+
+GENERATE_RTF           = YES
+
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
+# put in front of it. If left blank `rtf' will be used as the default path.
+
+RTF_OUTPUT             = rtf
+
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
+# RTF documents. This may be useful for small projects and may help to 
+# save some trees in general.
+
+COMPACT_RTF            = NO
+
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
+# will contain hyperlink fields. The RTF file will 
+# contain links (just like the HTML output) instead of page references. 
+# This makes the output suitable for online browsing using WORD or other 
+# programs which support those fields. 
+# Note: wordpad (write) and others do not support links.
+
+RTF_HYPERLINKS         = NO
+
+# Load stylesheet definitions from file. Syntax is similar to doxygen's 
+# config file, i.e. a series of assigments. You only have to provide 
+# replacements, missing definitions are set to their default value.
+
+RTF_STYLESHEET_FILE    = 
+
+# Set optional variables used in the generation of an rtf document. 
+# Syntax is similar to doxygen's config file.
+
+RTF_EXTENSIONS_FILE    = 
+
+#---------------------------------------------------------------------------
+# configuration options related to the man page output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
+# generate man pages
+
+GENERATE_MAN           = YES
+
+# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
+# put in front of it. If left blank `man' will be used as the default path.
+
+MAN_OUTPUT             = man
+
+# The MAN_EXTENSION tag determines the extension that is added to 
+# the generated man pages (default is the subroutine's section .3)
+
+MAN_EXTENSION          = .1
+
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
+# then it will generate one additional man file for each entity 
+# documented in the real man page(s). These additional files 
+# only source the real man page, but without them the man command 
+# would be unable to find the correct page. The default is NO.
+
+MAN_LINKS              = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the XML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_XML tag is set to YES Doxygen will 
+# generate an XML file that captures the structure of 
+# the code including all documentation. Note that this 
+# feature is still experimental and incomplete at the 
+# moment.
+
+GENERATE_XML           = NO
+
+# The XML_SCHEMA tag can be used to specify an XML schema, 
+# which can be used by a validating XML parser to check the 
+# syntax of the XML files.
+
+XML_SCHEMA             = 
+
+# The XML_DTD tag can be used to specify an XML DTD, 
+# which can be used by a validating XML parser to check the 
+# syntax of the XML files.
+
+XML_DTD                = 
+
+#---------------------------------------------------------------------------
+# configuration options for the AutoGen Definitions output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
+# generate an AutoGen Definitions (see autogen.sf.net) file 
+# that captures the structure of the code including all 
+# documentation. Note that this feature is still experimental 
+# and incomplete at the moment.
+
+GENERATE_AUTOGEN_DEF   = NO
+
+#---------------------------------------------------------------------------
+# Configuration options related to the preprocessor   
+#---------------------------------------------------------------------------
+
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
+# evaluate all C-preprocessor directives found in the sources and include 
+# files.
+
+ENABLE_PREPROCESSING   = YES
+
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
+# names in the source code. If set to NO (the default) only conditional 
+# compilation will be performed. Macro expansion can be done in a controlled 
+# way by setting EXPAND_ONLY_PREDEF to YES.
+
+MACRO_EXPANSION        = NO
+
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
+# then the macro expansion is limited to the macros specified with the 
+# PREDEFINED and EXPAND_AS_PREDEFINED tags.
+
+EXPAND_ONLY_PREDEF     = NO
+
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
+# in the INCLUDE_PATH (see below) will be search if a #include is found.
+
+SEARCH_INCLUDES        = YES
+
+# The INCLUDE_PATH tag can be used to specify one or more directories that 
+# contain include files that are not input files but should be processed by 
+# the preprocessor.
+
+INCLUDE_PATH           = 
+
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
+# patterns (like *.h and *.hpp) to filter out the header-files in the 
+# directories. If left blank, the patterns specified with FILE_PATTERNS will 
+# be used.
+
+INCLUDE_FILE_PATTERNS  = 
+
+# The PREDEFINED tag can be used to specify one or more macro names that 
+# are defined before the preprocessor is started (similar to the -D option of 
+# gcc). The argument of the tag is a list of macros of the form: name 
+# or name=definition (no spaces). If the definition and the = are 
+# omitted =1 is assumed.
+
+PREDEFINED             = 
+
+# If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then 
+# this tag can be used to specify a list of macro names that should be expanded. 
+# The macro definition that is found in the sources will be used. 
+# Use the PREDEFINED tag if you want to use a different macro definition.
+
+EXPAND_AS_DEFINED      = 
+
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
+# doxygen's preprocessor will remove all function-like macros that are alone 
+# on a line, have an all uppercase name, and do not end with a semicolon. Such 
+# function macros are typically used for boiler-plate code, and will confuse the 
+# parser if not removed.
+
+SKIP_FUNCTION_MACROS   = YES
+
+#---------------------------------------------------------------------------
+# Configuration::addtions related to external references   
+#---------------------------------------------------------------------------
+
+# The TAGFILES tag can be used to specify one or more tagfiles.
+
+TAGFILES               = 
+
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create 
+# a tag file that is based on the input files it reads.
+
+GENERATE_TAGFILE       = 
+
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed 
+# in the class index. If set to NO only the inherited external classes 
+# will be listed.
+
+ALLEXTERNALS           = NO
+
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
+# in the modules index. If set to NO, only the current project's groups will 
+# be listed.
+
+EXTERNAL_GROUPS        = YES
+
+# The PERL_PATH should be the absolute path and name of the perl script 
+# interpreter (i.e. the result of `which perl').
+
+PERL_PATH              = /usr/bin/perl
+
+#---------------------------------------------------------------------------
+# Configuration options related to the dot tool   
+#---------------------------------------------------------------------------
+
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
+# generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or 
+# super classes. Setting the tag to NO turns the diagrams off. Note that this 
+# option is superceded by the HAVE_DOT option below. This is only a fallback. It is 
+# recommended to install and use dot, since it yield more powerful graphs.
+
+CLASS_DIAGRAMS         = YES
+
+# If set to YES, the inheritance and collaboration graphs will hide 
+# inheritance and usage relations if the target is undocumented 
+# or is not a class.
+
+HIDE_UNDOC_RELATIONS   = YES
+
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
+# available from the path. This tool is part of Graphviz, a graph visualization 
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section 
+# have no effect if this option is set to NO (the default)
+
+HAVE_DOT               = NO
+
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
+# will generate a graph for each documented class showing the direct and 
+# indirect inheritance relations. Setting this tag to YES will force the 
+# the CLASS_DIAGRAMS tag to NO.
+
+CLASS_GRAPH            = YES
+
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
+# will generate a graph for each documented class showing the direct and 
+# indirect implementation dependencies (inheritance, containment, and 
+# class references variables) of the class with other documented classes.
+
+COLLABORATION_GRAPH    = YES
+
+# If set to YES, the inheritance and collaboration graphs will show the 
+# relations between templates and their instances.
+
+TEMPLATE_RELATIONS     = YES
+
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
+# tags are set to YES then doxygen will generate a graph for each documented 
+# file showing the direct and indirect include dependencies of the file with 
+# other documented files.
+
+INCLUDE_GRAPH          = YES
+
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
+# documented header file showing the documented files that directly or 
+# indirectly include this file.
+
+INCLUDED_BY_GRAPH      = YES
+
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
+# will graphical hierarchy of all classes instead of a textual one.
+
+GRAPHICAL_HIERARCHY    = YES
+
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
+# generated by dot. Possible values are png, jpg, or gif
+# If left blank png will be used.
+
+DOT_IMAGE_FORMAT       = png
+
+# The tag DOT_PATH can be used to specify the path where the dot tool can be 
+# found. If left blank, it is assumed the dot tool can be found on the path.
+
+DOT_PATH               = 
+
+# The DOTFILE_DIRS tag can be used to specify one or more directories that 
+# contain dot files that are included in the documentation (see the 
+# \dotfile command).
+
+DOTFILE_DIRS           = 
+
+# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width 
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than 
+# this value, doxygen will try to truncate the graph, so that it fits within 
+# the specified constraint. Beware that most browsers cannot cope with very 
+# large images.
+
+MAX_DOT_GRAPH_WIDTH    = 1024
+
+# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height 
+# (in pixels) of the graphs generated by dot. If a graph becomes larger than 
+# this value, doxygen will try to truncate the graph, so that it fits within 
+# the specified constraint. Beware that most browsers cannot cope with very 
+# large images.
+
+MAX_DOT_GRAPH_HEIGHT   = 1024
+
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
+# generate a legend page explaining the meaning of the various boxes and 
+# arrows in the dot generated graphs.
+
+GENERATE_LEGEND        = YES
+
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
+# remove the intermedate dot files that are used to generate 
+# the various graphs.
+
+DOT_CLEANUP            = YES
+
+#---------------------------------------------------------------------------
+# Configuration::addtions related to the search engine   
+#---------------------------------------------------------------------------
+
+# The SEARCHENGINE tag specifies whether or not a search engine should be 
+# used. If set to NO the values of all tags below this one will be ignored.
+
+SEARCHENGINE           = NO
+
+# The CGI_NAME tag should be the name of the CGI script that 
+# starts the search engine (doxysearch) with the correct parameters. 
+# A script with this name will be generated by doxygen.
+
+CGI_NAME               = search.cgi
+
+# The CGI_URL tag should be the absolute URL to the directory where the 
+# cgi binaries are located. See the documentation of your http daemon for 
+# details.
+
+CGI_URL                = 
+
+# The DOC_URL tag should be the absolute URL to the directory where the 
+# documentation is located. If left blank the absolute path to the 
+# documentation, with file:// prepended to it, will be used.
+
+DOC_URL                = 
+
+# The DOC_ABSPATH tag should be the absolute path to the directory where the 
+# documentation is located. If left blank the directory on the local machine 
+# will be used.
+
+DOC_ABSPATH            = 
+
+# The BIN_ABSPATH tag must point to the directory where the doxysearch binary 
+# is installed.
+
+BIN_ABSPATH            = /usr/local/bin/
+
+# The EXT_DOC_PATHS tag can be used to specify one or more paths to 
+# documentation generated for other projects. This allows doxysearch to search 
+# the documentation for these projects as well.
+
+EXT_DOC_PATHS          = 

--- /dev/null
+++ b/original/xnee.html
@@ -0,0 +1,5075 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
+<html>
+<!-- Created on December 24, 2009 by texi2html 1.82
+texi2html was written by: 
+            Lionel Cons <[e-mail]> (original author)
+            Karl Berry  <[e-mail]>
+            Olaf Bachmann <[e-mail]>
+            and many others.
+Maintained by: Many creative people.
+Send bugs and suggestions to <[e-mail]>
+-->
+<head>
+<title>Xnee Manual</title>
+
+<meta name="description" content="Xnee Manual">
+<meta name="keywords" content="Xnee Manual">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2html 1.82">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+pre.display {font-family: serif}
+pre.format {font-family: serif}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: serif; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: serif; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.roman {font-family:serif; font-weight:normal;}
+span.sansserif {font-family:sans-serif; font-weight:normal;}
+ul.toc {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
+
+<a name="Top"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h1 class="settitle">Xnee Manual</h1>
+
+
+<table class="menu" border="0" cellspacing="0">
+<tr><td align="left" valign="top"><a href="#Summary">1. Summary</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#Getting-started">2. Getting started</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#Functional-overview">3. Functional overview</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#Installation">4. Installation</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#Examples">5. Examples</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             examples
+</td></tr>
+<tr><td align="left" valign="top"><a href="#File-format">7. File types and format</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">          File format
+</td></tr>
+<tr><td align="left" valign="top"><a href="#Programs">6. Xnee Programs</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">             Programs
+</td></tr>
+<tr><td align="left" valign="top"><a href="#Internals">8. Xnee Internals</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">            Internals
+</td></tr>
+<tr><td align="left" valign="top"><a href="#Requirements">9. Xnee Requirements</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">         Requirements
+</td></tr>
+<tr><td align="left" valign="top"><a href="#FAQ">10. FAQ</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#Copying-This-Manual">A. Copying This Manual</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
+<tr><td align="left" valign="top"><a href="#Index">B. Index</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top"></td></tr>
+</table>
+
+
+
+<hr size="1">
+<a name="Summary"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Summary-1" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[ &lt;&lt; ]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Summary-2"></a>
+<h1 class="chapter">1. Summary</h1>
+
+<hr size="6">
+<a name="Summary-1"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Summary" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-features" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Summary" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Summary" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">1.1 Summary</h2>
+<p>  Xnee is a suite of programs that can record, replay and
+  distribute user actions under the X11 environment. 
+  Think of it as a robot that can imitate the job you just 
+  did. 
+</p>
+<p>Xnee consists of one library and two applications
+</p>
+<p>  <b>cnee</b> - command line program
+</p>
+<p>  <b>gnee</b> - graphical user interface program
+</p>
+<p>  <b>pnee</b> - a Gnome Panel Applet
+</p>
+<p>  <b>libxnee</b> - library used by xnee and gnee
+</p>
+            
+            
+<hr size="6">
+<a name="Xnee-features"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Summary-1" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Background" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Summary" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Summary" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">1.2 Xnee features</h2>
+<a name="index-features"></a>
+
+<p>Xnee can be used for multiple purposes, allthough it was initially designed as a test tool. The most used features are the foloowing:
+</p>
+<p><b>Test tool</b> - 
+        Instead of performing test cases for a GUI (or CLI program) 
+        over and over again, the test cases can be automated. Simply record 
+        a user session and replay it later. 
+</p>
+<p><b>Performance test tool</b> - 
+	If you want to simulate lots of simultaneous users in a network (or
+	a local machine) you can use Xnee. Simply record a user
+	session and start multiple instances of Xnee.
+</p>
+<p><b>Demonstration tool</b> - 
+	You can use Xnee to demonstrate the features of your program. Simply 
+	record a user session and replay it later. 
+</p>
+<p><b>Distribution tool</b> - 
+	If you want to send over your mouse/keyboard actions to another display
+	you can use the built-in distribution mechanism in Xnee. 
+</p>
+<p><b>Macro recorder/replayer</b> - 
+	By binding a key and modifier combination (e.g using xrebind)
+  to replay a recorded session you will have a Window Manager and 
+  application independent macro.
+</p>
+<p><b>File retyper</b> - 
+   Xnee can retype the contents of a file. This can be useful
+   during tests or if you want xnee to answer some command
+   session without having to record the session.
+</p>
+<p><b>X11 protocol sniffer</b> - 
+   Xnee can be used a sniffer for the X11 protocol.
+</p>
+
+<hr size="6">
+<a name="Background"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Xnee-features" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Summary" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Summary" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">1.3 Background</h2>
+<a name="index-background"></a>
+<p>In order to verify that a program does the job it&rsquo;s supposed to do, 
+certain tests have to be made. 
+These tests are, IMHO, perhaps the most boring things a programmer 
+can do. Xnee is designed to reduce the programmer from this burden.
+<br>
+</p>
+<p>Xnee started out as a commad line program. During the development
+phase the main functionality was broken out to a library, called
+libxnee. The command line program was renamed cnee. The thought behind
+making the library was to enable the writing of other clients than
+just the command line. Today there is a GUI program, gnee, and a Gnome
+panel applet, pnee, that uses the library.  
+<br>
+</p>
+<p>By using xnee your testcase(s) can be recorded and later on replayed.
+Xnee comes with other features For more information about these, read the 
+Introduction.
+</p>
+<p>This manual mainly focuses on the command line program, cnee. There
+are however a seperate chapters for the other programs.
+</p>
+
+
+
+
+<hr size="6">
+<a name="Getting-started"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Background" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started-1" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Summary" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Getting-started-2"></a>
+<h1 class="chapter">2. Getting started</h1>
+
+<hr size="6">
+<a name="Getting-started-1"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Getting-started" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Simple-replay" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">2.1 Getting started</h2>
+<a name="index-Getting-started"></a>
+<p>To get the first feel of Xnee some simple examples are presented. 
+</p>
+<hr size="6">
+<a name="Simple-replay"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Getting-started-1" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Simple-recording-of-Key-presses" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started-1" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">2.1.1 Simple replay</h3>
+<p>Start a terminal emulator (e.g xterm) and then start Xnee, 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay --file example1.xnr &amp;</code>
+</pre></td></tr></table>
+<p>....dont forget &rsquo;&amp;&rsquo;.
+The file example1.xnr contains keyboard events recorded during 
+development of this manual. When replayed you&rsquo;ll see what was typed and of 
+course more important you&rsquo;ll get i first glimpse of Xnee and its capabilities. 
+For information on where to find the example files, see below.
+</p>
+<hr size="6">
+<a name="Simple-recording-of-Key-presses"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Simple-replay" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Simple-replaying-of-your-recorded-file-1" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started-1" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">2.1.2 Simple recording of Key presses</h3>
+<p>We move on to a (very) simple recording session.
+Start a terminal emulator (e.g xterm) and your favorite editor.
+Move the pointer to one of the terminal windows and start Xnee.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record -o example2.xnr --device-event-range 2-3 \</code>
+   <code>--time 5 --events-to-record 20</code>
+</pre></td></tr></table>
+<p>Move the pointer to the editor and get focus (e.g click the 
+window frame). After 5 seconds you can type whatever you want to record 
+(20 press- and relase events of the keyboard are recorded). We are done
+and you have recorded your first session! Leave the desktop as it 
+is and go forward to the next example.
+</p>
+
+
+<hr size="6">
+<a name="Simple-replaying-of-your-recorded-file-1"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Simple-recording-of-Key-presses" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Simple-recording-of-mouse-motions" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started-1" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">2.1.3 Simple replaying of your recorded file</h3>
+<p>Start one terminal emulator (e.g xterm).
+Let Xnee repeat the stuff you did in the example above. 
+Undo all changes in the editor that was made in the previous example.
+Move the pointer to one of the terminal windows and start Xnee.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay -f example2.xnr --time 5</code>
+</pre></td></tr></table>
+<p>Move the pointer to the editor and get focus (e.g click the 
+window frame). After 5 seconds you will see your typings in the example 
+above being repeated.
+</p>
+<hr size="6">
+<a name="Simple-recording-of-mouse-motions"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Simple-replaying-of-your-recorded-file-1" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Simple-replaying-of-your-recorded-file" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started-1" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">2.1.4 Simple recording of mouse motions</h3>
+<p>We move on to another simple recording session.
+Start a terminal emulator (e.g xterm).
+Move the pointer to the terminal window and start Xnee.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record -o example3.xnr --device-event-range 5-6 \</code>
+   <code>--time 5 --events-to-record 20</code>
+</pre></td></tr></table>
+<p>After 5 seconds you can move the pointer around (20 motion events are recorded).
+</p>
+<hr size="6">
+<a name="Simple-replaying-of-your-recorded-file"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Simple-recording-of-mouse-motions" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Simple-retyping-of-a-text-file" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started-1" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">2.1.5 Simple replaying of your recorded file</h3>
+<p>Let Xnee repeat the stuff you did in the example above.. 
+Move the pointer to the terminal window and start Xnee.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay -f example3.xnr --time 5</code>
+</pre></td></tr></table>
+<p>After 5 seconds you will see your mouse motions in the example above being 
+repplayed.
+</p>
+<hr size="6">
+<a name="Simple-retyping-of-a-text-file"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Simple-replaying-of-your-recorded-file" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Example-Xnee-Session-files" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started-1" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">2.1.6 Simple retyping of a text file</h3>
+<p>Let Xnee retype (type again) the text in a text file.
+Move the pointer to the terminal window and create a text file containing
+the command <code>ls -l</code>. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>echo &quot;ls -l&quot; &gt; ./mytext.txt</code>
+</pre></td></tr></table>
+<p>And after that you start Xnee.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --retype-file  ./mytext.txt --time 5</code>
+</pre></td></tr></table>
+<p>After 5 seconds you will see Xnee type <code>ls -l</code>, which probably will 
+list the files in the current directory.
+</p>
+<hr size="6">
+<a name="Example-Xnee-Session-files"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Simple-retyping-of-a-text-file" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Getting-started-1" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">2.1.7 Example Xnee Session files</h3>
+<a name="index-Example-Xnee-Session-files"></a>
+<p>The example file above (example1.xnr) is a session file that has been 
+delivered with the sources (allthough not installed), rpm and with the 
+Xnee Documentation Package. The file(s) can be found:
+</p><table>
+<tr><td width="30%"></td><td width="30%"><b>Distribution</b></td><td width="30%"><b>Location</b></td></tr>
+<tr><td width="30%"></td><td width="30%">RPM</td><td width="30%">/usr/lib/xnee/session</td></tr>
+<tr><td width="30%"></td><td width="30%">Source</td><td width="30%">./sessions/</td></tr>
+<tr><td width="30%"></td><td width="30%">Document Package</td><td width="30%">./sessions/</td></tr>
+</table>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<hr size="6">
+<a name="Functional-overview"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Example-Xnee-Session-files" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview-1" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Getting-started" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Functional-overview-2"></a>
+<h1 class="chapter">3. Functional overview</h1>
+
+<hr size="6">
+<a name="Functional-overview-1"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Functional-overview" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Modes" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.1 Functional overview</h2>
+<a name="index-Functional-overview"></a>
+<p>The Xnee applications (gnee and xnee) receives X11 protocol data (e.g. events)
+from an X server (using libxnee) and print them to a file, called Xnee 
+Session File. Theses events are later read from the session file and replayed.
+Gnee and xnee can read its settings from a file, called Xnee Project File, 
+or from command line (cnee) or via the GUI (gnee).
+</p>
+
+<br>
+<p>Events directly generated by the user (e.g KeyPress) can be replayed 
+or faked. Requests, replies, errors and events not directly generated by the 
+user (e.g MapNotify) can be recorded as well. By using these data  
+Xnee can replay with synchronisation. 
+</p>
+<p>This picture gives an overview of Xnee and the files used.
+<br>
+<img src="xngener.png" alt="xngener">
+In this section you will be given information about key concepts in X11 and Xnee. It is
+vital that you read through this chapter. 
+</p>
+<hr size="6">
+<a name="Modes"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Functional-overview-1" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Record" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.2 Modes</h2>
+<a name="index-modes"></a>
+<p>Xnee has four modes:
+</p><ul>
+<li>	record 
+</li><li>	replay
+</li><li>	retype
+</li><li>	distribute
+</li></ul>
+
+<p>The distribution mechanism can be used together with the other three.
+</p>
+<hr size="6">
+<a name="Record"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Modes" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Modes" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.2.1 Record</h3>
+<a name="index-recording"></a>
+<p>When record mode is used Xnee receives a copy of the data sent to and from the 
+X server. The copy is printed to a file. Xnee can record the whole X11 
+protocol, not just mouse and keyboard events.
+</p>
+<p>This picture gives an overview of Xnee and the files used when recording.
+<br>
+<img src="xnrec.png" alt="xnrec">
+</p>
+
+<hr size="6">
+<a name="Replay"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Record" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Retype" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Modes" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.2.2 Replay</h3>
+<a name="index-replaying"></a>
+<p>When replay mode is used Xnee reads data from a file or stdin. These data is 
+either sent to the server (if it is a keyboard or a mouse event) or used to 
+synchronise with (if any of the other data). 
+</p>
+<p>This picture gives an overview of Xnee and the files used when replaying.
+<br>
+<img src="xnrep.png" alt="xnrep">
+</p>
+
+<hr size="6">
+<a name="Retype"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Distribution" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Modes" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.2.3 Retype</h3>
+<a name="index-retype"></a>
+<p>Xnee can retype the contents of a text file. This is useful when combining 
+replaying of different recorded session. You can change the text written in
+for example an editor (e.g emacs) without having to re-record the complete
+sessions. 
+</p>
+<hr size="6">
+<a name="Distribution"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Retype" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Ranges" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Modes" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.2.4 Distribution</h3>
+<a name="index-distributing"></a>
+<p>Xnee can fake mouse and keyboard events on multiple displays. This 
+distribution mechanism can be used when recording, replaying or retyping.
+</p>
+
+<hr size="6">
+<a name="Ranges"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Distribution" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#First-and-last-motion-event" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.3 Ranges</h2>
+<a name="index-ranges"></a>
+<p>What data to record is specified using ranges. Ranges has a start value and 
+a stop value. The following data can be recorded: 
+</p>
+<table>
+<tr><td width="10%"></td><td width="45%"><b>Xnee name</b></td><td width="45%"><b>X Protocol Name</b></td></tr>
+<tr><td width="10%"></td><td width="45%">core-requests</td><td width="45%">Request</td></tr>
+<tr><td width="10%"></td><td width="45%">device-event</td><td width="45%">Event</td></tr>
+<tr><td width="10%"></td><td width="45%">delivered-event</td><td width="45%">Event</td></tr>
+<tr><td width="10%"></td><td width="45%">error</td><td width="45%">Error</td></tr>
+<tr><td width="10%"></td><td width="45%">reply</td><td width="45%">Reply</td></tr>
+<tr><td width="10%"></td><td width="45%">ext-requests.ext-major</td><td width="45%">Extension Request</td></tr>
+<tr><td width="10%"></td><td width="45%">ext-requests.ext-minor</td><td width="45%">Extension Request</td></tr>
+<tr><td width="10%"></td><td width="45%">ext-replies.ext-major</td><td width="45%">Extension Reply</td></tr>
+<tr><td width="10%"></td><td width="45%">ext-replies.ext-minor</td><td width="45%">Extension Reply</td></tr>
+</table>
+
+<p>When specifying the ranges when using xnee you can either type the integer value 
+of the data or the name of the data. To find out what number belongs to what 
+data name, you can use the <code>--print-data-name</code> option. For an explanation 
+of the X protocol data, please read the &quot;X Record Extension Library&quot; or the 
+&quot;Record Extension Protocol Specification&quot;.
+</p>
+
+<hr size="6">
+<a name="First-and-last-motion-event"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Ranges" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Delay" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.4 First and last motion event</h2>
+<p>Xnee has the ability to skip recording of succesive motion events with no 
+other data in between. This option is intended to reduce the number of data 
+recorded by leaving out unnecessary data. This feature can be invoked with 
+the <code>--first-last</code> flag.
+</p>
+<hr size="6">
+<a name="Delay"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#First-and-last-motion-event" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Verbose" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.5 Delay</h2>
+<p>Sometimes when Xnee starts recording data, the keyrelease (caused by pressing and 
+releasing RETURN to execute the Xnee command line) is recorded. This single 
+keyrelease (with no corresponding keypress) might confuse the X server. 
+With the <code>--time &lt;secs&gt;</code> option Xnee can be paused for a number of seconds 
+before recording/replaying/retyping starts.
+</p>
+
+<hr size="6">
+<a name="Verbose"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Delay" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Human-printouts" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.6 Verbose</h2>
+<p>When enabling verbose mode (<code>--verbose</code>) Xnee prints a lot of information 
+about it&rsquo;s state. This option is only intended for runtime debugging.
+</p>
+<hr size="6">
+<a name="Human-printouts"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Verbose" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Invoking-Xnee" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.7 Human printouts</h2>
+<p>Sometimes it&rsquo;s hard to decide what data to use when synchronising. To do this 
+you have to analyse what data is sent from the server when recording. Instead of 
+reading the data number, s tring representation of the data is printed out. 
+To enable this option, use the <code>--human-printouts</code>.
+</p>
+
+
+<hr size="6">
+<a name="Invoking-Xnee"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Human-printouts" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Command-line-syntax" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.8 Invoking Xnee</h2>
+
+<hr size="6">
+<a name="Command-line-syntax"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Invoking-Xnee" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Project-file-1" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Invoking-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.8.1 Command line syntax</h3>
+<a name="index-command-line-syntax"></a>
+<p>To get information about how to use Xnee&rsquo;s command line options please use the man page(s).
+</p>
+<hr size="6">
+<a name="Project-file-1"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Command-line-syntax" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Session-file" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Invoking-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.8.2 Project file</h3>
+<p>To use a Project file use the <code>--project</code> option,  e.g <code>cnee --project xnee/projects/netscape.xns</code>
+</p>
+<hr size="6">
+<a name="Session-file"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Project-file-1" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Invoking-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.8.3 Session file</h3>
+<p>To use a session file use the <code>--file</code> option,  e.g 
+<code>cnee --file user1_session.xns</code>
+</p>
+
+<hr size="6">
+<a name="Interupting-Xnee"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Session-file" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#modifier-and-key" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.9 Interupting Xnee</h2>
+<a name="index-Interupting-xnee"></a>
+<p>Interupting Xnee when recording or replaying can be done as follows
+</p><ul>
+<li>	user specified modifier and key
+</li><li>	limit the number of data to record
+</li><li>	sending a SIGTERM signal (e.g pressing Control-c in a terminal window)
+</li></ul>
+
+<p>The prefered way to interrupt xnee is to use the modifier+key. 
+</p>
+<hr size="6">
+<a name="modifier-and-key"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#limit-the-number-of-data-to-record" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.1 modifier and key</h3>
+<a name="index-modifier"></a>
+<a name="index-key"></a>
+<p>It is possible to specify a modifier (e.g Control button) and a key (e.g &rsquo;a&rsquo;) 
+that will stop the Xnee session. When using this option make sure that the
+modifier/key is not used in any way by the applications you are recording. 
+You can specify a key+modifier to stop, pause and resume xnee. You can also 
+insert a mark in the recorded session file. 
+</p>
+<hr size="6">
+<a name="limit-the-number-of-data-to-record"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#modifier-and-key" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#sending-a-SIGTERM-signal" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.2 limit the number of data to record</h3>
+<p>By specifying the number of data to record (<code>--loops</code>) xnee stops when this number 
+of data is received from the server. When replaying the same amount of data 
+is replayed. 
+</p>
+<hr size="6">
+<a name="sending-a-SIGTERM-signal"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#limit-the-number-of-data-to-record" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Stop-Xnee-with-key-combination" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.3 sending a SIGTERM signal</h3>
+<a name="index-SIGTERM"></a>
+<p>The easiest way to send a signal to a process is by launching Xnee
+from a terminal window (e.g xterm) and then press Control-c which will
+send the SIGTERM signal to Xnee. When replaying it can sometimes be
+hard to move the pointer into the terminal window (e.g if a lot of
+motion events were recorded that will let you compete with Xnee on
+where the mouse pointer shall be located.  Beleive me, you&rsquo;ll end up
+lossing that battle).
+</p>
+<p>When using Control-c to stop Xnee you must be aware of that the pressing of the Control key gets recorded. When replaying a recorded session ending with pressing of Control your apps may think you are pressing the Control key. A simple solution for this is to press and release the Control.
+</p>
+<hr size="6">
+<a name="Stop-Xnee-with-key-combination"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#sending-a-SIGTERM-signal" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Pause-Xnee-with-key-combination" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.4 Stop Xnee with key combination</h3>
+<a name="index-Stop-Xnee-with-key-combination"></a>
+<p>Xnee stops its current action when the user presses the key
+combination as specified during setup. Xnee will be shut gracefully.
+</p>
+<hr size="6">
+<a name="Pause-Xnee-with-key-combination"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Stop-Xnee-with-key-combination" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Pause-Xnee-with-key-combination-1" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.5 Pause Xnee with key combination</h3>
+<a name="index-Pause-Xnee-with-key-combination"></a>
+<p>Xnee pause its current action when the user presses the key
+combination as specified during setup. Xnee will be in paused mode until
+the user stops or resumes Xnee.
+</p>
+<hr size="6">
+<a name="Pause-Xnee-with-key-combination-1"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Pause-Xnee-with-key-combination" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Insert-marks-Xnee-with-key-combination" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.6 Pause Xnee with key combination</h3>
+<a name="index-Pause-Xnee-with-key-combination-1"></a>
+<p>Xnee resumes its current paused action when the user presses the key
+combination as specified during setup. Xnee will continue where it was
+paused.
+</p>
+<hr size="6">
+<a name="Insert-marks-Xnee-with-key-combination"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Pause-Xnee-with-key-combination-1" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Limit-number-of-data-to-record" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.7 Insert marks Xnee with key combination</h3>
+<a name="index-Insert-marks-Xnee-with-key-combination"></a>
+<p>When the user presses the key combination as specified during setup 
+Xnee will print a mark in the session file containing a time stamp. This 
+feature is intended be used when you want to mark an interresting time/event 
+during recording. After recording has finished you can add Xnee scripting 
+calls to Xnee which will be interpreted and executed as if they were recorded.
+</p>
+
+<hr size="6">
+<a name="Limit-number-of-data-to-record"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Insert-marks-Xnee-with-key-combination" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Limit-the-events-to-record" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.8 Limit number of data to record</h3>
+<p>There a a few ways to limit the number of data Xnee records.
+</p><ul>
+<li>	limit the events to recored
+</li><li>	limit the data to recored
+</li><li>	limit the time to recored
+</li><li>	send a signal to xnee (SIGTERM)
+</li><li>	use a selfmade record callback function
+</li></ul>
+
+
+<hr size="6">
+<a name="Limit-the-events-to-record"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Limit-number-of-data-to-record" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Limit-the-data-to-record" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.9 Limit the events to record</h3>
+<a name="index-limit-the-events"></a>
+<p>When having received the specified amount of events from the server, Xnee 
+stops the recording. For more information on how to use this option, read
+the man page for cnee or the user manual for gnee.
+</p>
+<hr size="6">
+<a name="Limit-the-data-to-record"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Limit-the-events-to-record" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Limit-the-time-to-record" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.10 Limit the data to record</h3>
+<a name="index-limit-the-data"></a>
+<p>When having received the specified amount of data from the server, Xnee 
+stops the recording. For more information on how to use this option, read
+the man page for cnee or the user manual for gnee.
+</p>
+<hr size="6">
+<a name="Limit-the-time-to-record"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Limit-the-data-to-record" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Send-SIGTERM-to-Xnee" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.11 Limit the time to record</h3>
+<a name="index-limit-the-events-1"></a>
+<p>When having recorded for the specified amount of time from the server, Xnee 
+stops the recording. For more information on how to use this option, read
+the man page for cnee or the user manual for gnee.
+</p>
+<hr size="6">
+<a name="Send-SIGTERM-to-Xnee"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Limit-the-time-to-record" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-plugins" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Interupting-Xnee" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">3.9.12 Send SIGTERM to Xnee</h3>
+<a name="index-SIGTERM-1"></a>
+<p>The easiest way to send a signal to a process is by launching Xnee from a 
+terminal window (e.g xterm). By pressing Control-c xterm sends the 
+SIGTERM signal to Xnee. When replaying it can sometimes be hard to 
+move the pointer into the terminal window (e.g if a lot of motion 
+events were recorded that will let you compete with Xnee on where 
+the mouse pointer shall be located. Beleive me, you&rsquo;ll end up lossing 
+that battle).  
+</p>
+
+<hr size="6">
+<a name="Xnee-plugins"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Send-SIGTERM-to-Xnee" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">3.10 Xnee plugins</h2>
+<a name="index-plugins"></a>
+<p>Xnee supports plugins since version 1.07. For information about how to write 
+plugins, download the source code and look at the plugin example which is 
+delivered with Xnee.
+</p>
+
+
+
+<hr size="6">
+<a name="Installation"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Xnee-plugins" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation-from-source-with-the-configure-script" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Functional-overview" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Installation-1"></a>
+<h1 class="chapter">4. Installation</h1>
+
+<hr size="6">
+<a name="Installation-from-source-with-the-configure-script"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Installation" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation-from-source-with-default-Makefile" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Installation" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">4.1 Installation from source with the configure script</h2>
+<p>To build and install Xnee do the following:
+Download the following source files into a directory (version numbers given here are just examples)
+</p><ul>
+<li>	xnee-3.02.tar.gz
+</li></ul>
+
+
+<br>
+<p>Unzip the source file
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>gunzip xnee-3.02.tar.gz</code>
+</pre></td></tr></table>
+
+<br>
+<p>Untar the source file
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>tar xvf xnee-3.02.tar</code>
+</pre></td></tr></table>
+
+<br>
+<p>Enter the Xnee directory
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cd xnee-3.02</code>
+</pre></td></tr></table>
+
+<br>
+<p>Generate the makefiles
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>./configure</code>
+</pre></td></tr></table>
+<br>
+<p>or if you want to specify which directory to install xnee to 
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>./configure --prefix=&lt;PATH TO INSTALLATION DIR&gt;</code>
+</pre></td></tr></table>
+
+<br>
+<p>Build Xnee
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>make clean all</code>
+</pre></td></tr></table>
+
+<br>
+<p>Install (as root) if you want libxnee to be installed. If not, skip the following command. Installation of libxnee is not needed to build cnee and gnee.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>make install</code>
+</pre></td></tr></table>
+
+
+<hr size="6">
+<a name="Installation-from-source-with-default-Makefile"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Installation-from-source-with-the-configure-script" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation-from-CVS" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Installation" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">4.2 Installation from source with default Makefile</h2>
+<p>To unpack, build and install Xnee from the sourcefiles do the following:
+<br>
+Download the source files into a directory
+</p>
+<p>Unzip the source file
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>gunzip xnee-3.02.tar.gz</code>
+</pre></td></tr></table>
+
+<p>Untar the source file
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>tar xvf xnee-3.02.tar</code>
+</pre></td></tr></table>
+
+<p>Enter the Xnee directory
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cd xnee-3.02</code>
+</pre></td></tr></table>
+
+<p>Build Xnee
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>make -f Makefile.xnee clean all</code>
+</pre></td></tr></table>
+
+<p>Copy the Xnee binary (xnee/src/xnee) to a directory
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cp xnee/src/xnee /usr/local/bin</code>
+</pre></td></tr></table>
+
+
+
+
+
+<hr size="6">
+<a name="Installation-from-CVS"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Installation-from-source-with-default-Makefile" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Installation" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">4.3 Installation from CVS</h2>
+<br>
+<p>Download the xnee source code from the CVS repository at 
+<a href="http://savannah.gnu.org">http://savannah.gnu.org</a>. Instructions on how to do 
+this can be found there as well. 
+</p>
+<br>
+
+<p>Build Xnee
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cd xnee</code>
+<code>make -f Makefile.cvs</code>
+<code>./configure --enable-doc</code>
+<code>make</code>
+<code>make install</code> (optional)
+</pre></td></tr></table>
+
+
+<p>Build Xnee Documentation
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cd doc</code>
+<code>make manual</code>
+<code>make install</code> (as root)
+<code>cd ..</code>
+</pre></td></tr></table>
+
+
+
+
+<hr size="6">
+<a name="Examples"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Installation-from-CVS" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Recorder" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Installation" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Examples-1"></a>
+<h1 class="chapter">5. Examples</h1>
+
+<hr size="6">
+<a name="Recorder"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Examples" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Record-mouse-motions" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">5.1 Recorder</h2>
+
+
+<hr size="6">
+<a name="Record-mouse-motions"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Recorder" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Record-keyboard" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Recorder" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.1.1 Record mouse motions</h3>
+<a name="index-Record-mouse-motions"></a>
+<p>Record mouse motions only and save the session to mouse-rec.xnl. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record --mouse --out-file mouse-rec.xnl</code>
+</pre></td></tr></table>
+<p>After having typed this you can move your mouse round for a while. After Xnee 
+has exited you will be able to replay your motions. Xnee will stop
+after having record 100 events (this is the default behaviour).
+</p>
+
+<hr size="6">
+<a name="Record-keyboard"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Record-mouse-motions" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Record-keyboard-and-mouse" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Recorder" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.1.2 Record keyboard</h3>
+<a name="index-Record-keyboard"></a>
+<p>Record keyboard events only and save log to kbd-rec.xnl. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record --keyboard --out-file kbd-rec.xnl</code>
+</pre></td></tr></table>
+<p>After having typed this Xnee records all your keyboard actions. After Xnee 
+has exited you will be able to replay your keyboard actions. Xnee will stop
+after having record 100 events (this is the default behaviour).
+</p>
+
+<hr size="6">
+<a name="Record-keyboard-and-mouse"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Record-keyboard" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Record-a-gnumeric-session" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Recorder" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.1.3 Record keyboard and mouse</h3>
+<a name="index-Record-keyboard-and-mouse"></a>
+<p>Record keyboard and mouse and save log to km-rec.xnl. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record --keyboard --mouse --out-file kbd-rec.xnl</code>
+</pre></td></tr></table>
+<p>After having typed this Xnee records all your keyboard and mouse actions. 
+So now move your pointer and write some stuff with your keyboard. After Xnee 
+has exited you will be able to replay your keyboard and mouse actions. Xnee 
+will stop after having record 100 events (this is the default behaviour).
+</p>
+
+
+<hr size="6">
+<a name="Record-a-gnumeric-session"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Record-keyboard-and-mouse" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Record-a-gnumeric-session-with-synchronisation-data" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Recorder" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.1.4 Record a gnumeric session</h3>
+<a name="index-Record-a-gnumeric-session"></a>
+<p>Record a gnumeric session. Record 400 events. Save output in file gnumeric.xnl
+Start a terminal emulator (e.g xterm)
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>xterm&amp;</code>
+</pre></td></tr></table>
+
+<p>Start Xnee
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record --keyboard --mouse --events-to-record 400 \</code>
+   <code> --out-file gnumeric.xnl&amp;</code>
+</pre></td></tr></table>
+
+<p>Start gnumeric
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>gnumeric&amp;</code>
+</pre></td></tr></table>
+<p>Start using gnumeric. Browse the menus above, reset the fonts etc.
+</p>
+
+
+
+<hr size="6">
+<a name="Record-a-gnumeric-session-with-synchronisation-data"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Record-a-gnumeric-session" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Recorder" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.1.5 Record a gnumeric session with synchronisation data</h3>
+<a name="index-Record-a-gnumeric-session-with-synchronisation-data"></a>
+<p>Record a gnumeric session. Record 400 events. Save output in file gnumeric2.xnl
+</p>
+<br>
+<p>Start a terminal emulator (e.g xterm)
+<code>xterm&amp;</code>
+</p>
+<p>Start Xnee
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record --keyboard --mouse --events-to-record 400 \</code>
+   <code> --out-file gnumeric2.xnl\</code>
+   <code>--delivered-event-range Expose,MapRequest,LeaveNotify,EnterNotify  &amp;</code>
+</pre></td></tr></table>
+
+<br>
+<p>Start gnumeric
+<code>gnumeric&amp;</code>
+Start using gnumeric. Browse the menus above, reset the fonts etc.
+</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<hr size="6">
+<a name="Replayer"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Record-a-gnumeric-session-with-synchronisation-data" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-mouse-motions" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">5.2 Replayer</h2>
+
+<hr size="6">
+<a name="Replay-mouse-motions"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replayer" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-mouse-motions-using-with-half-speed" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.2.1 Replay mouse motions</h3>
+<a name="index-replay-mouse-motions"></a>
+<p>Replay mouse motions as found in the file mouse-rec.xnl. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay  --file mouse-rec.xnl</code>
+</pre></td></tr></table>
+<p>Xnee will now imitate exactly what you did when you recorded this file.
+</p>
+<hr size="6">
+<a name="Replay-mouse-motions-using-with-half-speed"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-mouse-motions" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-mouse-motions-using-with-double-speed" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.2.2 Replay mouse motions using with half speed</h3>
+<a name="index-replay-using-half-speed"></a>
+<p>Replay mouse motions as found in the file mouse-rec.xnl but with the 
+speed set to 50% of the recorded.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay  --file mouse-rec.xnl --speed-percent 50</code>
+</pre></td></tr></table>
+<p>Xnee will now imitate exactly what you did when you recorded this file, 
+allthough it will be done in 50% of the recorded time.
+</p>
+<hr size="6">
+<a name="Replay-mouse-motions-using-with-double-speed"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-mouse-motions-using-with-half-speed" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-keyboard-actions" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.2.3 Replay mouse motions using with double speed</h3>
+<a name="index-replay-using-double-speed"></a>
+<p>Replay mouse motions as found in the file mouse-rec.xnl but with the 
+speed set to 200% of the recorded.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay  --file mouse-rec.xnl --speed-percent 200</code>
+</pre></td></tr></table>
+<p>Xnee will now imitate exactly what you did when you recorded this file, 
+allthough it will be done twice as fast as when recorded.
+</p>
+<hr size="6">
+<a name="Replay-keyboard-actions"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-mouse-motions-using-with-double-speed" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-keyboard-and-mouse" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.2.4 Replay keyboard actions</h3>
+<a name="index-Replay-keyboard-actions"></a>
+<p>Replay keyboard events from file kbd-rec.xnl. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay --file kbd-rec.xnl</code>
+</pre></td></tr></table>
+<p>After having typed this Xnee replays all your keyboard actions. After Xnee 
+has exited you will be able to replay your keyboard actions. 
+</p>
+
+
+<hr size="6">
+<a name="Replay-keyboard-and-mouse"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-keyboard-actions" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-a-gnumeric-session" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.2.5 Replay keyboard and mouse</h3>
+<a name="index-Replay-keyboard-and-mouse"></a>
+<p>Replay keyboard and mouse from the file km-rec.xnl. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay --keyboard --mouse --file kbd-rec.xnl</code>
+</pre></td></tr></table>
+<p>After having typed this Xnee replays all your keyboard and mouse actions. 
+Xnee moves your pointer and writes the the same stuff as you did when
+recording. 
+</p>
+
+
+<hr size="6">
+<a name="Replay-a-gnumeric-session"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-keyboard-and-mouse" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-a-gnumeric-session-with-synchronisation-data" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.2.6 Replay a gnumeric session</h3>
+<a name="index-Replay-a-gnumeric-session"></a>
+<p>Replay the gnumeric session above
+<br>
+Start a terminal emulator (e.g xterm)
+<code>xterm&amp;</code>
+Start a new fresh gnumeric spreadsheet
+<code>gnumeric&amp;</code>
+</p>
+<p>Start Xnee
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay  --file gnumeric.xnl</code>
+</pre></td></tr></table>
+<p>Xnee will now do the same stuff you did when recording. It may happen 
+that some user actions are replayed to early. This is so because Xnee has
+no way of knowing if it is in sync with the recorded session.
+</p>
+
+
+
+<hr size="6">
+<a name="Replay-a-gnumeric-session-with-synchronisation-data"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-a-gnumeric-session" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-a-gnumeric-session-with-synchronisation-data-setting-threshold" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.2.7 Replay a gnumeric session with synchronisation data</h3>
+<a name="index-Replay-a-gnumeric-session-with-synchronisation-data"></a>
+<p>Replay the second gnumeric session above.
+<br>
+Start a terminal emulator (e.g xterm)
+<code>xterm&amp;</code>
+Start a new fresh gnumeric spreadsheet
+<code>gnumeric&amp;</code>
+</p>
+
+<p>Start Xnee
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay  --file gnumeric2.xnl</code>
+</pre></td></tr></table>
+<p>Xnee will now do the same stuff you did when recording. It may happen 
+that the replaying slows down. This is because Xnee is currently out of sync. 
+When being out of sync Xnee slows down a bit and checks the thresholds if it
+is allowed to continue. Xnee will most probably find itself in sync after
+a short while. All recorded user actions should have occured the same way
+as when recording.
+</p>
+
+<hr size="6">
+<a name="Replay-a-gnumeric-session-with-synchronisation-data-setting-threshold"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-a-gnumeric-session-with-synchronisation-data" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Retyper" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replayer" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.2.8 Replay a gnumeric session with synchronisation data setting threshold</h3>
+<a name="index-Replay-a-gnumeric-session-with-synchronisation-data-setting-threshold"></a>
+<p>Replay the second gnumeric session above.
+<br>
+Start a terminal emulator (e.g xterm)
+<code>xterm&amp;</code>
+Start a new fresh gnumeric spreadsheet
+<code>gnumeric&amp;</code>
+</p>
+
+<hr size="6">
+<a name="Retyper"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-a-gnumeric-session-with-synchronisation-data-setting-threshold" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Retype-the-help-printout" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">5.3 Retyper</h2>
+
+<hr size="6">
+<a name="Retype-the-help-printout"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Retyper" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Retype-a-file" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Retyper" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.3.1 Retype the help printout</h3>
+<a name="index-Retype-the-help-printout"></a>
+<p>If you want Xnee to fake a user typing the help printout from xnee
+you can use the <code>--type-help</code> option.
+<br>
+Start a terminal emulator (e.g xterm) and an editor (e.g emacs).
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>xterm &amp;</code>
+</pre></td></tr></table>
+<table><tr><td>&nbsp;</td><td><pre class="example"><code>emacs &amp;</code>
+</pre></td></tr></table>
+<p>Retype the help printout by starting xnee with a 10 seconds delay delay.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --time 10 --type-help</code>
+</pre></td></tr></table>
+<p>Move your mouse to the editor and make the editor have focus.
+Wait a few seconds and xnee will type the help. You will now also have a 
+copy of help text.
+</p>
+
+<hr size="6">
+<a name="Retype-a-file"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Retype-the-help-printout" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Distributor" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Retyper" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.3.2 Retype a file</h3>
+<a name="index-Retype-a-file"></a>
+<p>If you want Xnee to fake a user typing the letters as found in a text 
+file you can use the retype mode. Note that it isn&rsquo;t possible to retype all
+characters yet. This will be implemented as soon as possible. We&rsquo;ll give 
+an example on how to use this mode.
+<br>
+Start a terminal emulator (e.g xterm)
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>xterm &amp;</code>
+</pre></td></tr></table>
+<p>Create a text file
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>echo &quot;Hi Xnee&quot; &gt; testfile.txt</code>
+</pre></td></tr></table>
+
+<p>Retype the contents of this file to another file by starting xnee 
+with a 10 seconds delay delay.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --time 10 --retype-file testfile.txt</code>
+</pre></td></tr></table>
+<p>Start the fabulous editor <code>cat</code>
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cat &gt; copiedfile.txt</code>
+</pre></td></tr></table>
+<p>Wait a few seconds and xnee will retype the letters in the file 
+<code>testfile.txt</code>. You will now also have a copy of that file.
+The copy is called copiedfile.txt. This is a realy a stupid way
+to copy a file but this option opens up a few possibilities.
+</p>
+
+
+<hr size="6">
+<a name="Distributor"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Retype-a-file" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Distribute-your-mouse-motions" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">5.4 Distributor</h2>
+<p>With the distribution mode Xnee can send your device events to 
+multiple displays. 
+</p>
+<hr size="6">
+<a name="Distribute-your-mouse-motions"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Distributor" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Distribute-the-replaying-of-mouse-motions" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Distributor" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.4.1 Distribute your mouse motions</h3>
+<a name="index-Distribute-your-mouse-motions"></a>
+<p>You can distribute your mouse motions to the displays frodo:0.0 and
+sam:0.0 
+<br>
+Start a terminal emulator (e.g xterm)
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>xterm &amp;</code>
+</pre></td></tr></table>
+<p>Start xnee
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --distribute frodo:0,sam:0.0</code>
+<code> --record --mouse</code>
+</pre></td></tr></table>
+
+<p>If you have setup authority correct on frodo and sam you will
+see all you mouse motions being done on those displays as well.
+</p>
+
+<hr size="6">
+<a name="Distribute-the-replaying-of-mouse-motions"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Distribute-your-mouse-motions" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Distribute-the-retyping-of-a-file" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Distributor" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.4.2 Distribute the replaying of mouse motions</h3>
+<a name="index-Distribute-the-replaying-of-mouse-motions"></a>
+<p>Replay and distribute mouse motions as found in the file 
+<code>mouse-rec.xnl</code>. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --replay  --file mouse-rec.xnl</code>
+   <code> --distribute frodo:0,sam:0.0</code>
+</pre></td></tr></table>
+<p>Xnee will now imitate exactly what you did when you recorded this file on 
+your host as well on frodo and sam.
+</p>
+
+
+<hr size="6">
+<a name="Distribute-the-retyping-of-a-file"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Distribute-the-replaying-of-mouse-motions" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Key" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Distributor" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.4.3 Distribute the retyping of a file</h3>
+<a name="index-Distribute-the-retyping-of-a-file"></a>
+<p>If you want Xnee to to distribute the fakeing of a user typing the 
+letters as found in a text file you can use the retype mode together
+with the distribution mode. 
+<br>
+Start a terminal emulator (e.g xterm) on each of the hosts
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>xterm &amp;</code>
+</pre></td></tr></table>
+<p>Create a text file. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>echo &quot;Hi again Xnee&quot; &gt; distfile.txt</code>
+</pre></td></tr></table>
+
+<p>Retype the contents of this file to another file by starting xnee 
+with a 10 seconds delay delay.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --time 10 --retype-file distfile.txt</code>
+<code> --distribute frodo:0,sam:0.0 </code>
+</pre></td></tr></table>
+<p>Start the fabulous editor <code>cat</code> on the terminal emulators on each the 
+terminals.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cat &gt; copiedfile.txt</code>
+</pre></td></tr></table>
+<br>
+<p>If you have setup authority correct on frodo and sam you will, after
+a few seconds, see xnee retype the letters in the file 
+<code>distfile.txt</code>. You will now also have three copies of that file.
+On copy on each host. The copy is called copiedfile.txt. This might 
+seem like a stupid way to copy a file to three locations but this
+is just an example.
+</p>
+
+
+
+<hr size="6">
+<a name="Key"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Distribute-the-retyping-of-a-file" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Stop-Xnee-with-key" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">5.5 Key</h2>
+
+<hr size="6">
+<a name="Stop-Xnee-with-key"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Key" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Pausing-and-resuming-Xnee-with-key" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Key" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.5.1 Stop Xnee with key</h3>
+<a name="index-Stop-Xnee-with-key"></a>
+<p>You can stop xnee by specifying a key. Make
+sure that this key isn&rsquo;t grabbed by another X client (e.g by the
+Window Manager). Let&rsquo;s say that you want Xnee to stop recording if you press
+Control and h. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record --mouse --events-to-record -1 --stop-key h</code>
+</pre></td></tr></table>
+<p>This will make xnee record mouse events until you press h. 
+All printouts are done to stdout so you can see that Xnee stops when you
+press the key. 
+<br>
+Move your mouse for a while and you&rsquo;ll see xnee print out lots of lines. 
+<br>
+Press h. 
+<br>
+Xnee will now have stopped recording.
+</p>
+
+<hr size="6">
+<a name="Pausing-and-resuming-Xnee-with-key"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Stop-Xnee-with-key" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-macro" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Key" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.5.2 Pausing and resuming Xnee with key</h3>
+<a name="index-Pausing-and-resuming-Xnee-with-key"></a>
+<p>You can pause and resum xnee by specifying a key. 
+Make sure that this key isn&rsquo;t grabbed by another X client (e.g by 
+the Window Manager). Let&rsquo;s say that you want Xnee to pause recording if you 
+press p and to resume when pressing Comntrol and r. 
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record --mouse --events-to-record -1 --pause-key p \</code>
+   <code>--resume-key r</code>
+</pre></td></tr></table>
+<p>This will make xnee record mouse events until you press p. 
+All printouts are done to stdout so you can see that Xnee stops when you
+press the key. 
+<br>
+Move your mouse for a while and you&rsquo;ll see xnee print out lots of lines. 
+<br>
+Press p. 
+<br>
+Xnee will now have paused recording. Move your mouse for a while and note that
+nothing is printed.
+<br>
+Press r. 
+<br>
+Xnee will now have resumed recording. Move your mouse for a while and note that
+xnee begins its printouts.
+</p>
+
+<hr size="6">
+<a name="Using-macro"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Pausing-and-resuming-Xnee-with-key" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Define-a-simple-macro" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">5.6 Using macro</h2>
+<p>Macors can be used in various applications allthough many applicaions have 
+a macro functionality built in (e.g emacs). 
+</p>
+<hr size="6">
+<a name="Define-a-simple-macro"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Using-macro" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Define-another-simple-macro" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-macro" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.6.1 Define a simple macro</h3>
+<a name="index-Define-a-simple-macro"></a>
+<p>There are plenty of tools that bind a key combination to 
+different actions. For various reasons the author of this manual is familliar
+with xrebind so we will use xrebind in this example.
+<br>
+The first thing to do is to decide which key combination to tie
+to the wanted action. Let&rsquo;s say we want to use one of the funtion keys, F1. 
+We then have to find out which keycode belongs to that key. The action we will 
+bind to this key combination will be the replaying of a recorded
+session from the previous examples. 
+<br>
+We use Xnee to find the keycode for F1. Start xnee.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">   <code>cnee --record --keyboard --events-to-record 20</code>
+</pre></td></tr></table>
+<p>Press the F1 key and see what number was printed out. It will look something
+like this:
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>0,2,0,0,0,67,0,90300078</code>
+<code>0,3,0,0,0,67,0,90300156</code>
+</pre></td></tr></table>
+<p>The interesting part here is the 6th column. In our example we find 67, which
+is the keycode for F1.
+<br>
+Now we move on to setup xrebind to grab F1 and bind that to replay the 
+mouse motions from the file <code>mouse-rec.xnl</code>. Open or create a new file
+in your home directory called <code>.xrbrc</code> and add the lines.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>XrebindGrab</code>
+<code>{</code>
+<code>  Action      = Execute</code>
+<code>  GrabKeycode = 67</code>
+<code>  Modifier    = AnyModifier</code>
+<code>  Command     = xnee  --replay --file mouse-rec.xnl</code>
+<code>  Comment     = Starting xnee replay</code>
+<code>  AutoRepeat  = false</code>
+<code>  Fork        = true</code>
+<code>}</code>
+</pre></td></tr></table>
+<p>Let&rsquo;s try it. Start xrebind with verbose printouts.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>xrebind --verbose</code>
+</pre></td></tr></table>
+<p>Press F1 and the recorded session from the previous example shall be replayed. You
+can also see in the verbose printouts that xrebind executes xnee.
+</p>
+
+<hr size="6">
+<a name="Define-another-simple-macro"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Define-a-simple-macro" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-macro" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.6.2 Define another simple macro</h3>
+<a name="index-Define-another-simple-macro"></a>
+<p>Let&rsquo;s say we want to bind Control and e to execute the session as in the
+example above. This time setting up xrebind is a bit easier.
+<br>
+Setup xrebind to grab F1 and bind that to replay the 
+mouse motions from the file <code>mouse-rec.xnl</code> by opening or create a 
+new file in your home directory called <code>.xrbrc</code> and add the lines.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>XrebindGrab</code>
+<code>{</code>
+<code>  Action      = Execute</code>
+<code>  GrabKey     = e</code>
+<code>  Modifier    = Control</code>
+<code>  Command     = xnee  --replay --file mouse-rec.xnl</code>
+<code>  Comment     = Starting xnee replay</code>
+<code>  AutoRepeat  = false</code>
+<code>  Fork        = true</code>
+<code>}</code>
+<code>e, Control, Exec, xnee,  --replay --file mouse-rec.xnl, \</code>
+<code>Fork, NoAutoRepeat</code>
+</pre></td></tr></table>
+<p>Let&rsquo;s try it. Start xrebind with verbose printouts.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>xrebind --verbose</code>
+</pre></td></tr></table>
+<p>Press Control and e and the recorded session from the previous example 
+shall be replayed.
+</p>
+
+
+
+
+
+
+
+
+
+
+
+<hr size="6">
+<a name="Various-options"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Define-another-simple-macro" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-verbose-mode" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">5.7 Various options</h2>
+
+<hr size="6">
+<a name="Using-verbose-mode"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Various-options" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-human-readable-printouts" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.7.1 Using verbose mode</h3>
+<a name="index-Using-verbose-mode"></a>
+<p>To enable verbose mode, start xnee like this
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --verbose --record --mouse</code>
+</pre></td></tr></table>
+<p>Move the mouse for a while and you&rsquo;ll lots of verbose printouts that 
+usualy isn&rsquo;t there.
+</p>
+
+<hr size="6">
+<a name="Using-human-readable-printouts"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Using-verbose-mode" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-a-differet-screen-resolution" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.7.2 Using human readable printouts</h3>
+<a name="index-Using-human-readable-printouts"></a>
+<p>To enable human printout mode, start xnee like this
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --human-printout --record --mouse</code>
+</pre></td></tr></table>
+<p>Move the mouse for a while and you&rsquo;ll see the data printed out in an almost
+human friendly format.
+</p>
+
+
+<hr size="6">
+<a name="Using-a-differet-screen-resolution"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Using-human-readable-printouts" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-a-offset-when-replaying" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.7.3 Using a differet screen resolution</h3>
+<a name="index-Using-a-differet-screen-resolution"></a>
+<p>If a session was recorded on a screen with another resolution than 
+on the one where we replay the session xnee will translate all coordinates
+automagically. However, you can force xnee to use a specific resolution when 
+replaying. To do this, start xnee like this
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --replay --file mouse-rec.xnl \ </code>
+<code>--replay-resolution  800x600</code>
+</pre></td></tr></table>
+<p>Xnee will now replay the events recorded in the sessions file 
+<code>mouse-rec.xnl</code> as if the screen has a resolution of 800x600. 
+</p>
+
+<hr size="6">
+<a name="Using-a-offset-when-replaying"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Using-a-differet-screen-resolution" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-a-window-position-recall" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.7.4 Using a offset when replaying</h3>
+<a name="index-Using-a-offset-when-replaying"></a>
+<p>If a session was recording a centered window with a window manager 
+and is to bo replayed without a window manager (still centered) you 
+can use the offset switch to make Xnee replay the events in order to
+get the coordinates right.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --replay --file mouse-rec.xnl \ </code>
+<code>--replay-offset 12,-7</code>
+</pre></td></tr></table>
+<p>Xnee will now replay the events recorded in the sessions file 
+<code>mouse-rec.xnl</code> and adding 12 to the x coordinate and subtract
+7 from the y coordinate. 
+</p>
+
+<hr size="6">
+<a name="Using-a-window-position-recall"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Using-a-offset-when-replaying" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Using-no-resolution-translation" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.7.5 Using a window position recall</h3>
+<a name="index-Using-a-window-position-recall"></a>
+<p>For some reason a replayed window may pop up at a different position
+as when recorded. Xnee can try to solve this by adding the
+<code>recall-window-position</code> option during replay.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --replay --file mouse-rec.xnl \ </code>
+<code>--recall-window-position</code>
+</pre></td></tr></table>
+<p>If a window pops up at a different position when replaying (as whe
+recorded) Xnee moves the new window to the same position as when
+recorded.
+</p>
+
+<hr size="6">
+<a name="Using-no-resolution-translation"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Using-a-window-position-recall" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Record-another-display-than-the-default" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.7.6 Using no resolution translation</h3>
+<a name="index-Using-no-resolution-translation"></a>
+<p>If a session was recorded on a screen with another resolution than the
+on the one where we replay the session xnee will translate all coordinates
+automagically. However, you can force xnee not to use translation. To do this, 
+start xnee like this
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --replay --file mouse-rec.xnl \ </code>
+<code>--no-resolution-adjustment</code>
+</pre></td></tr></table>
+<p>Xnee will now replay the events recorded in the sessions file 
+<code>mouse-rec.xnl</code> as if the screen had the same resolution 
+the recorded one.
+</p>
+
+
+<hr size="6">
+<a name="Record-another-display-than-the-default"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Using-no-resolution-translation" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-to-another-display-than-the-default" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.7.7 Record another display than the default</h3>
+<a name="index-Record-another-display-than-the-default"></a>
+<p>If you want to record another display than the default, as set in the 
+DISPLAY variable, you use the <code>--display</code> option.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --record --mouse --display frodo:0.0 </code>
+</pre></td></tr></table>
+<p>Xnee will now record the mouse events on the display frodo:0.0.
+</p>
+
+<hr size="6">
+<a name="Replay-to-another-display-than-the-default"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Record-another-display-than-the-default" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Shell-scripts-using-Xnee" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Various-options" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">5.7.8 Replay to another display than the default</h3>
+<a name="index-Replay-to-another-display-than-the-default"></a>
+<p>If you want to replay to another display than the default, as set in the 
+DISPLAY variable, you use the <code>--display</code> option.
+</p><table><tr><td>&nbsp;</td><td><pre class="example"><code>cnee --replay --display frodo:0.0 --file mouse-rec.xnl </code>
+</pre></td></tr></table>
+<p>Xnee will now replay the mouse events on the display frodo:0.0.
+</p>
+<hr size="6">
+<a name="Shell-scripts-using-Xnee"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-to-another-display-than-the-default" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Examples" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">5.8 Shell scripts using Xnee</h2>
+<a name="index-Shell-scripts-using-Xnee"></a>
+<p>Insted of onvoking Xnee for every time you need to fake events
+you can make use of the shell functions as delivered with Xnee. 
+With these functions you can start one instance of Xnee and fake
+device events whenever you need.
+</p><table><tr><td>&nbsp;</td><td><pre class="example">
+<code>#!/bin/bash </code>
+<code> </code>
+<code># Source in handy functions </code>
+<code>. /usr/share/xnee/xnee.sh </code>
+<code> </code>
+<code># Loop and press buttons </code>
+<code>TMP=0 </code>
+<code>while [ $TMP -le 5]</code>
+<code>do</code>
+<code>  TMP=$(($TMP+1))</code>
+<code>  xnee_fake_button $TMP </code>
+<code>done</code>
+<code> </code>
+<code># Just a simple example ....don't bother to understand </code>
+<code>tar cvf /tmp/crap.tar *</code>
+<code>sleep 2</code>
+<code> </code>
+<code># Fake ls and Enter </code>
+<code>xnee_fake_key l</code>
+<code>xnee_fake_key s</code>
+<code>xnee_fake_key XK_Return</code>
+<code> </code>
+<code> </code>
+</pre></td></tr></table>
+<p>This example will fake press and release of the mouse button and 
+do fake press and release of ls followed by a press and release 
+of Enter.... and of course, you&rsquo;ll get a tar file in /tmp.
+</p>
+
+<p>Make sure that the path to the <code>xnee.sh</code> is correct.
+</p>
+
+
+
+<hr size="6">
+<a name="Programs"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Shell-scripts-using-Xnee" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#cnee-_002d-cnee_0027s-not-an-event-emulator" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Examples" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Xnee-Programs"></a>
+<h1 class="chapter">6. Xnee Programs</h1>
+
+<p>GNU Xnee consists of three different programs, cnee, gnee and pnee. 
+</p>
+
+
+<hr size="6">
+<a name="cnee-_002d-cnee_0027s-not-an-event-emulator"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Programs" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#gnee-_002d-gnee_0027s-not-an-emulator-either" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Programs" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">6.1 cnee - cnee&rsquo;s not an event emulator</h2>
+
+<p>This is the Xnee command line program. This programs contains most
+features and is the basis for this documentation.
+</p>
+<p>For a user not used to X11 it is probably a good idea to start with
+gnee or pnee instead or start using cnee in demonstration mode:
+<code>cnee --demo</code>
+</p>
+
+<hr size="6">
+<a name="gnee-_002d-gnee_0027s-not-an-emulator-either"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#cnee-_002d-cnee_0027s-not-an-event-emulator" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#pnee-_002d-pnee_0027s-not-even-emulating" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Programs" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">6.2 gnee - gnee&rsquo;s not an emulator either</h2>
+
+<p>This is a GUI (using GTK2/Gnome) with most of the features of
+cnee. The GUI has been designed for ease of use.
+</p>
+<p>Currently there are no plans for making a separate manual for gnee.
+</p>
+<hr size="6">
+<a name="pnee-_002d-pnee_0027s-not-even-emulating"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#gnee-_002d-gnee_0027s-not-an-emulator-either" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Reporting-pnee-bugs" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Programs" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Programs" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">6.3 pnee - pnee&rsquo;s not even emulating</h2>
+
+<p>This is a Gnome panel applet with a minimal set of features. Ease of
+use is the motto for this program. It is intended for users not being
+experts on X11 but still wants to record and replay a session for what
+ever purpose. By default pnee have settings that need not be changed
+for most cases. You can, however, launch the preferences dialog and
+set your preferred values as in most other applets.
+</p>
+<p>If you find pnee a bit limited we suggest you switch over to using
+cnee.
+</p>
+<p><b>Note</b>: If pnee hangs you can press the stop button twice to make a
+reset. Hopefully this will solve the problem.
+</p>
+<hr size="6">
+<a name="Reporting-pnee-bugs"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#pnee-_002d-pnee_0027s-not-even-emulating" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Programs" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#pnee-_002d-pnee_0027s-not-even-emulating" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">6.3.1 Reporting pnee bugs</h3>
+<a name="index-Reporting-pnee-bugs"></a>
+
+<p>By default pnee writes error, verbose printouts and warnings to stderr
+which will not be visible to you as a user, since pnee will be started
+automatically along with the other applets. If you start up the
+preferences dialog you can choose a file for pnee printouts. After
+that you should turn on verbose logging (also in the preferences
+dialog) and then reproduce the bug and send over the file to
+<a href="mailto:[e-mail]">[e-mail]</a>.
+
+</p>
+<hr size="6">
+<a name="File-format"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Reporting-pnee-bugs" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Project-file" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Programs" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="File-types-and-format"></a>
+<h1 class="chapter">7. File types and format</h1>
+
+<p>The files used by Xnee are
+</p><ul>
+<li>  Xnee Project File
+</li><li>  Xnee Session File
+</li></ul>
+
+<p>These files must follow the Xnee File Format.
+</p>
+<hr size="6">
+<a name="Project-file"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#File-format" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Create-a-project-file" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">7.1 Project file</h2>
+<a name="index-Project-file"></a>
+<p>Xnee can be set either using command line options (when using xnee) or by
+clicking the correct buttons etc in the GUI (using gnee). Instead of setting 
+the same settings over and over again, you can use the Xnee Project File. 
+</p>
+
+<hr size="6">
+<a name="Create-a-project-file"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Project-file" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-Session-file" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Project-file" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">7.1.1 Create a project file</h3>
+<a name="index-Create-a-project-file"></a>
+<p>You can create a project by yourself. This can be done using 
+the <code>write-settings</code> option in cnee or the &ldquo;save settings to file&rdquo; 
+when using gnee or you can use the Xnee GUI (gnee) to write one.
+You can also write one by yourself in your favorite editor.  Just make sure you 
+follow the Xnee format. For information and specification on this format read 
+the Xnee format chapter.
+&nbsp;
+</p>
+<p>The authors of Xnee suggests you start of with a generated project file. To get one 
+such file, type the following
+<code>cnee --mouse --keyboard --write-settings new_proj.xnp</code>. You will now 
+have a file <code>new_proj.xnp</code> with some useful values, which you can edit as you wish.
+&nbsp;
+</p>
+<p>To use this file to record, simply type
+<code>cnee --record --project new_proj.xnp</code>
+</p>
+
+<hr size="6">
+<a name="Xnee-Session-file"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Create-a-project-file" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-file-format" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">7.2 Xnee Session file</h2>
+<a name="index-Session-file"></a>
+<p>The Xnee session files are the printouts from a recorded session
+following the Xnee File Format. For information and specification on
+this format read the Xnee File Format chapter.
+</p>
+
+
+<hr size="6">
+<a name="Xnee-file-format"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Xnee-Session-file" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-directives" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">7.3 Xnee file format</h2>
+<p>The Xnee Format is divided into different directives. 
+The format is line based, meaning that
+</p>
+<ul>
+<li>  there is one directive per line
+</li><li>  one line contains one (and only one) directive
+</li></ul>
+
+<p>These directives are definied as follows. 
+</p>
+<hr size="6">
+<a name="Xnee-directives"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Xnee-file-format" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Comment" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#File-format" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">7.4 Xnee directives</h2>
+<p>The following directives are used in Xnee:
+</p><table>
+<tr><td width="0%"></td><td width="30%"><b>Directives</b></td><td width="70%"><b>Description</b></td></tr>
+<tr><td width="0%"></td><td width="30%">Comment</td><td width="70%">This is used to comment the various files</td></tr>
+<tr><td width="0%"></td><td width="30%">Project</td><td width="70%">These contains information about the session- or project file</td></tr>
+<tr><td width="0%"></td><td width="30%">Settings</td><td width="70%">Data used when recording and replaying</td></tr>
+<tr><td width="0%"></td><td width="30%">Replay data</td><td width="70%">Recorded replayable data (used when replaying)</td></tr>
+<tr><td width="0%"></td><td width="30%">Script replay data</td><td width="70%">Scriptable primitives</td></tr>
+<tr><td width="0%"></td><td width="30%">Mark</td><td width="70%">Lines inserted in the seesion file when a modifier+key was pressed</td></tr>
+<tr><td width="0%"></td><td width="30%">Execution</td><td width="70%">Lines that trigger the execution of an external program</td></tr>
+<tr><td width="0%"></td><td width="30%">Project information</td><td width="70%">Project</td></tr>
+</table>
+
+
+
+
+<hr size="6">
+<a name="Comment"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Xnee-directives" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Settings" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-directives" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">7.4.1 Comment</h3>
+<a name="index-Comment-directives"></a>
+
+
+<table>
+<tr><td width="0%"></td><td width="20%"><b>First token</b></td><td width="50%"><b>Interpretation</b></td></tr>
+<tr><td width="0%"></td><td width="20%">#</td><td width="50%">The whole line is ignored.</td></tr>
+</table>
+
+<p>As long as the first token is <code>#</code> the whole line is intrepreted as a comment, just
+as in bash.
+</p>
+
+<hr size="6">
+<a name="Settings"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Comment" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Replay-1" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-directives" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">7.4.2 Settings</h3>
+<a name="index-Settings"></a>
+
+<table>
+<tr><td width="45%"><b>Settings directive</b></td><td width="15%"><b>Argument</b></td><td width="60%"><b>Interpretation</b></td></tr>
+<tr><td width="45%">data-to-record</td><td width="15%">integer</td><td width="60%">Limits the number of data to record to to the integer value</td></tr>
+<tr><td width="45%">events-to-record</td><td width="15%">integer</td><td width="60%">Limits the number of events to record to to the integer value</td></tr>
+<tr><td width="45%">time-to-record</td><td width="15%">integer</td><td width="60%">Limits the number of seconds to record to to the integer value</td></tr>
+<tr><td width="45%">display</td><td width="15%">string</td><td width="60%">Sets the display to record or replay to the string</td></tr>
+<tr><td width="45%">distribute</td><td width="15%">string</td><td width="60%">Distribute all recorded or replayed replayable events to the display given by the string</td></tr>
+<tr><td width="45%">file</td><td width="15%">string</td><td width="60%">Read replay data from the file given by the string</td></tr>
+<tr><td width="45%">out-file</td><td width="15%">string</td><td width="60%">Print recorded data to the file given by the string</td></tr>
+<tr><td width="45%">plugin</td><td width="15%">string</td><td width="60%">Use the plugin given by the string</td></tr>
+<tr><td width="45%">first-last</td><td width="15%">boolean</td><td width="60%">Print only first and last of successive MotionNotify events</td></tr>
+<tr><td width="45%">verbose</td><td width="15%">boolean</td><td width="60%">Use verbose debugging printout</td></tr>
+<tr><td width="45%">buffer-verbose</td><td width="15%">boolean</td><td width="60%">Use verbose buffer verbose printouts (not built by default)</td></tr>
+<tr><td width="45%">time</td><td width="15%">integer</td><td width="60%">Delay the start of the Xnee action</td></tr>
+<tr><td width="45%">all-clients</td><td width="15%">boolean</td><td width="60%">Record all curret and future clients (default)</td></tr>
+<tr><td width="45%">future-clients</td><td width="15%">boolean</td><td width="60%">Record only future clients</td></tr>
+<tr><td width="45%">human-printout</td><td width="15%">boolean</td><td width="60%">Prints the recorded data in a (quite) more ser friendly format</td></tr>
+<tr><td width="45%">sync-mode</td><td width="15%">boolean</td><td width="60%">Sets recording mode</td></tr>
+<tr><td width="45%">speed-percent</td><td width="15%">integer</td><td width="60%">Sets the replaying speed percentage to the integer value</td></tr>
+<tr><td width="45%">stop-key</td><td width="15%"><acronym>string</acronym></td><td width="60%">Sets the stop key combination to the string</td></tr>
+<tr><td width="45%">pause-key</td><td width="15%"><acronym>string</acronym></td><td width="60%">Sets the pause key combination to the string</td></tr>
+<tr><td width="45%">resume-key</td><td width="15%"><acronym>string</acronym></td><td width="60%">Sets the resume key combination to the string</td></tr>
+<tr><td width="45%">mark-key</td><td width="15%"><acronym>string</acronym></td><td width="60%">Sets the mark key combination to the string</td></tr>
+<tr><td width="45%">exec-key</td><td width="15%"><acronym>string</acronym></td><td width="60%">Sets the execute key combination to string</td></tr>
+<tr><td width="45%">replay-resolution</td><td width="15%">string</td><td width="60%">Sets the replay resolution to the string</td></tr>
+<tr><td width="45%">replay-resolution</td><td width="15%">string</td><td width="60%">Sets the replay resolution to the string</td></tr>
+<tr><td width="45%">recall-window-position</td><td width="15%"></td><td width="60%">Use window position recall during replay</td></tr>
+<tr><td width="45%">resolution-adjustment</td><td width="15%">boolean</td><td width="60%">Use resolution adjustment, even if the recored resolution differs from the one to replay to</td></tr>
+<tr><td width="45%">event-range</td><td width="15%">range</td><td width="60%">Sets the events to record</td></tr>
+<tr><td width="45%">error-range</td><td width="15%">range</td><td width="60%">Sets the errors to record to range*</td></tr>
+<tr><td width="45%">request-range</td><td width="15%">range</td><td width="60%">Sets the request to record to range*</td></tr>
+<tr><td width="45%">reply-range</td><td width="15%">range</td><td width="60%">Sets the replies to record to range*</td></tr>
+<tr><td width="45%">extension-request-major-range</td><td width="15%">range</td><td width="60%">Sets the extension requests (major) to record to range*</td></tr>
+<tr><td width="45%">extension-request-minor-range</td><td width="15%">range</td><td width="60%">Sets the extension requests (minor) to record to range*</td></tr>
+<tr><td width="45%">extension-reply-major-range</td><td width="15%">range</td><td width="60%">Sets the extension replies (major) to record to range*</td></tr>
+<tr><td width="45%">extension-reply-minor-range</td><td width="15%">range</td><td width="60%">Sets the extension replies (minor) to record to range*</td></tr>
+<tr><td width="45%">force-replay</td><td width="15%">boolean</td><td width="60%">Continue to replay even if Xnee is out of sync</td></tr>
+<tr><td width="45%">max-threshold</td><td width="15%">integer</td><td width="60%">Sets the maximum synchronisation threshold</td></tr>
+<tr><td width="45%">min-threshold</td><td width="15%">integer</td><td width="60%">Sets the minimum synchronisation threshold</td></tr>
+<tr><td width="45%">total-threshold</td><td width="15%">integer</td><td width="60%">Sets the total maximum synchronisation threshold</td></tr>
+<tr><td width="45%">events-to-record</td><td width="15%">integer</td><td width="60%">Sets the number of events to record</td></tr>
+<tr><td width="45%">data-to-record</td><td width="15%">integer</td><td width="60%">Sets the number of data to record</td></tr>
+<tr><td width="45%">time-to-record</td><td width="15%">integer</td><td width="60%">Sets the number of seconds to record</td></tr>
+<tr><td width="45%">store-mouse-position</td><td width="15%"></td><td width="60%">If set, Xnee records the initial mouse position and makes sure that replaying starts from there</td></tr>
+<tr><td width="45%">retype-press-delay</td><td width="15%">integer</td><td width="60%">Xnee delays processing after a faked key press (during retype)
+with integer milli seconds</td></tr>
+<tr><td width="45%">retype-release-delay</td><td width="15%">integer</td><td width="60%">Xnee delays processing after a faked key press (during retype)
+with integer milli seconds</td></tr>
+</table>
+
+
+<a name="index-Xnee-Settings-Arguments"></a>
+
+<table>
+<tr><td width="30%"><b>Settings argument</b></td><td width="40%"><b>Description</b></td><td width="30%"><b>Example</b></td></tr>
+<tr><td width="30%"><code>integer</code></td><td width="40%">is an integer value.</td><td width="30%">1</td></tr>
+<tr><td width="30%"><code>string</code></td><td width="40%">is a string.</td><td width="30%">localhost</td></tr>
+<tr><td width="30%"><code>boolean</code></td><td width="40%">is a boolean value given by true/1 or false/0</td><td width="30%">true, false, 0, 1</td></tr>
+<tr><td width="30%"><code>subrange</code></td><td width="40%">Subrange is gives a range of data by specifying a start and stop
+      data. In the case of one data the stop data can be omitted.</td><td width="30%">2-5 or MapNotify</td></tr>
+<tr><td width="30%"><code>range</code></td><td width="40%">Ranges are a comma separated list of subranges.</td><td width="30%">2-3,MotionNotify-MapNotify,GravityNotify,PropertyNotify,30</td></tr>
+</table>
+
+
+
+
+<hr size="6">
+<a name="Replay-1"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Settings" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Script-replay-data" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-directives" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">7.4.3 Replay</h3>
+<a name="index-Replay-directive"></a>
+<table>
+<tr><td width="40%"><b>Replay directive</b></td><td width="60%"><b>Interpretation</b></td></tr>
+<tr><td width="40%">0,0</td><td width="60%">not valid</td></tr>
+<tr><td width="40%">0,1</td><td width="60%">not valid</td></tr>
+<tr><td width="40%">0,2,keycode,time</td><td width="60%">KeyPress on key with keycode, used to replay</td></tr>
+<tr><td width="40%">0,3,keycode,time</td><td width="60%">KeyRelease on key with keycode, used to replay</td></tr>
+<tr><td width="40%">0,4,button nr,time</td><td width="60%">ButtonPress on button nr, used to replay</td></tr>
+<tr><td width="40%">0,5,button nr,time</td><td width="60%">ButtonRelease on button nr, used to replay</td></tr>
+<tr><td width="40%">0,6,x,y,time</td><td width="60%">MotionNotify on poistion (x,y), used to replay</td></tr>
+<tr><td width="40%">0,7-XXX,time</td><td width="60%">MotionNotify on poistion (x,y), used to replay</td></tr>
+<tr><td width="40%">1,request number, request type, length, request id, time</td><td width="60%">Recorded request, used during synchronisation</td></tr>
+<tr><td width="40%">2,reply number,time</td><td width="60%">Recorded reply, used during synchronisation</td></tr>
+<tr><td width="40%">3,error number,time</td><td width="60%">Recorded error, used during synchronisation</td></tr>
+</table>
+
+<p>time is the time on the server the data was to the recording Xnee
+client. This time is used to keep the speed intact during replay.
+</p>
+<hr size="6">
+<a name="Script-replay-data"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Replay-1" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Mark" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-directives" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">7.4.4 Script replay data</h3>
+<a name="index-Script-replay-data"></a>
+
+<table>
+<tr><td width="40%"><b>Primitive</b></td><td width="60%"><b>Interpretation</b></td></tr>
+<tr><td width="40%">fake-motion</td><td width="60%">Fakes a mouse motion</td></tr>
+<tr><td width="40%">fake-button-press</td><td width="60%">Fakes a button press</td></tr>
+<tr><td width="40%">fake-button-release</td><td width="60%">Fakes a button release</td></tr>
+<tr><td width="40%">fake-button</td><td width="60%">Fakes a button press and release</td></tr>
+<tr><td width="40%">fake-key-press</td><td width="60%">Fakes a key press</td></tr>
+<tr><td width="40%">fake-key-release</td><td width="60%">Fakes a key release</td></tr>
+<tr><td width="40%">fake-key</td><td width="60%">Fakes a key press and release</td></tr>
+</table>
+
+
+<table>
+<tr><td width="20%"><b>Primitive variable</b></td><td width="20%"><b>Primitive values</b></td><td width="60%"><b>Interpretation</b></td></tr>
+<tr><td width="20%">x=value</td><td width="20%">integer</td><td width="60%">Sets the x position used in fake-motion to value</td></tr>
+<tr><td width="20%">x=value</td><td width="20%">+integer</td><td width="60%">Set the relative motion (x direction) used in fake-motion to value</td></tr>
+<tr><td width="20%">x=value</td><td width="20%">-integer</td><td width="60%">Set the relative motion (x direction) used in fake-motion to value</td></tr>
+<tr><td width="20%">y=value</td><td width="20%">integer</td><td width="60%">Sets the y position used in fake-motion to value</td></tr>
+<tr><td width="20%">y=value</td><td width="20%">+integer</td><td width="60%">Set the relative motion (y direction) used in fake-motion to value</td></tr>
+<tr><td width="20%">y=value</td><td width="20%">-integer</td><td width="60%">Set the relative motion (y direction) used in fake-motion to value</td></tr>
+<tr><td width="20%">button=value</td><td width="20%">integer</td><td width="60%">set the button to fake with fake-button-press, fake-button-release and fake-button to value</td></tr>
+<tr><td width="20%">key=value</td><td width="20%">integer</td><td width="60%">set the key to fake with fake-key-press, fake-key-release and fake-key to value</td></tr>
+</table>
+
+
+
+<hr size="6">
+<a name="Mark"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Script-replay-data" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Exec" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-directives" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">7.4.5 Mark</h3>
+<a name="index-Mark-directive"></a>
+<table>
+<tr><td width="20%"><b>First tokens</b></td><td width="20%"><b>Arguments</b></td><td width="60%"><b>Interpretation</b></td></tr>
+<tr><td width="20%">Mark</td><td width="20%">time string</td><td width="60%">Ignored. This feature is intended to let the user do whatever he/she
+      wants to. This will obviously lead to modifying the source code etc.</td></tr>
+</table>
+
+
+
+<hr size="6">
+<a name="Exec"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Mark" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Project-information" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-directives" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">7.4.6 Exec</h3>
+<a name="index-Exec-directive"></a>
+<table>
+<tr><td width="20%"><b>First tokens</b></td><td width="20%"><b>Arguments</b></td><td width="60%"><b>Interpretation</b></td></tr>
+<tr><td width="20%">Exec</td><td width="20%">command string</td><td width="60%">This is used during to replay to execute a given command. If no
+      command string is found Xnee will try to
+      read the command from the environment variable <code>XNEE_EXEC_COMMAND</code></td></tr>
+</table>
+
+
+
+<hr size="6">
+<a name="Project-information"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Exec" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Xnee-directives" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">7.4.7 Project information</h3>
+<a name="index-Project-information-directive"></a>
+<table>
+<tr><td width="45%"><b>Project information directives</b></td><td width="55%"><b>Arguments</b></td></tr>
+<tr><td width="45%">ProjectName</td><td width="55%">string s is the project name</td></tr>
+<tr><td width="45%">ProjectDescription</td><td width="55%">string s is the project description</td></tr>
+<tr><td width="45%">ProjectCreationDate</td><td width="55%">string s is the project creation date</td></tr>
+<tr><td width="45%">ProjectCreationProgram</td><td width="55%">string s is the name of the program that create the project file</td></tr>
+<tr><td width="45%">ProjectCreationProgVersion</td><td width="55%">string s is the version of the program that create the project file</td></tr>
+<tr><td width="45%">ProjectLastChangeDate</td><td width="55%">string s is the date of the last change of the project file</td></tr>
+<tr><td width="45%">ProjectLastChangeProgram</td><td width="55%">string s is the name of the program that last changed of the project file</td></tr>
+<tr><td width="45%">ProjectLastChangeVersion</td><td width="55%">string s is the version of the program that last changed of the project file</td></tr>
+<tr><td width="45%">ProjectCurrentChangeDate</td><td width="55%">string s is the date of the current change of the project file</td></tr>
+<tr><td width="45%">ProjectCurrentChangeProgram</td><td width="55%">string s is the name of the program that current changed of the project file</td></tr>
+<tr><td width="45%">ProjectCurrentChangeVersion</td><td width="55%">string s is the version of the program that current changed of the project file</td></tr>
+</table>
+
+
+
+<hr size="6">
+<a name="Internals"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Project-information" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#File-format" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+
+<a name="Xnee-Internals"></a>
+<h1 class="chapter">8. Xnee Internals</h1>
+<a name="index-Xnee-Internals"></a>
+<p>This chapter is intended to explain the internal design of libxnee. 
+Hopefully this will lead to a better understanding of how to use Xnee
+and why some features exists and why some doesn&rsquo;t. 
+</p>
+
+
+
+
+
+
+<hr size="6">
+<a name="Synchronisation"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Internals" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Why-synchronise" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Internals" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">8.1 Synchronisation</h2>
+<a name="index-Synchronisation"></a>
+<p>We will try to go through the basics of how Xnee implememnts synchronisation 
+and try to tell you, by using examples, why synhronisation is important.
+</p>
+<hr size="6">
+<a name="Why-synchronise"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Synchronisation" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#How-to-synchronise" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">8.1.1 Why synchronise</h3>
+<a name="index-why-synchronise"></a>
+
+<p>To understand why synchronisation during replay is needed an example is given. 
+</p>
+<p>In this example only mouse and keyboard events are recorded. Think of a session with a web browser. 
+</p>
+<p>During record the following is done:
+</p><ul>
+<li>	Start galeon (or another web browser) via the GNOME panel
+</li><li>	Press Ctrl-O which pops up a window
+</li><li>   Press the left button in the textfield of the popup window
+</li><li>   Enter the URL you want to enter (e.g <a href="http://www.gnu.org">http://www.gnu.org</a>)
+</li><li>   Click on the OK button 
+</li><li>   Then click on another URL (e.g GNU Documentation)
+</li><li>   Then click on another URL (e.g On-Line Documentation)
+</li></ul>
+
+<p>When replaying this session it is often to synchronise the recorded session with what&rsquo;s happening &quot;right now&quot; on the display since sometimes (or rather always) there can be different response times from the same URL. 
+</p>
+<p>During replay the following is done:
+</p><ul>
+<li>   Galeon is started
+</li><li>   Ctrl-O is typed which pops up a window
+</li><li>   Press the left button in the textfield of the popup window
+</li><li>   Enter the URL you want to enter (e.g <a href="http://www.gnu.org">http://www.gnu.org</a>)
+</li><li>   Click on the OK button 
+</li><li>      ... due to an enormous amount of visitors the GNU web server can&rsquo;t respond as quick as it did when recording. So when the next thing happens
+</li><li>   Then click on another URL (e.g GNU Documentation)
+</li><li>      ... the page hasn&rsquo;t been loaded and when the next event is replayed
+</li><li>   Then click on another URL (e.g On-Line Documentation)
+</li><li>      ... the link isn&rsquo;t there and we&rsquo;re really out of sync with the recorded session
+</li></ul>
+
+
+<hr size="6">
+<a name="How-to-synchronise"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Why-synchronise" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation-is-needed" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">8.1.2 How to synchronise</h3>
+<a name="index-how-to-synchronise"></a>
+<p>Instead we could record some more data than just the mouse and keyboard events. 
+</p>
+<p>During record the following is done:
+</p><ul>
+<li>	Start galeon (or another web browser) via the GNOME panel
+</li><li>   Record some X data that tells us that a window have been created
+</li><li>	Press Ctrl-O which pops up a window
+</li><li>   Record some X data that tells us that a window have been created
+</li><li>   Press the left button in the textfield of the popup window
+</li><li>   Enter the URL you want to enter (e.g <a href="http://www.gnu.org">http://www.gnu.org</a>)
+</li><li>   Click on the OK button 
+</li><li>   Record some X data that tells us that a window have been destroyed
+</li><li>   Then click on another URL (e.g GNU Documentation)
+</li><li>   Record some X data that tells us that a some text has been displayed in a window
+</li><li>   Then click on another URL (e.g On-Line Documentation)
+</li><li>   Record some X data that tells us that a some text has been displayed in a window
+</li></ul>
+<p>The non-mouse-or-keyboard events recorded (window created &amp; text displayed) are record for synchronisation purposes.
+</p>
+<p>During replay the following is done:
+</p><ul>
+<li>	Start galeon (or another web browser) via the GNOME panel
+</li><li>   wait for: the recorded X data to be sent again
+</li><li>	Press Ctrl-O which pops up a window
+</li><li>   wait for: the recorded X data to be sent again
+</li><li>   Press the left button in the textfield of the popup window
+</li><li>   Enter the URL you want to enter (e.g <a href="http://www.gnu.org">http://www.gnu.org</a>)
+</li><li>   Click on the OK button 
+</li><li>   wait for: the recorded X data to be sent again
+</li><li>   Then click on another URL (e.g GNU Documentation)
+</li><li>   wait for: the recorded X data to be sent again
+</li><li>   Then click on another URL (e.g On-Line Documentation)
+</li><li>   wait for: the recorded X data to be sent again
+</li></ul>
+
+
+
+<hr size="6">
+<a name="Synchronisation-is-needed"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#How-to-synchronise" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Different-data-for-different-kind-of-sessions" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">8.1.3 Synchronisation is needed</h3>
+<p>So by recording more data than just the events to be replayed we can synchornise what was recorded with what is going on when replaying. But the data has to be choosen with respect to that the data:
+</p><ul>
+<li>    differs from different sessions (Gimp and Xterm are really different)
+</li><li>    slows down the replay session if there are too many
+</li><li>    is hard to choose since the X protocol is rich
+</li><li>    differs (comparing record and replaying)
+</li><li>    can have different ordering (comparing record and replaying)
+</li></ul>
+
+<hr size="6">
+<a name="Different-data-for-different-kind-of-sessions"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Synchronisation-is-needed" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Slow-replay-session-due-to-too-many-synchronise-data" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">8.1.4 Different data for different kind of sessions</h3>
+<p>If we record an xterm session with all data being recorded and compare that to a recorded GIMP session with all data being recordr we can see that the data to use as synchronisation data differs. AS an example there aren&rsquo;t so many windows created/destryed during an xterm session.
+</p>
+<p>The solve to the the problem of finding out what data to use as synchronisation data one can:
+</p><ul>
+<li>   use the project files delivered with Xnee
+</li><li>   analyse the application (using Xnee&rsquo;s  <code>--human-printouts</code> option) and do some &quot;trial and error&quot;
+</li></ul>
+
+
+<hr size="6">
+<a name="Slow-replay-session-due-to-too-many-synchronise-data"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Different-data-for-different-kind-of-sessions" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#X-protocol-is-rich-and-asynchronous" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">8.1.5 Slow replay session due to too many synchronise data</h3>
+<p>The synchronisation itself doesn&rsquo;t take much time but there are timeouts that makes Xnee paues for a short while (see above). If there are many such timeouts it will lead to a slow or shaky replaying session.
+</p>
+<hr size="6">
+<a name="X-protocol-is-rich-and-asynchronous"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Slow-replay-session-due-to-too-many-synchronise-data" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Different-data-sent" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">8.1.6 X protocol is rich and asynchronous</h3>
+<p>For an end user (with no X expertise) it is hard to read the X protocol specification and make assumptions on what data to use.
+</p>
+<hr size="6">
+<a name="Different-data-sent"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#X-protocol-is-rich-and-asynchronous" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Buffers-and-timeouts" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">8.1.7 Different data sent</h3>
+<p>Even if one starts up a machine from scratch (reboot) when recording and from scratch when replaying there is no guarantee that the data is sent in the same order or that exactly the same amount of data is sent.
+</p>
+
+<hr size="6">
+<a name="Buffers-and-timeouts"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Different-data-sent" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Synchronisation" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h3 class="subsection">8.1.8 Buffers and timeouts</h3>
+<p>To enable synchronisation Xnee buffers data:
+</p><ul>
+<li>    that was read in the session file but hasn&rsquo;t been sent during replay
+</li><li>    that was sent during replay but hasn&rsquo;t been seen in the session
+         file being replayed
+</li></ul>
+<p>For every data read from session file (during replay) that isn&rsquo;t replayable 
+(i e device event) Xnee stores the data in a buffer. Xnee also stores the
+data sent from the X server during playback. The data received from the server
+make the buffer entry for that specific data be decremented. If, on the other 
+hand, the same data was read from file the buffer entry for that data is 
+incremented.
+Before replaying any replayable event Xnee makes sure it is in sync. If Xnee 
+is in sync the replaying 
+continues. If Xnee is out of sync it will look for its thresholds and see
+if it is inside a user specified range. There are three thresholds:
+</p><ul>
+<li>    <b>positive maximum</b>  nr data read from session file
+</li><li>    <b>negative minimum</b>  nr of data sent from X server
+</li><li>    <b>absolute total maximum</b> sum of the absolute values above
+</li></ul>
+<p>If Xnee read one data from file (e.g the event MapNotify) Xnee checks if the 
+buffer entry for the specific data is bigger than the positive maximum value
+(after having incremented the buffer value). 
+</p>
+<p>If Xnee receives one data from the X server (e.g the event MapNotify) it 
+checks if the  buffer entry for the specific data is bigger than the 
+negative minimum value (after having decremented the buffer value). 
+</p>
+<p>Xnee also checks if the absolute sum of the differences for every entry
+in the buffer is higher the a total threshold.
+</p>
+<p>If Xnee is getting out of sync it slows down the speed a bit and tries to 
+continue. However after a while it may happen that Xnee considers that it
+no use to continue since we are too much out of sync.
+<br>
+Xnee compensates for the delay during replay that is caused when being out of 
+sync.
+<br>
+It is possible to tweak the thresholds using the <code>--maximum-threshold</code>,
+<code>--negative-threshold</code> and <code>--total-diff-threshold</code> options. Is is
+also possible to turn off synchronisation completely using the <code>--no-sync</code>
+option.
+
+</p>
+<hr size="6">
+<a name="Requirements"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Buffers-and-timeouts" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Runtime-requirements" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Internals" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#FAQ" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Xnee-Requirements"></a>
+<h1 class="chapter">9. Xnee Requirements</h1>
+<a name="index-requirements"></a>
+
+<hr size="6">
+<a name="Runtime-requirements"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Requirements" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Development-requirements" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#FAQ" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">9.1 Runtime requirements</h2>
+<a name="index-runtime-requirements"></a>
+<p>Xnee requirements:
+</p><ul>
+<li>	RECORD extension
+</li><li>	XTest extension
+</li></ul>
+<p>You can use Xnee in replaying mode without RECORD extension if synchronisation is turned off.
+</p>
+<hr size="6">
+<a name="Development-requirements"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Runtime-requirements" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#FAQ" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#FAQ" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="section">9.2 Development requirements</h2>
+<a name="index-development-requirements"></a>
+<p>For development requirements, please look at the DEVELOPMENT file that is distributed with all packages and with CVS.
+</p>
+
+
+<hr size="6">
+<a name="FAQ"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Development-requirements" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Copying-This-Manual" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Requirements" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Copying-This-Manual" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="FAQ-1"></a>
+<h1 class="chapter">10. FAQ</h1>
+
+
+<dl compact="compact">
+<dt> &lsquo;<samp>Where do I send questions?</samp>&rsquo;</dt>
+<dd><a name="index-questions-is-sent-where_003f"></a>
+<p><a href="mailto:[e-mail]">[e-mail]</a>
+<br>
+</p>
+</dd>
+<dt> &lsquo;<samp>Where and how do I report bugs?</samp>&rsquo;</dt>
+<dd><a name="index-Report-bugs_003f"></a>
+<p>Turn on verbose mode <code>cnee --verbose</code> and save the printouts. 
+Include all printouts and log files in the mail which is sent to
+<a href="mailto:[e-mail]">[e-mail]</a>
+<br>
+</p>
+</dd>
+<dt> &lsquo;<samp>Can you add xxx functionality to Xnee</samp>&rsquo;</dt>
+<dd><p>  Send an email to <a href="mailto:[e-mail]">[e-mail]</a> and we&rsquo;ll consider it.
+</p>
+</dd>
+<dt> &lsquo;<samp>Why the name Xnee?</samp>&rsquo;</dt>
+<dd><a name="index-why-name-it-Xnee"></a>
+<p>We wanted to use a recursive acronym, as GNU (&ldquo;GNU&rsquo;s Not Unix&rsquo;). 
+After having read the Wine documentation, we thought that Xnee is not an 
+Event Emulator would work fine since Xnee is Not an Event Emulator but 
+rather a event recorder and faker. 
+</p>
+</dd>
+<dt> &lsquo;<samp>What does the name cnee mean?</samp>&rsquo;</dt>
+<dd><a name="index-What-does-the-name-cnee-mean_003f"></a>
+<p>          cnee&rsquo;s not an event emulator
+</p>
+</dd>
+<dt> &lsquo;<samp>What does the name gnee mean?</samp>&rsquo;</dt>
+<dd><a name="index-What-does-the-name-gnee-mean_003f"></a>
+<p>          gnee&rsquo;s not an emulator either
+</p>
+</dd>
+<dt> &lsquo;<samp>What does the name pnee mean?</samp>&rsquo;</dt>
+<dd><a name="index-What-does-the-name-gnee-mean_003f-1"></a>
+<p>          pnee&rsquo;s not even emulating
+</p>
+
+</dd>
+<dt> &lsquo;<samp>What doesn't the name gnee mean?</samp>&rsquo;</dt>
+<dd><a name="index-What-does-the-name-gnee-mean_003f-2"></a>
+<p>          gnee&rsquo;s not an Event Emulator  
+</p>
+
+</dd>
+<dt> &lsquo;<samp>What license is Xnee released under ?</samp>&rsquo;</dt>
+<dd><a name="index-license"></a>
+<p>GPL version two or later. Which can be found at
+<a href="http://www.gnu.org/copyleft/gpl.html">http://www.gnu.org/copyleft/gpl.html</a>. Xnee will switch to GPLv3
+as soon as GPLv3 is released.
+</p>
+
+</dd>
+<dt> &lsquo;<samp>Where is the CVS repository?</samp>&rsquo;</dt>
+<dd><p>You can find a CVS tree at <a href="http://savannah.gnu.org">http://savannah.gnu.org</a>.
+You are more than welcome to join
+</p>
+</dd>
+<dt> &lsquo;<samp>Is there a GUI frontend for Xnee ?</samp>&rsquo;</dt>
+<dd><a name="index-GUI-frontend-for-Xnee"></a>
+<p>Yes! Gnee.
+</p>
+
+</dd>
+<dt> &lsquo;<samp>When setting ranges (integers), how do I know what numbers belong</samp>&rsquo; </dt>
+<dd><p>to X11 data?
+<a name="index-what-numbers-belong-to-X11-data_003f"></a>
+You can either type the data name directly (e.g MotionNotify) or you 
+can use the 
+print-xxx-name options. 
+</p><ul>
+<li>  <code>--print-data-name</code> 
+</li><li>  <code>--print-event-name</code>
+</li><li>  <code>--print-error-name</code>
+</li><li>  <code>--print-reply-name</code>
+</li><li>  <code>--print-request-name</code> 
+</li></ul>
+
+</dd>
+<dt> &lsquo;<samp>When I replay to another display the characters are not correct?</samp>&rsquo;</dt>
+<dd><a name="index-replay-to-another-display-the-characters-are-not-correct"></a>
+<p>Make sure you use the same keyboard mapping. 
+<br>
+A typical example:
+<br>
+<br>
+Record local host using Xnee:
+<br>
+<code>cnee --record --out-file recorded_on_local.xnl </code>
+<br>
+<br>
+Store remote keymap:
+<br>
+<code>xmodmap -pke -display remote:0 &gt; remote.map </code>
+<br>
+<br>
+Store local keymap:
+<br>
+<code>xmodmap -pke   &gt; local.map </code>
+<br>
+<br>
+Copy local keymap to remote host:
+<br>
+<code>cat local.map | xmodmap -display remote:0 - </code>
+<br>
+<br>
+Replay previously recorded session:
+<br>
+<code>cnee --replay --file recorded_on_local.xnl --display remote:0 </code>
+<br>
+<br>
+Copy the original remote keymap to remote host:
+<br>
+<code>cat remote.map | xmodmap -display remote:0 - </code>
+<br>
+<br>
+</p>
+</dd>
+<dt> &lsquo;<samp>When starting Xnee I am informed that I am missing the RECORD extension</samp>&rsquo;</dt>
+<dd><a name="index-missing-RECORD-extension"></a>
+<p>Your X server doesn&rsquo;t have the RECORD extension either loaded or compiled. To solve this you have to, depending on what Xserver you have do the following:
+</p>
+</dd>
+<dt> &lsquo;<samp>Can Xnee record more than one display?</samp>&rsquo;</dt>
+<dd><a name="index-can-Xnee-record-more-than-one-display"></a>
+<p>No, we used to consider adding the functionality but have no plans to
+implement it anymore.
+</p>
+</dd>
+<dt> &lsquo;<samp>When starting Xnee I am informed that I am missing the RECORD extension</samp>&rsquo;</dt>
+<dd><a name="index-missing-RECORD-extension-1"></a>
+<p>Your X server doesn&rsquo;t have the RECORD extension either loaded or compiled. To solve this you have to, depending on what Xserver you have do the following:
+</p>
+<ul>
+<li> XFree86 4.0 and higher
+Make sure that the RECORD extension is loaded. This is done by letting the Module section in the X config file (e.g /etc/X11/XF86Config-4) look something like:
+
+<p><code>Section &quot;Module&quot;</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code>Load  &quot;dbe&quot;         # Double-buffering</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code>Load  &quot;GLcore&quot;      # OpenGL support</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code>Load  &quot;dri&quot;         # Direct rendering infrastructure</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code>Load  &quot;glx&quot;         # OpenGL X protocol interface</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code>Load  &quot;extmod&quot;      # Misc. required extensions</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code>Load  &quot;v4l&quot;         # Video4Linux</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code># Load  &quot;pex5&quot;      # PHIGS for X 3D environment (obsolete)</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code>Load  &quot;record&quot;      # X event recorder</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code># Load  &quot;xie&quot;       # X Image Extension (obsolete)</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code># You only need the following two modules if you do not use xfs.</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code># Load  &quot;freetype&quot;  # TrueType font handler</code><br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code># Load  &quot;type1&quot;     # Adobe Type 1 font handler</code><br>
+EndSection
+</p>
+<p>The important load directive (in this case) is the following line<br>
+&nbsp;&nbsp;&nbsp;&nbsp;<code>Load  &quot;record&quot;  # X event recorder</code><br>
+</p>
+
+
+</li><li> X.org, XFree86 (3.3 and lower)  or any other Xserver
+Recompile and reinstall the Xserver and make sure that RECORD extension 
+is built into the Xserver. Please look at the documentation from your 
+Xserver &quot;vendor&quot; on how to do that.
+</li></ul>
+
+</dd>
+<dt>   &lsquo;<samp>How do I build VNC so that I can use Xnee together with it?</samp>&rsquo;</dt>
+<dd><a name="index-Build-VNC-to-be-used-with-Xnee"></a>
+<br>
+<p>Download vnc source from:
+<br>
+<a href="http://www.uk.research.att.com/vnc/xvnchistory.html">http://www.uk.research.att.com/vnc/xvnchistory.html</a>
+<br>
+<br>
+In the file <code>Xvnc/config/cf/vnc.def</code> change NO on the following 
+items to YES as below:
+<br>
+<code>#define BuildRECORD YES</code>
+<br>
+<code>#define BuildRECORDlib YES</code>
+<br>
+<br>
+Download the Xfree86 distribution from <a href="http://www.xfree86.org">http://www.xfree86.org</a>. 
+Specifically, the following dir, 
+(currently in the file <code>X430src-3.tgz file</code> ):
+<br>
+<code>tar zxvf \</code>
+<br>
+<code>X430src-3.tgz </code>
+<br>
+<code>xc/programs/Xserver/record/</code>
+<br>
+<code>xc/programs/Xserver/record/Imakefile</code>
+<br>
+<code>xc/programs/Xserver/record/record.c</code>
+<br>
+<code>xc/programs/Xserver/record/recordmod.c</code>
+<br>
+<code>xc/programs/Xserver/record/set.c</code>
+<br>
+<code>xc/programs/Xserver/record/set.h</code>
+<br>
+<code>xc/programs/Xserver/record/module/</code>
+<br>
+<code>xc/programs/Xserver/record/module/Imakefile</code>
+<br>
+<code>cp -rf \</code>
+<br>
+<code>xc/programs/Xserver/record \</code>
+<br>
+<code>vnc_unixsrc/Xvnc/programs/Xserver</code>
+<br>
+<code>cd libvncauth/</code>
+<code>xmkmf</code>
+<code>make all</code>
+<br>
+<code>cd Xvnc</code>
+<code>make World |&amp; tee LOG</code>
+<br>
+<br>
+Verify the build by running <code>xdpyinfo</code> in an xterm in the vncserver 
+and verify that RECORD and XTEST extensions are loaded.
+</p>
+
+</dd>
+<dt> &lsquo;<samp>How do I ensure that the mouse, during replay, is at the same position (x,y) as when recorded?</samp>&rsquo;</dt>
+<dd><p>Use the <code>--store-mouse-pos</code> option. 
+This will cause Xnee to store the mouse position before starting to record. This position will be used to set the start position before replaying of recorded data starts.
+</p>
+</dd>
+<dt> &lsquo;<samp>How do I ensure that the same window is focused as when recorded?</samp>&rsquo;</dt>
+<dd><p>It&rsquo;s simple, just make sure that you record the window getting focus.
+</p>
+</dd>
+<dt> &lsquo;<samp>The window pops up at different positions when replaying, can Xnee handle that?</samp>&rsquo;</dt>
+<dd><p>Yes, use the <code>--recall-window-position</code> option when
+replaying (with cnee). This makes cnee try yo reposition the window as
+it was positioned when recording the session.
+</p>
+</dd>
+<dt> &lsquo;<samp>Xnee seems to mess up my entire session after replaying a sessions which was interupted by Control-C?</samp>&rsquo;</dt>
+<dd><p>Xnee records the KeyPress belonging to Control. After that the system
+sends Xnee a signal which makes Xnee stop recording. So you end up
+having a Control KeyPress recorded, with no coresponding
+KeyRelease. To solve the screwed up session, press Control (which
+generates a KeyPress and the wanted KeyRelease). If you want to keep
+your recorded session and not want this to happen again, remove the
+last line in the recorded file starting with <code>2,</code>.
+</p>
+
+<p>A better way to interrupt Xnee is to use the stop key option, e.g in
+cnee <code>--stop-key F1</code>. This prevents the above situation.
+</p>
+
+</dd>
+<dt> &lsquo;<samp>Autorepeat is turned off by Xnee, how do I turn it on again?</samp>&rsquo;</dt>
+<dd><p><code>xset r on</code>
+</p>
+
+</dd>
+</dl>
+
+
+
+
+<hr size="6">
+<a name="Copying-This-Manual"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#FAQ" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#GNU-Free-Documentation-License" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#FAQ" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Copying-This-Manual-1"></a>
+<h1 class="appendix">A. Copying This Manual</h1>
+<hr size="6">
+<a name="GNU-Free-Documentation-License"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Copying-This-Manual" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Next section in reading order"> &gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Copying-This-Manual" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Copying-This-Manual" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Next chapter"> &gt;&gt; </a>]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h2 class="appendixsec">A.1 GNU Free Documentation License</h2>
+
+<a name="index-FDL_002c-GNU-Free-Documentation-License"></a>
+<p align="center"> Version 1.2, November 2002
+</p>
+<table><tr><td>&nbsp;</td><td><pre class="display">Copyright &copy; 2000,2001,2002 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</pre></td></tr></table>
+
+<ol>
+<li>
+PREAMBLE
+
+<p>The purpose of this License is to make a manual, textbook, or other
+functional and useful document <em>free</em> in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+</p>
+<p>This License is a kind of &ldquo;copyleft&rdquo;, which means that derivative
+works of the document must themselves be free in the same sense.  It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+</p>
+<p>We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does.  But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book.  We recommend this License
+principally for works whose purpose is instruction or reference.
+</p>
+</li><li>
+APPLICABILITY AND DEFINITIONS
+
+<p>This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License.  Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein.  The &ldquo;Document&rdquo;, below,
+refers to any such manual or work.  Any member of the public is a
+licensee, and is addressed as &ldquo;you&rdquo;.  You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+</p>
+<p>A &ldquo;Modified Version&rdquo; of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+</p>
+<p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter section
+of the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document&rsquo;s overall
+subject (or to related matters) and contains nothing that could fall
+directly within that overall subject.  (Thus, if the Document is in
+part a textbook of mathematics, a Secondary Section may not explain
+any mathematics.)  The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+</p>
+<p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License.  If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant.  The Document may contain zero
+Invariant Sections.  If the Document does not identify any Invariant
+Sections then there are none.
+</p>
+<p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License.  A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+</p>
+<p>A &ldquo;Transparent&rdquo; copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters.  A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text.  A copy that is not &ldquo;Transparent&rdquo; is called &ldquo;Opaque&rdquo;.
+</p>
+<p>Examples of suitable formats for Transparent copies include plain
+<small>ASCII</small> without markup, Texinfo input format, LaTeX input
+format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available
+<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
+PostScript or <acronym>PDF</acronym> designed for human modification.  Examples
+of transparent image formats include <acronym>PNG</acronym>, <acronym>XCF</acronym> and
+<acronym>JPG</acronym>.  Opaque formats include proprietary formats that can be
+read and edited only by proprietary word processors, <acronym>SGML</acronym> or
+<acronym>XML</acronym> for which the <acronym>DTD</acronym> and/or processing tools are
+not generally available, and the machine-generated <acronym>HTML</acronym>,
+PostScript or <acronym>PDF</acronym> produced by some word processors for
+output purposes only.
+</p>
+<p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page.  For works in
+formats which do not have any title page as such, &ldquo;Title Page&rdquo; means
+the text near the most prominent appearance of the work&rsquo;s title,
+preceding the beginning of the body of the text.
+</p>
+<p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language.  (Here XYZ stands for a
+specific section name mentioned below, such as &ldquo;Acknowledgements&rdquo;,
+&ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or &ldquo;History&rdquo;.)  To &ldquo;Preserve the Title&rdquo;
+of such a section when you modify the Document means that it remains a
+section &ldquo;Entitled XYZ&rdquo; according to this definition.
+</p>
+<p>The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document.  These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+</p>
+</li><li>
+VERBATIM COPYING
+
+<p>You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License.  You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute.  However, you may accept
+compensation in exchange for copies.  If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+</p>
+<p>You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+</p>
+</li><li>
+COPYING IN QUANTITY
+
+<p>If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document&rsquo;s license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover.  Both covers must also clearly and legibly identify
+you as the publisher of these copies.  The front cover must present
+the full title with all words of the title equally prominent and
+visible.  You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+</p>
+<p>If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+</p>
+<p>If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+</p>
+<p>It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+</p>
+</li><li>
+MODIFICATIONS
+
+<p>You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it.  In addition, you must do these things in the Modified Version:
+</p>
+<ol>
+<li>
+Use in the Title Page (and on the covers, if any) a title distinct
+from that of the Document, and from those of previous versions
+(which should, if there were any, be listed in the History section
+of the Document).  You may use the same title as a previous version
+if the original publisher of that version gives permission.
+
+</li><li>
+List on the Title Page, as authors, one or more persons or entities
+responsible for authorship of the modifications in the Modified
+Version, together with at least five of the principal authors of the
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.
+
+</li><li>
+State on the Title page the name of the publisher of the
+Modified Version, as the publisher.
+
+</li><li>
+Preserve all the copyright notices of the Document.
+
+</li><li>
+Add an appropriate copyright notice for your modifications
+adjacent to the other copyright notices.
+
+</li><li>
+Include, immediately after the copyright notices, a license notice
+giving the public permission to use the Modified Version under the
+terms of this License, in the form shown in the Addendum below.
+
+</li><li>
+Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document&rsquo;s license notice.
+
+</li><li>
+Include an unaltered copy of this License.
+
+</li><li>
+Preserve the section Entitled &ldquo;History&rdquo;, Preserve its Title, and add
+to it an item stating at least the title, year, new authors, and
+publisher of the Modified Version as given on the Title Page.  If
+there is no section Entitled &ldquo;History&rdquo; in the Document, create one
+stating the title, year, authors, and publisher of the Document as
+given on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.
+
+</li><li>
+Preserve the network location, if any, given in the Document for
+public access to a Transparent copy of the Document, and likewise
+the network locations given in the Document for previous versions
+it was based on.  These may be placed in the &ldquo;History&rdquo; section.
+You may omit a network location for a work that was published at
+least four years before the Document itself, or if the original
+publisher of the version it refers to gives permission.
+
+</li><li>
+For any section Entitled &ldquo;Acknowledgements&rdquo; or &ldquo;Dedications&rdquo;, Preserve
+the Title of the section, and preserve in the section all the
+substance and tone of each of the contributor acknowledgements and/or
+dedications given therein.
+
+</li><li>
+Preserve all the Invariant Sections of the Document,
+unaltered in their text and in their titles.  Section numbers
+or the equivalent are not considered part of the section titles.
+
+</li><li>
+Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a section
+may not be included in the Modified Version.
+
+</li><li>
+Do not retitle any existing section to be Entitled &ldquo;Endorsements&rdquo; or
+to conflict in title with any Invariant Section.
+
+</li><li>
+Preserve any Warranty Disclaimers.
+</li></ol>
+
+<p>If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant.  To do this, add their titles to the
+list of Invariant Sections in the Modified Version&rsquo;s license notice.
+These titles must be distinct from any other section titles.
+</p>
+<p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it contains
+nothing but endorsements of your Modified Version by various
+parties&mdash;for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+</p>
+<p>You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version.  Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity.  If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+</p>
+<p>The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+</p>
+</li><li>
+COMBINING DOCUMENTS
+
+<p>You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+</p>
+<p>The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy.  If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+</p>
+<p>In the combination, you must combine any sections Entitled &ldquo;History&rdquo;
+in the various original documents, forming one section Entitled
+&ldquo;History&rdquo;; likewise combine any sections Entitled &ldquo;Acknowledgements&rdquo;,
+and any sections Entitled &ldquo;Dedications&rdquo;.  You must delete all
+sections Entitled &ldquo;Endorsements.&rdquo;
+</p>
+</li><li>
+COLLECTIONS OF DOCUMENTS
+
+<p>You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+</p>
+<p>You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+</p>
+</li><li>
+AGGREGATION WITH INDEPENDENT WORKS
+
+<p>A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation&rsquo;s users beyond what the individual works permit.
+When the Document is included an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+</p>
+<p>If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document&rsquo;s Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+</p>
+</li><li>
+TRANSLATION
+
+<p>Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections.  You may include a
+translation of this License, and all the license notices in the
+Document, and any Warrany Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers.  In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+</p>
+<p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
+&ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+</p>
+</li><li>
+TERMINATION
+
+<p>You may not copy, modify, sublicense, or distribute the Document except
+as expressly provided for under this License.  Any other attempt to
+copy, modify, sublicense or distribute the Document is void, and will
+automatically terminate your rights under this License.  However,
+parties who have received copies, or rights, from you under this
+License will not have their licenses terminated so long as such
+parties remain in full compliance.
+</p>
+</li><li>
+FUTURE REVISIONS OF THIS LICENSE
+
+<p>The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation License from time to time.  Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.  See
+<a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.
+</p>
+<p>Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License &ldquo;or any later version&rdquo; applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation.  If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation.
+</p></li></ol>
+
+
+
+
+
+
+<hr size="6">
+<a name="Index"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#GNU-Free-Documentation-License" title="Previous section in reading order"> &lt; </a>]</td>
+<td valign="middle" align="left">[ &gt; ]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Copying-This-Manual" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
+<td valign="middle" align="left">[<a href="#Top" title="Up section"> Up </a>]</td>
+<td valign="middle" align="left">[ &gt;&gt; ]</td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left"> &nbsp; </td>
+<td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<a name="Index-1"></a>
+<h1 class="chapter">B. Index</h1>
+<table><tr><th valign="top">Jump to: &nbsp; </th><td><a href="#Index-1_cp_letter-B" class="summary-letter"><b>B</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-C" class="summary-letter"><b>C</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-D" class="summary-letter"><b>D</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-E" class="summary-letter"><b>E</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-F" class="summary-letter"><b>F</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-G" class="summary-letter"><b>G</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-H" class="summary-letter"><b>H</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-I" class="summary-letter"><b>I</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-K" class="summary-letter"><b>K</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-L" class="summary-letter"><b>L</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-M" class="summary-letter"><b>M</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-P" class="summary-letter"><b>P</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-Q" class="summary-letter"><b>Q</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-R" class="summary-letter"><b>R</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-S" class="summary-letter"><b>S</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-U" class="summary-letter"><b>U</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-W" class="summary-letter"><b>W</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-X" class="summary-letter"><b>X</b></a>
+ &nbsp; 
+</td></tr></table>
+<table border="0" class="index-cp">
+<tr><td></td><th align="left">Index Entry</th><th align="left"> Section</th></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-B">B</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-background">background</a></td><td valign="top"><a href="#Background">1.3 Background</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Build-VNC-to-be-used-with-Xnee">Build VNC to be used with Xnee</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-C">C</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-can-Xnee-record-more-than-one-display">can Xnee record more than one display</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-command-line-syntax">command line syntax</a></td><td valign="top"><a href="#Command-line-syntax">3.8.1 Command line syntax</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Comment-directives">Comment directives</a></td><td valign="top"><a href="#Comment">7.4.1 Comment</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Create-a-project-file">Create a project file</a></td><td valign="top"><a href="#Create-a-project-file">7.1.1 Create a project file</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-D">D</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Define-a-simple-macro">Define a simple macro</a></td><td valign="top"><a href="#Define-a-simple-macro">5.6.1 Define a simple macro</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Define-another-simple-macro">Define another simple macro</a></td><td valign="top"><a href="#Define-another-simple-macro">5.6.2 Define another simple macro</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-development-requirements">development requirements</a></td><td valign="top"><a href="#Development-requirements">9.2 Development requirements</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Distribute-the-replaying-of-mouse-motions">Distribute the replaying of mouse motions</a></td><td valign="top"><a href="#Distribute-the-replaying-of-mouse-motions">5.4.2 Distribute the replaying of mouse motions</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Distribute-the-retyping-of-a-file">Distribute the retyping of a file</a></td><td valign="top"><a href="#Distribute-the-retyping-of-a-file">5.4.3 Distribute the retyping of a file</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Distribute-your-mouse-motions">Distribute your mouse motions</a></td><td valign="top"><a href="#Distribute-your-mouse-motions">5.4.1 Distribute your mouse motions</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-distributing">distributing</a></td><td valign="top"><a href="#Distribution">3.2.4 Distribution</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-E">E</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Example-Xnee-Session-files">Example Xnee Session files</a></td><td valign="top"><a href="#Example-Xnee-Session-files">2.1.7 Example Xnee Session files</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Exec-directive">Exec directive</a></td><td valign="top"><a href="#Exec">7.4.6 Exec</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-F">F</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-FDL_002c-GNU-Free-Documentation-License">FDL, GNU Free Documentation License</a></td><td valign="top"><a href="#GNU-Free-Documentation-License">A.1 GNU Free Documentation License</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-features">features</a></td><td valign="top"><a href="#Xnee-features">1.2 Xnee features</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Functional-overview">Functional overview</a></td><td valign="top"><a href="#Functional-overview-1">3.1 Functional overview</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-G">G</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Getting-started">Getting started</a></td><td valign="top"><a href="#Getting-started-1">2.1 Getting started</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-GUI-frontend-for-Xnee">GUI frontend for Xnee</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-H">H</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-how-to-synchronise">how to synchronise</a></td><td valign="top"><a href="#How-to-synchronise">8.1.2 How to synchronise</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-I">I</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Insert-marks-Xnee-with-key-combination">Insert marks Xnee with key combination</a></td><td valign="top"><a href="#Insert-marks-Xnee-with-key-combination">3.9.7 Insert marks Xnee with key combination</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Interupting-xnee">Interupting xnee</a></td><td valign="top"><a href="#Interupting-Xnee">3.9 Interupting Xnee</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-K">K</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-key">key</a></td><td valign="top"><a href="#modifier-and-key">3.9.1 modifier and key</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-L">L</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-license">license</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-limit-the-data">limit the data</a></td><td valign="top"><a href="#Limit-the-data-to-record">3.9.10 Limit the data to record</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-limit-the-events">limit the events</a></td><td valign="top"><a href="#Limit-the-events-to-record">3.9.9 Limit the events to record</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-limit-the-events-1">limit the events</a></td><td valign="top"><a href="#Limit-the-time-to-record">3.9.11 Limit the time to record</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-M">M</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Mark-directive">Mark directive</a></td><td valign="top"><a href="#Mark">7.4.5 Mark</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-missing-RECORD-extension">missing RECORD extension</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-missing-RECORD-extension-1">missing RECORD extension</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-modes">modes</a></td><td valign="top"><a href="#Modes">3.2 Modes</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-modifier">modifier</a></td><td valign="top"><a href="#modifier-and-key">3.9.1 modifier and key</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-P">P</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Pause-Xnee-with-key-combination">Pause Xnee with key combination</a></td><td valign="top"><a href="#Pause-Xnee-with-key-combination">3.9.5 Pause Xnee with key combination</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Pause-Xnee-with-key-combination-1">Pause Xnee with key combination</a></td><td valign="top"><a href="#Pause-Xnee-with-key-combination-1">3.9.6 Pause Xnee with key combination</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Pausing-and-resuming-Xnee-with-key">Pausing and resuming Xnee with key</a></td><td valign="top"><a href="#Pausing-and-resuming-Xnee-with-key">5.5.2 Pausing and resuming Xnee with key</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-plugins">plugins</a></td><td valign="top"><a href="#Xnee-plugins">3.10 Xnee plugins</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Project-file">Project file</a></td><td valign="top"><a href="#Project-file">7.1 Project file</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Project-information-directive">Project information directive</a></td><td valign="top"><a href="#Project-information">7.4.7 Project information</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-Q">Q</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-questions-is-sent-where_003f">questions is sent where?</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-R">R</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-ranges">ranges</a></td><td valign="top"><a href="#Ranges">3.3 Ranges</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Record-a-gnumeric-session">Record a gnumeric session</a></td><td valign="top"><a href="#Record-a-gnumeric-session">5.1.4 Record a gnumeric session</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Record-a-gnumeric-session-with-synchronisation-data">Record a gnumeric session with synchronisation data</a></td><td valign="top"><a href="#Record-a-gnumeric-session-with-synchronisation-data">5.1.5 Record a gnumeric session with synchronisation data</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Record-another-display-than-the-default">Record another display than the default</a></td><td valign="top"><a href="#Record-another-display-than-the-default">5.7.7 Record another display than the default</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Record-keyboard">Record keyboard</a></td><td valign="top"><a href="#Record-keyboard">5.1.2 Record keyboard</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Record-keyboard-and-mouse">Record keyboard and mouse</a></td><td valign="top"><a href="#Record-keyboard-and-mouse">5.1.3 Record keyboard and mouse</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Record-mouse-motions">Record mouse motions</a></td><td valign="top"><a href="#Record-mouse-motions">5.1.1 Record mouse motions</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-recording">recording</a></td><td valign="top"><a href="#Record">3.2.1 Record</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Replay-a-gnumeric-session">Replay a gnumeric session</a></td><td valign="top"><a href="#Replay-a-gnumeric-session">5.2.6 Replay a gnumeric session</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Replay-a-gnumeric-session-with-synchronisation-data">Replay a gnumeric session with synchronisation data</a></td><td valign="top"><a href="#Replay-a-gnumeric-session-with-synchronisation-data">5.2.7 Replay a gnumeric session with synchronisation data</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Replay-a-gnumeric-session-with-synchronisation-data-setting-threshold">Replay a gnumeric session with synchronisation data setting threshold</a></td><td valign="top"><a href="#Replay-a-gnumeric-session-with-synchronisation-data-setting-threshold">5.2.8 Replay a gnumeric session with synchronisation data setting threshold</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Replay-directive">Replay directive</a></td><td valign="top"><a href="#Replay-1">7.4.3 Replay</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Replay-keyboard-actions">Replay keyboard actions</a></td><td valign="top"><a href="#Replay-keyboard-actions">5.2.4 Replay keyboard actions</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Replay-keyboard-and-mouse">Replay keyboard and mouse</a></td><td valign="top"><a href="#Replay-keyboard-and-mouse">5.2.5 Replay keyboard and mouse</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-replay-mouse-motions">replay mouse motions</a></td><td valign="top"><a href="#Replay-mouse-motions">5.2.1 Replay mouse motions</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Replay-to-another-display-than-the-default">Replay to another display than the default</a></td><td valign="top"><a href="#Replay-to-another-display-than-the-default">5.7.8 Replay to another display than the default</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-replay-to-another-display-the-characters-are-not-correct">replay to another display the characters are not correct</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-replay-using-double-speed">replay using double speed</a></td><td valign="top"><a href="#Replay-mouse-motions-using-with-double-speed">5.2.3 Replay mouse motions using with double speed</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-replay-using-half-speed">replay using half speed</a></td><td valign="top"><a href="#Replay-mouse-motions-using-with-half-speed">5.2.2 Replay mouse motions using with half speed</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-replaying">replaying</a></td><td valign="top"><a href="#Replay">3.2.2 Replay</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Report-bugs_003f">Report bugs?</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Reporting-pnee-bugs">Reporting pnee bugs</a></td><td valign="top"><a href="#Reporting-pnee-bugs">6.3.1 Reporting pnee bugs</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-requirements">requirements</a></td><td valign="top"><a href="#Requirements">9. Xnee Requirements</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-retype">retype</a></td><td valign="top"><a href="#Retype">3.2.3 Retype</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Retype-a-file">Retype a file</a></td><td valign="top"><a href="#Retype-a-file">5.3.2 Retype a file</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Retype-the-help-printout">Retype the help printout</a></td><td valign="top"><a href="#Retype-the-help-printout">5.3.1 Retype the help printout</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-runtime-requirements">runtime requirements</a></td><td valign="top"><a href="#Runtime-requirements">9.1 Runtime requirements</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-S">S</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Script-replay-data">Script replay data</a></td><td valign="top"><a href="#Script-replay-data">7.4.4 Script replay data</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Session-file">Session file</a></td><td valign="top"><a href="#Xnee-Session-file">7.2 Xnee Session file</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Settings">Settings</a></td><td valign="top"><a href="#Settings">7.4.2 Settings</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Shell-scripts-using-Xnee">Shell scripts using Xnee</a></td><td valign="top"><a href="#Shell-scripts-using-Xnee">5.8 Shell scripts using Xnee</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-SIGTERM">SIGTERM</a></td><td valign="top"><a href="#sending-a-SIGTERM-signal">3.9.3 sending a SIGTERM signal</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-SIGTERM-1">SIGTERM</a></td><td valign="top"><a href="#Send-SIGTERM-to-Xnee">3.9.12 Send SIGTERM to Xnee</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Stop-Xnee-with-key">Stop Xnee with key</a></td><td valign="top"><a href="#Stop-Xnee-with-key">5.5.1 Stop Xnee with key</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Stop-Xnee-with-key-combination">Stop Xnee with key combination</a></td><td valign="top"><a href="#Stop-Xnee-with-key-combination">3.9.4 Stop Xnee with key combination</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Synchronisation">Synchronisation</a></td><td valign="top"><a href="#Synchronisation">8.1 Synchronisation</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-U">U</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Using-a-differet-screen-resolution">Using a differet screen resolution</a></td><td valign="top"><a href="#Using-a-differet-screen-resolution">5.7.3 Using a differet screen resolution</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Using-a-offset-when-replaying">Using a offset when replaying</a></td><td valign="top"><a href="#Using-a-offset-when-replaying">5.7.4 Using a offset when replaying</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Using-a-window-position-recall">Using a window position recall</a></td><td valign="top"><a href="#Using-a-window-position-recall">5.7.5 Using a window position recall</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Using-human-readable-printouts">Using human readable printouts</a></td><td valign="top"><a href="#Using-human-readable-printouts">5.7.2 Using human readable printouts</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Using-no-resolution-translation">Using no resolution translation</a></td><td valign="top"><a href="#Using-no-resolution-translation">5.7.6 Using no resolution translation</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Using-verbose-mode">Using verbose mode</a></td><td valign="top"><a href="#Using-verbose-mode">5.7.1 Using verbose mode</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-W">W</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-What-does-the-name-cnee-mean_003f">What does the name cnee mean?</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-What-does-the-name-gnee-mean_003f">What does the name gnee mean?</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-What-does-the-name-gnee-mean_003f-1">What does the name gnee mean?</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-What-does-the-name-gnee-mean_003f-2">What does the name gnee mean?</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-what-numbers-belong-to-X11-data_003f">what numbers belong to X11 data?</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-why-name-it-Xnee">why name it Xnee</a></td><td valign="top"><a href="#FAQ">10. FAQ</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-why-synchronise">why synchronise</a></td><td valign="top"><a href="#Why-synchronise">8.1.1 Why synchronise</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+<tr><th><a name="Index-1_cp_letter-X">X</a></th><td></td><td></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Xnee-Internals">Xnee Internals</a></td><td valign="top"><a href="#Internals">8. Xnee Internals</a></td></tr>
+<tr><td></td><td valign="top"><a href="#index-Xnee-Settings-Arguments">Xnee Settings Arguments</a></td><td valign="top"><a href="#Settings">7.4.2 Settings</a></td></tr>
+<tr><td colspan="3"> <hr></td></tr>
+</table>
+<table><tr><th valign="top">Jump to: &nbsp; </th><td><a href="#Index-1_cp_letter-B" class="summary-letter"><b>B</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-C" class="summary-letter"><b>C</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-D" class="summary-letter"><b>D</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-E" class="summary-letter"><b>E</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-F" class="summary-letter"><b>F</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-G" class="summary-letter"><b>G</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-H" class="summary-letter"><b>H</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-I" class="summary-letter"><b>I</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-K" class="summary-letter"><b>K</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-L" class="summary-letter"><b>L</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-M" class="summary-letter"><b>M</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-P" class="summary-letter"><b>P</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-Q" class="summary-letter"><b>Q</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-R" class="summary-letter"><b>R</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-S" class="summary-letter"><b>S</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-U" class="summary-letter"><b>U</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-W" class="summary-letter"><b>W</b></a>
+ &nbsp; 
+<a href="#Index-1_cp_letter-X" class="summary-letter"><b>X</b></a>
+ &nbsp; 
+</td></tr></table>
+
+
+<hr size="6">
+<a name="SEC_Contents"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h1>Table of Contents</h1>
+<div class="contents">
+
+<ul class="toc">
+  <li><a name="toc-Summary-2" href="#Summary">1. Summary</a>
+  <ul class="toc">
+    <li><a name="toc-Summary-1" href="#Summary-1">1.1 Summary</a></li>
+    <li><a name="toc-Xnee-features" href="#Xnee-features">1.2 Xnee features</a></li>
+    <li><a name="toc-Background" href="#Background">1.3 Background</a></li>
+  </ul></li>
+  <li><a name="toc-Getting-started-2" href="#Getting-started">2. Getting started</a>
+  <ul class="toc">
+    <li><a name="toc-Getting-started-1" href="#Getting-started-1">2.1 Getting started</a>
+    <ul class="toc">
+      <li><a name="toc-Simple-replay" href="#Simple-replay">2.1.1 Simple replay</a></li>
+      <li><a name="toc-Simple-recording-of-Key-presses" href="#Simple-recording-of-Key-presses">2.1.2 Simple recording of Key presses</a></li>
+      <li><a name="toc-Simple-replaying-of-your-recorded-file-1" href="#Simple-replaying-of-your-recorded-file-1">2.1.3 Simple replaying of your recorded file</a></li>
+      <li><a name="toc-Simple-recording-of-mouse-motions" href="#Simple-recording-of-mouse-motions">2.1.4 Simple recording of mouse motions</a></li>
+      <li><a name="toc-Simple-replaying-of-your-recorded-file" href="#Simple-replaying-of-your-recorded-file">2.1.5 Simple replaying of your recorded file</a></li>
+      <li><a name="toc-Simple-retyping-of-a-text-file" href="#Simple-retyping-of-a-text-file">2.1.6 Simple retyping of a text file</a></li>
+      <li><a name="toc-Example-Xnee-Session-files" href="#Example-Xnee-Session-files">2.1.7 Example Xnee Session files</a></li>
+    </ul>
+</li>
+  </ul></li>
+  <li><a name="toc-Functional-overview-2" href="#Functional-overview">3. Functional overview</a>
+  <ul class="toc">
+    <li><a name="toc-Functional-overview-1" href="#Functional-overview-1">3.1 Functional overview</a></li>
+    <li><a name="toc-Modes" href="#Modes">3.2 Modes</a>
+    <ul class="toc">
+      <li><a name="toc-Record" href="#Record">3.2.1 Record</a></li>
+      <li><a name="toc-Replay" href="#Replay">3.2.2 Replay</a></li>
+      <li><a name="toc-Retype" href="#Retype">3.2.3 Retype</a></li>
+      <li><a name="toc-Distribution" href="#Distribution">3.2.4 Distribution</a></li>
+    </ul></li>
+    <li><a name="toc-Ranges" href="#Ranges">3.3 Ranges</a></li>
+    <li><a name="toc-First-and-last-motion-event" href="#First-and-last-motion-event">3.4 First and last motion event</a></li>
+    <li><a name="toc-Delay" href="#Delay">3.5 Delay</a></li>
+    <li><a name="toc-Verbose" href="#Verbose">3.6 Verbose</a></li>
+    <li><a name="toc-Human-printouts" href="#Human-printouts">3.7 Human printouts</a></li>
+    <li><a name="toc-Invoking-Xnee" href="#Invoking-Xnee">3.8 Invoking Xnee</a>
+    <ul class="toc">
+      <li><a name="toc-Command-line-syntax" href="#Command-line-syntax">3.8.1 Command line syntax</a></li>
+      <li><a name="toc-Project-file-1" href="#Project-file-1">3.8.2 Project file</a></li>
+      <li><a name="toc-Session-file" href="#Session-file">3.8.3 Session file</a></li>
+    </ul></li>
+    <li><a name="toc-Interupting-Xnee" href="#Interupting-Xnee">3.9 Interupting Xnee</a>
+    <ul class="toc">
+      <li><a name="toc-modifier-and-key" href="#modifier-and-key">3.9.1 modifier and key</a></li>
+      <li><a name="toc-limit-the-number-of-data-to-record" href="#limit-the-number-of-data-to-record">3.9.2 limit the number of data to record</a></li>
+      <li><a name="toc-sending-a-SIGTERM-signal" href="#sending-a-SIGTERM-signal">3.9.3 sending a SIGTERM signal</a></li>
+      <li><a name="toc-Stop-Xnee-with-key-combination" href="#Stop-Xnee-with-key-combination">3.9.4 Stop Xnee with key combination</a></li>
+      <li><a name="toc-Pause-Xnee-with-key-combination" href="#Pause-Xnee-with-key-combination">3.9.5 Pause Xnee with key combination</a></li>
+      <li><a name="toc-Pause-Xnee-with-key-combination-1" href="#Pause-Xnee-with-key-combination-1">3.9.6 Pause Xnee with key combination</a></li>
+      <li><a name="toc-Insert-marks-Xnee-with-key-combination" href="#Insert-marks-Xnee-with-key-combination">3.9.7 Insert marks Xnee with key combination</a></li>
+      <li><a name="toc-Limit-number-of-data-to-record" href="#Limit-number-of-data-to-record">3.9.8 Limit number of data to record</a></li>
+      <li><a name="toc-Limit-the-events-to-record" href="#Limit-the-events-to-record">3.9.9 Limit the events to record</a></li>
+      <li><a name="toc-Limit-the-data-to-record" href="#Limit-the-data-to-record">3.9.10 Limit the data to record</a></li>
+      <li><a name="toc-Limit-the-time-to-record" href="#Limit-the-time-to-record">3.9.11 Limit the time to record</a></li>
+      <li><a name="toc-Send-SIGTERM-to-Xnee" href="#Send-SIGTERM-to-Xnee">3.9.12 Send SIGTERM to Xnee</a></li>
+    </ul></li>
+    <li><a name="toc-Xnee-plugins" href="#Xnee-plugins">3.10 Xnee plugins</a></li>
+  </ul></li>
+  <li><a name="toc-Installation-1" href="#Installation">4. Installation</a>
+  <ul class="toc">
+    <li><a name="toc-Installation-from-source-with-the-configure-script" href="#Installation-from-source-with-the-configure-script">4.1 Installation from source with the configure script</a></li>
+    <li><a name="toc-Installation-from-source-with-default-Makefile" href="#Installation-from-source-with-default-Makefile">4.2 Installation from source with default Makefile</a></li>
+    <li><a name="toc-Installation-from-CVS" href="#Installation-from-CVS">4.3 Installation from CVS</a></li>
+  </ul></li>
+  <li><a name="toc-Examples-1" href="#Examples">5. Examples</a>
+  <ul class="toc">
+    <li><a name="toc-Recorder" href="#Recorder">5.1 Recorder</a>
+    <ul class="toc">
+      <li><a name="toc-Record-mouse-motions" href="#Record-mouse-motions">5.1.1 Record mouse motions</a></li>
+      <li><a name="toc-Record-keyboard" href="#Record-keyboard">5.1.2 Record keyboard</a></li>
+      <li><a name="toc-Record-keyboard-and-mouse" href="#Record-keyboard-and-mouse">5.1.3 Record keyboard and mouse</a></li>
+      <li><a name="toc-Record-a-gnumeric-session" href="#Record-a-gnumeric-session">5.1.4 Record a gnumeric session</a></li>
+      <li><a name="toc-Record-a-gnumeric-session-with-synchronisation-data" href="#Record-a-gnumeric-session-with-synchronisation-data">5.1.5 Record a gnumeric session with synchronisation data</a></li>
+    </ul></li>
+    <li><a name="toc-Replayer" href="#Replayer">5.2 Replayer</a>
+    <ul class="toc">
+      <li><a name="toc-Replay-mouse-motions" href="#Replay-mouse-motions">5.2.1 Replay mouse motions</a></li>
+      <li><a name="toc-Replay-mouse-motions-using-with-half-speed" href="#Replay-mouse-motions-using-with-half-speed">5.2.2 Replay mouse motions using with half speed</a></li>
+      <li><a name="toc-Replay-mouse-motions-using-with-double-speed" href="#Replay-mouse-motions-using-with-double-speed">5.2.3 Replay mouse motions using with double speed</a></li>
+      <li><a name="toc-Replay-keyboard-actions" href="#Replay-keyboard-actions">5.2.4 Replay keyboard actions</a></li>
+      <li><a name="toc-Replay-keyboard-and-mouse" href="#Replay-keyboard-and-mouse">5.2.5 Replay keyboard and mouse</a></li>
+      <li><a name="toc-Replay-a-gnumeric-session" href="#Replay-a-gnumeric-session">5.2.6 Replay a gnumeric session</a></li>
+      <li><a name="toc-Replay-a-gnumeric-session-with-synchronisation-data" href="#Replay-a-gnumeric-session-with-synchronisation-data">5.2.7 Replay a gnumeric session with synchronisation data</a></li>
+      <li><a name="toc-Replay-a-gnumeric-session-with-synchronisation-data-setting-threshold" href="#Replay-a-gnumeric-session-with-synchronisation-data-setting-threshold">5.2.8 Replay a gnumeric session with synchronisation data setting threshold</a></li>
+    </ul></li>
+    <li><a name="toc-Retyper" href="#Retyper">5.3 Retyper</a>
+    <ul class="toc">
+      <li><a name="toc-Retype-the-help-printout" href="#Retype-the-help-printout">5.3.1 Retype the help printout</a></li>
+      <li><a name="toc-Retype-a-file" href="#Retype-a-file">5.3.2 Retype a file</a></li>
+    </ul></li>
+    <li><a name="toc-Distributor" href="#Distributor">5.4 Distributor</a>
+    <ul class="toc">
+      <li><a name="toc-Distribute-your-mouse-motions" href="#Distribute-your-mouse-motions">5.4.1 Distribute your mouse motions</a></li>
+      <li><a name="toc-Distribute-the-replaying-of-mouse-motions" href="#Distribute-the-replaying-of-mouse-motions">5.4.2 Distribute the replaying of mouse motions</a></li>
+      <li><a name="toc-Distribute-the-retyping-of-a-file" href="#Distribute-the-retyping-of-a-file">5.4.3 Distribute the retyping of a file</a></li>
+    </ul></li>
+    <li><a name="toc-Key" href="#Key">5.5 Key</a>
+    <ul class="toc">
+      <li><a name="toc-Stop-Xnee-with-key" href="#Stop-Xnee-with-key">5.5.1 Stop Xnee with key</a></li>
+      <li><a name="toc-Pausing-and-resuming-Xnee-with-key" href="#Pausing-and-resuming-Xnee-with-key">5.5.2 Pausing and resuming Xnee with key</a></li>
+    </ul></li>
+    <li><a name="toc-Using-macro" href="#Using-macro">5.6 Using macro</a>
+    <ul class="toc">
+      <li><a name="toc-Define-a-simple-macro" href="#Define-a-simple-macro">5.6.1 Define a simple macro</a></li>
+      <li><a name="toc-Define-another-simple-macro" href="#Define-another-simple-macro">5.6.2 Define another simple macro</a></li>
+    </ul></li>
+    <li><a name="toc-Various-options" href="#Various-options">5.7 Various options</a>
+    <ul class="toc">
+      <li><a name="toc-Using-verbose-mode" href="#Using-verbose-mode">5.7.1 Using verbose mode</a></li>
+      <li><a name="toc-Using-human-readable-printouts" href="#Using-human-readable-printouts">5.7.2 Using human readable printouts</a></li>
+      <li><a name="toc-Using-a-differet-screen-resolution" href="#Using-a-differet-screen-resolution">5.7.3 Using a differet screen resolution</a></li>
+      <li><a name="toc-Using-a-offset-when-replaying" href="#Using-a-offset-when-replaying">5.7.4 Using a offset when replaying</a></li>
+      <li><a name="toc-Using-a-window-position-recall" href="#Using-a-window-position-recall">5.7.5 Using a window position recall</a></li>
+      <li><a name="toc-Using-no-resolution-translation" href="#Using-no-resolution-translation">5.7.6 Using no resolution translation</a></li>
+      <li><a name="toc-Record-another-display-than-the-default" href="#Record-another-display-than-the-default">5.7.7 Record another display than the default</a></li>
+      <li><a name="toc-Replay-to-another-display-than-the-default" href="#Replay-to-another-display-than-the-default">5.7.8 Replay to another display than the default</a></li>
+    </ul></li>
+    <li><a name="toc-Shell-scripts-using-Xnee" href="#Shell-scripts-using-Xnee">5.8 Shell scripts using Xnee</a></li>
+  </ul></li>
+  <li><a name="toc-Xnee-Programs" href="#Programs">6. Xnee Programs</a>
+  <ul class="toc">
+    <li><a name="toc-cnee-_002d-cnee_0027s-not-an-event-emulator" href="#cnee-_002d-cnee_0027s-not-an-event-emulator">6.1 cnee - cnee&rsquo;s not an event emulator</a></li>
+    <li><a name="toc-gnee-_002d-gnee_0027s-not-an-emulator-either" href="#gnee-_002d-gnee_0027s-not-an-emulator-either">6.2 gnee - gnee&rsquo;s not an emulator either</a></li>
+    <li><a name="toc-pnee-_002d-pnee_0027s-not-even-emulating" href="#pnee-_002d-pnee_0027s-not-even-emulating">6.3 pnee - pnee&rsquo;s not even emulating</a>
+    <ul class="toc">
+      <li><a name="toc-Reporting-pnee-bugs" href="#Reporting-pnee-bugs">6.3.1 Reporting pnee bugs</a></li>
+    </ul>
+</li>
+  </ul></li>
+  <li><a name="toc-File-types-and-format" href="#File-format">7. File types and format</a>
+  <ul class="toc">
+    <li><a name="toc-Project-file" href="#Project-file">7.1 Project file</a>
+    <ul class="toc">
+      <li><a name="toc-Create-a-project-file" href="#Create-a-project-file">7.1.1 Create a project file</a></li>
+    </ul></li>
+    <li><a name="toc-Xnee-Session-file" href="#Xnee-Session-file">7.2 Xnee Session file</a></li>
+    <li><a name="toc-Xnee-file-format" href="#Xnee-file-format">7.3 Xnee file format</a></li>
+    <li><a name="toc-Xnee-directives" href="#Xnee-directives">7.4 Xnee directives</a>
+    <ul class="toc">
+      <li><a name="toc-Comment" href="#Comment">7.4.1 Comment</a></li>
+      <li><a name="toc-Settings" href="#Settings">7.4.2 Settings</a></li>
+      <li><a name="toc-Replay-1" href="#Replay-1">7.4.3 Replay</a></li>
+      <li><a name="toc-Script-replay-data" href="#Script-replay-data">7.4.4 Script replay data</a></li>
+      <li><a name="toc-Mark" href="#Mark">7.4.5 Mark</a></li>
+      <li><a name="toc-Exec" href="#Exec">7.4.6 Exec</a></li>
+      <li><a name="toc-Project-information" href="#Project-information">7.4.7 Project information</a></li>
+    </ul>
+</li>
+  </ul></li>
+  <li><a name="toc-Xnee-Internals" href="#Internals">8. Xnee Internals</a>
+  <ul class="toc">
+    <li><a name="toc-Synchronisation" href="#Synchronisation">8.1 Synchronisation</a>
+    <ul class="toc">
+      <li><a name="toc-Why-synchronise" href="#Why-synchronise">8.1.1 Why synchronise</a></li>
+      <li><a name="toc-How-to-synchronise" href="#How-to-synchronise">8.1.2 How to synchronise</a></li>
+      <li><a name="toc-Synchronisation-is-needed" href="#Synchronisation-is-needed">8.1.3 Synchronisation is needed</a></li>
+      <li><a name="toc-Different-data-for-different-kind-of-sessions" href="#Different-data-for-different-kind-of-sessions">8.1.4 Different data for different kind of sessions</a></li>
+      <li><a name="toc-Slow-replay-session-due-to-too-many-synchronise-data" href="#Slow-replay-session-due-to-too-many-synchronise-data">8.1.5 Slow replay session due to too many synchronise data</a></li>
+      <li><a name="toc-X-protocol-is-rich-and-asynchronous" href="#X-protocol-is-rich-and-asynchronous">8.1.6 X protocol is rich and asynchronous</a></li>
+      <li><a name="toc-Different-data-sent" href="#Different-data-sent">8.1.7 Different data sent</a></li>
+      <li><a name="toc-Buffers-and-timeouts" href="#Buffers-and-timeouts">8.1.8 Buffers and timeouts</a></li>
+    </ul>
+</li>
+  </ul></li>
+  <li><a name="toc-Xnee-Requirements" href="#Requirements">9. Xnee Requirements</a>
+  <ul class="toc">
+    <li><a name="toc-Runtime-requirements" href="#Runtime-requirements">9.1 Runtime requirements</a></li>
+    <li><a name="toc-Development-requirements" href="#Development-requirements">9.2 Development requirements</a></li>
+  </ul></li>
+  <li><a name="toc-FAQ-1" href="#FAQ">10. FAQ</a></li>
+  <li><a name="toc-Copying-This-Manual-1" href="#Copying-This-Manual">A. Copying This Manual</a>
+  <ul class="toc">
+    <li><a name="toc-GNU-Free-Documentation-License" href="#GNU-Free-Documentation-License">A.1 GNU Free Documentation License</a></li>
+  </ul></li>
+  <li><a name="toc-Index-1" href="#Index">B. Index</a></li>
+</ul>
+</div>
+<hr size="1">
+<a name="SEC_Overview"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h1>Short Table of Contents</h1>
+<div class="shortcontents">
+<ul class="toc">
+<li><a name="stoc-Summary-2" href="#Summary">1. Summary</a></li>
+<li><a name="stoc-Getting-started-2" href="#Getting-started">2. Getting started</a></li>
+<li><a name="stoc-Functional-overview-2" href="#Functional-overview">3. Functional overview</a></li>
+<li><a name="stoc-Installation-1" href="#Installation">4. Installation</a></li>
+<li><a name="stoc-Examples-1" href="#Examples">5. Examples</a></li>
+<li><a name="stoc-Xnee-Programs" href="#Programs">6. Xnee Programs</a></li>
+<li><a name="stoc-File-types-and-format" href="#File-format">7. File types and format</a></li>
+<li><a name="stoc-Xnee-Internals" href="#Internals">8. Xnee Internals</a></li>
+<li><a name="stoc-Xnee-Requirements" href="#Requirements">9. Xnee Requirements</a></li>
+<li><a name="stoc-FAQ-1" href="#FAQ">10. FAQ</a></li>
+<li><a name="stoc-Copying-This-Manual-1" href="#Copying-This-Manual">A. Copying This Manual</a></li>
+<li><a name="stoc-Index-1" href="#Index">B. Index</a></li>
+</ul>
+</div>
+<hr size="1">
+<a name="SEC_About"></a>
+<table cellpadding="1" cellspacing="1" border="0">
+<tr><td valign="middle" align="left">[<a href="#Top" title="Cover (top) of document">Top</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>
+<td valign="middle" align="left">[<a href="#Index" title="Index">Index</a>]</td>
+<td valign="middle" align="left">[<a href="#SEC_About" title="About (help)"> ? </a>]</td>
+</tr></table>
+<h1>About This Document</h1>
+<p>
+  This document was generated by <em>Henrik Sandklef</em> on <em>December 24, 2009</em> using <a href="http://www.nongnu.org/texi2html/"><em>texi2html 1.82</em></a>.
+</p>
+<p>
+  The buttons in the navigation panels have the following meaning:
+</p>
+<table border="1">
+  <tr>
+    <th> Button </th>
+    <th> Name </th>
+    <th> Go to </th>
+    <th> From 1.2.3 go to</th>
+  </tr>
+  <tr>
+    <td align="center"> [ &lt; ] </td>
+    <td align="center">Back</td>
+    <td>Previous section in reading order</td>
+    <td>1.2.2</td>
+  </tr>
+  <tr>
+    <td align="center"> [ &gt; ] </td>
+    <td align="center">Forward</td>
+    <td>Next section in reading order</td>
+    <td>1.2.4</td>
+  </tr>
+  <tr>
+    <td align="center"> [ &lt;&lt; ] </td>
+    <td align="center">FastBack</td>
+    <td>Beginning of this chapter or previous chapter</td>
+    <td>1</td>
+  </tr>
+  <tr>
+    <td align="center"> [ Up ] </td>
+    <td align="center">Up</td>
+    <td>Up section</td>
+    <td>1.2</td>
+  </tr>
+  <tr>
+    <td align="center"> [ &gt;&gt; ] </td>
+    <td align="center">FastForward</td>
+    <td>Next chapter</td>
+    <td>2</td>
+  </tr>
+  <tr>
+    <td align="center"> [Top] </td>
+    <td align="center">Top</td>
+    <td>Cover (top) of document</td>
+    <td> &nbsp; </td>
+  </tr>
+  <tr>
+    <td align="center"> [Contents] </td>
+    <td align="center">Contents</td>
+    <td>Table of contents</td>
+    <td> &nbsp; </td>
+  </tr>
+  <tr>
+    <td align="center"> [Index] </td>
+    <td align="center">Index</td>
+    <td>Index</td>
+    <td> &nbsp; </td>
+  </tr>
+  <tr>
+    <td align="center"> [ ? ] </td>
+    <td align="center">About</td>
+    <td>About (help)</td>
+    <td> &nbsp; </td>
+  </tr>
+</table>
+
+<p>
+  where the <strong> Example </strong> assumes that the current position is at <strong> Subsubsection One-Two-Three </strong> of a document of the following structure:
+</p>
+
+<ul>
+  <li> 1. Section One
+    <ul>
+      <li>1.1 Subsection One-One
+        <ul>
+          <li>...</li>
+        </ul>
+      </li>
+      <li>1.2 Subsection One-Two
+        <ul>
+          <li>1.2.1 Subsubsection One-Two-One</li>
+          <li>1.2.2 Subsubsection One-Two-Two</li>
+          <li>1.2.3 Subsubsection One-Two-Three &nbsp; &nbsp;
+            <strong>&lt;== Current Position </strong></li>
+          <li>1.2.4 Subsubsection One-Two-Four</li>
+        </ul>
+      </li>
+      <li>1.3 Subsection One-Three
+        <ul>
+          <li>...</li>
+        </ul>
+      </li>
+      <li>1.4 Subsection One-Four</li>
+    </ul>
+  </li>
+</ul>
+
+<hr size="1">
+<p>
+ <font size="-1">
+  This document was generated by <em>Henrik Sandklef</em> on <em>December 24, 2009</em> using <a href="http://www.nongnu.org/texi2html/"><em>texi2html 1.82</em></a>.
+ </font>
+ <br>
+
+</p>
+</body>
+</html>

--- /dev/null
+++ b/original/xnee.info
@@ -0,0 +1,2311 @@
+This is xnee.info, produced by makeinfo version 4.13 from xnee.texi.
+
+INFO-DIR-SECTION Miscellaneous
+START-INFO-DIR-ENTRY
+ * : (Xnee).        Xnee's Not Event Emulator.
+END-INFO-DIR-ENTRY
+
+
+File: xnee.info,  Node: Top,  Next: Summary,  Prev: (dir),  Up: (dir)
+
+Xnee Manual
+***********
+
+* Menu:
+
+* Summary::              Summary.
+* Getting started::      Getting started
+* Functional overview::  Functional overview
+* Installation::         Installation
+* Examples::             examples
+* File format::          File format
+* Programs::             Programs
+* Internals::            Internals
+* Requirements::         Requirements
+* FAQ::                  FAQ
+* Copying This Manual::  Copying This Manual
+* Index::                Index
+
+
+File: xnee.info,  Node: Summary,  Next: Getting started,  Prev: Top,  Up: Top
+
+1 Summary
+*********
+
+1.1 Summary
+===========
+
+Xnee is a suite of programs that can record, replay and   distribute
+user actions under the X11 environment.    Think of it as a robot that
+can imitate the job you just   did.
+
+   Xnee consists of one library and two applications
+
+   cnee - command line program
+
+   gnee - graphical user interface program
+
+   pnee - a Gnome Panel Applet
+
+   libxnee - library used by xnee and gnee
+
+1.2 Xnee features
+=================
+
+Xnee can be used for multiple purposes, allthough it was initially
+designed as a test tool. The most used features are the foloowing:
+
+   Test tool -         Instead of performing test cases for a GUI (or
+CLI program)         over and over again, the test cases can be
+automated. Simply record         a user session and replay it later.
+
+   Performance test tool - 	If you want to simulate lots of
+simultaneous users in a network (or 	a local machine) you can use
+Xnee. Simply record a user 	session and start multiple instances of
+Xnee.
+
+   Demonstration tool - 	You can use Xnee to demonstrate the
+features of your program. Simply 	record a user session and
+replay it later.
+
+   Distribution tool - 	If you want to send over your mouse/keyboard
+actions to another display 	you can use the built-in distribution
+mechanism in Xnee.
+
+   Macro recorder/replayer - 	By binding a key and modifier
+combination (e.g using xrebind)   to replay a recorded session you will
+have a Window Manager and   application independent macro.
+
+   File retyper -    Xnee can retype the contents of a file. This can
+be useful    during tests or if you want xnee to answer some command
+session without having to record the session.
+
+   X11 protocol sniffer -    Xnee can be used a sniffer for the X11
+protocol.
+
+1.3 Background
+==============
+
+In order to verify that a program does the job it's supposed to do,
+certain tests have to be made.  These tests are, IMHO, perhaps the most
+boring things a programmer can do. Xnee is designed to reduce the
+programmer from this burden.
+Xnee started out as a commad line program. During the development phase
+the main functionality was broken out to a library, called libxnee. The
+command line program was renamed cnee. The thought behind making the
+library was to enable the writing of other clients than just the
+command line. Today there is a GUI program, gnee, and a Gnome panel
+applet, pnee, that uses the library.
+By using xnee your testcase(s) can be recorded and later on replayed.
+Xnee comes with other features For more information about these, read
+the Introduction.
+
+   This manual mainly focuses on the command line program, cnee. There
+are however a seperate chapters for the other programs.
+
+
+File: xnee.info,  Node: Getting started,  Next: Functional overview,  Prev: Summary,  Up: Top
+
+2 Getting started
+*****************
+
+2.1 Getting started
+===================
+
+To get the first feel of Xnee some simple examples are presented.
+
+2.1.1 Simple replay
+-------------------
+
+Start a terminal emulator (e.g xterm) and then start Xnee,
+        `cnee --replay --file example1.xnr &'
+   ....dont forget '&'.  The file example1.xnr contains keyboard events
+recorded during development of this manual. When replayed you'll see
+what was typed and of course more important you'll get i first glimpse
+of Xnee and its capabilities.  For information on where to find the
+example files, see below.
+
+2.1.2 Simple recording of Key presses
+-------------------------------------
+
+We move on to a (very) simple recording session.  Start a terminal
+emulator (e.g xterm) and your favorite editor.  Move the pointer to one
+of the terminal windows and start Xnee.
+        `cnee --record -o example2.xnr --device-event-range 2-3 \'
+        `--time 5 --events-to-record 20'
+   Move the pointer to the editor and get focus (e.g click the window
+frame). After 5 seconds you can type whatever you want to record (20
+press- and relase events of the keyboard are recorded). We are done and
+you have recorded your first session! Leave the desktop as it is and go
+forward to the next example.
+
+2.1.3 Simple replaying of your recorded file
+--------------------------------------------
+
+Start one terminal emulator (e.g xterm).  Let Xnee repeat the stuff you
+did in the example above.  Undo all changes in the editor that was made
+in the previous example.  Move the pointer to one of the terminal
+windows and start Xnee.
+        `cnee --replay -f example2.xnr --time 5'
+   Move the pointer to the editor and get focus (e.g click the window
+frame). After 5 seconds you will see your typings in the example above
+being repeated.
+
+2.1.4 Simple recording of mouse motions
+---------------------------------------
+
+We move on to another simple recording session.  Start a terminal
+emulator (e.g xterm).  Move the pointer to the terminal window and
+start Xnee.
+        `cnee --record -o example3.xnr --device-event-range 5-6 \'
+        `--time 5 --events-to-record 20'
+   After 5 seconds you can move the pointer around (20 motion events
+are recorded).
+
+2.1.5 Simple replaying of your recorded file
+--------------------------------------------
+
+Let Xnee repeat the stuff you did in the example above..  Move the
+pointer to the terminal window and start Xnee.
+        `cnee --replay -f example3.xnr --time 5'
+   After 5 seconds you will see your mouse motions in the example above
+being repplayed.
+
+2.1.6 Simple retyping of a text file
+------------------------------------
+
+Let Xnee retype (type again) the text in a text file.  Move the pointer
+to the terminal window and create a text file containing the command
+`ls -l'.
+        `echo "ls -l" > ./mytext.txt'
+   And after that you start Xnee.
+        `cnee --retype-file  ./mytext.txt --time 5'
+   After 5 seconds you will see Xnee type `ls -l', which probably will
+list the files in the current directory.
+
+2.1.7 Example Xnee Session files
+--------------------------------
+
+The example file above (example1.xnr) is a session file that has been
+delivered with the sources (allthough not installed), rpm and with the
+Xnee Documentation Package. The file(s) can be found:
+                       Distribution           Location
+                       RPM                    /usr/lib/xnee/session
+                       Source                 ./sessions/
+                       Document Package       ./sessions/
+
+
+File: xnee.info,  Node: Functional overview,  Next: Installation,  Prev: Getting started,  Up: Top
+
+3 Functional overview
+*********************
+
+3.1 Functional overview
+=======================
+
+The Xnee applications (gnee and xnee) receives X11 protocol data (e.g.
+events) from an X server (using libxnee) and print them to a file,
+called Xnee Session File. Theses events are later read from the session
+file and replayed.  Gnee and xnee can read its settings from a file,
+called Xnee Project File, or from command line (cnee) or via the GUI
+(gnee).
+
+Events directly generated by the user (e.g KeyPress) can be replayed or
+faked. Requests, replies, errors and events not directly generated by
+the user (e.g MapNotify) can be recorded as well. By using these data
+Xnee can replay with synchronisation.
+
+   In this section you will be given information about key concepts in
+X11 and Xnee. It is
 vital that you read through this chapter. 
 
+
+3.2 Modes
+=========
+
+Xnee has four modes:
+   * record 
+
+   * replay
+
+   * retype
+
+   * distribute
+   The distribution mechanism can be used together with the other
+three.
 
+
+3.2.1 Record
+------------
+
+When record mode is used Xnee receives a copy of the data sent to and
+from the 
 X server. The copy is printed to a file. Xnee can record
+the whole X11 
 protocol, not just mouse and keyboard events.
 
 
+
+
+3.2.2 Replay
+------------
+
+When replay mode is used Xnee reads data from a file or stdin. These
+data is 
 either sent to the server (if it is a keyboard or a mouse
+event) or used to 
 synchronise with (if any of the other data). 
 
+
 
+
+3.2.3 Retype
+------------
+
+Xnee can retype the contents of a text file. This is useful when
+combining 
 replaying of different recorded session. You can change
+the text written in
 for example an editor (e.g emacs) without having
+to re-record the complete
 sessions. 
 
+
+3.2.4 Distribution
+------------------
+
+Xnee can fake mouse and keyboard events on multiple displays. This 
+distribution mechanism can be used when recording, replaying or
+retyping.
 
 
+
+3.3 Ranges
+==========
+
+What data to record is specified using ranges. Ranges has a start value
+and 
 a stop value. The following data can be recorded: 
 
+        Xnee name                        X Protocol Name
+        core-requests                    Request
+        device-event                     Event
+        delivered-event                  Event
+        error                            Error
+        reply                            Reply
+        ext-requests.ext-major           Extension Request
+        ext-requests.ext-minor           Extension Request
+        ext-replies.ext-major            Extension Reply
+        ext-replies.ext-minor            Extension Reply
+   When specifying the ranges when using xnee you can either type the
+integer value 
 of the data or the name of the data. To find out what
+number belongs to what 
 data name, you can use the
+`--print-data-name' option. For an explanation 
 of the X protocol
+data, please read the "X Record Extension Library" or the 
 "Record
+Extension Protocol Specification".
 
 
+
+3.4 First and last motion event
+===============================
+
+Xnee has the ability to skip recording of succesive motion events with
+no 
 other data in between. This option is intended to reduce the
+number of data 
 recorded by leaving out unnecessary data. This
+feature can be invoked with 
 the `--first-last' flag.
 
+
+3.5 Delay
+=========
+
+Sometimes when Xnee starts recording data, the keyrelease (caused by
+pressing and 
 releasing RETURN to execute the Xnee command line) is
+recorded. This single 
 keyrelease (with no corresponding keypress)
+might confuse the X server. 
 With the `--time <secs>' option Xnee can
+be paused for a number of seconds 
 before
+recording/replaying/retyping starts.
 
 
+
+3.6 Verbose
+===========
+
+When enabling verbose mode (`--verbose') Xnee prints a lot of
+information 
 about it's state. This option is only intended for
+runtime debugging.
 
+
+3.7 Human printouts
+===================
+
+Sometimes it's hard to decide what data to use when synchronising. To
+do this 
 you have to analyse what data is sent from the server when
+recording. Instead of 
 reading the data number, s tring
+representation of the data is printed out. 
 To enable this option,
+use the `--human-printouts'.
 
 
 
+
+3.8 Invoking Xnee
+=================
+
+
+
+3.8.1 Command line syntax
+-------------------------
+
+To get information about how to use Xnee's command line options please
+use the man page(s).
 
+
+3.8.2 Project file
+------------------
+
+To use a Project file use the `--project' option,  e.g `cnee --project
+xnee/projects/netscape.xns'
 
+
+3.8.3 Session file
+------------------
+
+To use a session file use the `--file' option,  e.g 
 `cnee --file
+user1_session.xns'
 
 
+
+3.9 Interupting Xnee
+====================
+
+Interupting Xnee when recording or replaying can be done as follows
+   * user specified modifier and key
+
+   * limit the number of data to record
+
+   * sending a SIGTERM signal (e.g pressing Control-c in a terminal
+     window)
+   The prefered way to interrupt xnee is to use the modifier+key. 
 
+
+3.9.1 modifier and key
+----------------------
+
+It is possible to specify a modifier (e.g Control button) and a key
+(e.g 'a') 
 that will stop the Xnee session. When using this option
+make sure that the
 modifier/key is not used in any way by the
+applications you are recording. 
 You can specify a key+modifier to
+stop, pause and resume xnee. You can also 
 insert a mark in the
+recorded session file. 
 
+
+3.9.2 limit the number of data to record
+----------------------------------------
+
+By specifying the number of data to record (`--loops') xnee stops when
+this number 
 of data is received from the server. When replaying the
+same amount of data 
 is replayed. 
 
+
+3.9.3 sending a SIGTERM signal
+------------------------------
+
+The easiest way to send a signal to a process is by launching Xnee
+from a terminal window (e.g xterm) and then press Control-c which will
+send the SIGTERM signal to Xnee. When replaying it can sometimes be
+hard to move the pointer into the terminal window (e.g if a lot of
+motion events were recorded that will let you compete with Xnee on
+where the mouse pointer shall be located.  Beleive me, you'll end up
+lossing that battle).
 
 When using Control-c to stop Xnee you must
+be aware of that the pressing of the Control key gets recorded. When
+replaying a recorded session ending with pressing of Control your apps
+may think you are pressing the Control key. A simple solution for this
+is to press and release the Control.
 
+
+3.9.4 Stop Xnee with key combination
+------------------------------------
+
+Xnee stops its current action when the user presses the key
+combination as specified during setup. Xnee will be shut gracefully.
+
+
+3.9.5 Pause Xnee with key combination
+-------------------------------------
+
+Xnee pause its current action when the user presses the key
+combination as specified during setup. Xnee will be in paused mode
+until
 the user stops or resumes Xnee.
 
+
+3.9.6 Pause Xnee with key combination
+-------------------------------------
+
+Xnee resumes its current paused action when the user presses the key
+combination as specified during setup. Xnee will continue where it was
+paused.
 
+
+3.9.7 Insert marks Xnee with key combination
+--------------------------------------------
+
+When the user presses the key combination as specified during setup 
+Xnee will print a mark in the session file containing a time stamp.
+This 
 feature is intended be used when you want to mark an
+interresting time/event 
 during recording. After recording has
+finished you can add Xnee scripting 
 calls to Xnee which will be
+interpreted and executed as if they were recorded.
 
 
+
+3.9.8 Limit number of data to record
+------------------------------------
+
+There a a few ways to limit the number of data Xnee records.
+   * limit the events to recored
+
+   * limit the data to recored
+
+   * limit the time to recored
+
+   * send a signal to xnee (SIGTERM)
+
+   * use a selfmade record callback function
+   
+
+3.9.9 Limit the events to record
+--------------------------------
+
+When having received the specified amount of events from the server,
+Xnee 
 stops the recording. For more information on how to use this
+option, read
 the man page for cnee or the user manual for gnee.
 
+
+3.9.10 Limit the data to record
+-------------------------------
+
+When having received the specified amount of data from the server, Xnee
+
 stops the recording. For more information on how to use this option,
+read
 the man page for cnee or the user manual for gnee.
 
+
+3.9.11 Limit the time to record
+-------------------------------
+
+When having recorded for the specified amount of time from the server,
+Xnee 
 stops the recording. For more information on how to use this
+option, read
 the man page for cnee or the user manual for gnee.
 
+
+3.9.12 Send SIGTERM to Xnee
+---------------------------
+
+The easiest way to send a signal to a process is by launching Xnee from
+a 
 terminal window (e.g xterm). By pressing Control-c xterm sends the
+
 SIGTERM signal to Xnee. When replaying it can sometimes be hard to 
+move the pointer into the terminal window (e.g if a lot of motion 
+events were recorded that will let you compete with Xnee on where 
+the mouse pointer shall be located. Beleive me, you'll end up lossing 
+that battle).  
 
 
+
+3.10 Xnee plugins
+=================
+
+Xnee supports plugins since version 1.07. For information about how to
+write 
 plugins, download the source code and look at the plugin
+example which is 
 delivered with Xnee.
 
+
+
+File: xnee.info,  Node: Installation,  Next: Examples,  Prev: Functional overview,  Up: Top
+
+4 Installation
+**************
+
+4.1 Installation from source with the configure script
+======================================================
+
+To build and install Xnee do the following: Download the following
+source files into a directory (version numbers given here are just
+examples)
+   * xnee-3.02.tar.gz
+
+Unzip the source file
+     `gunzip xnee-3.02.tar.gz'
+
+Untar the source file
+     `tar xvf xnee-3.02.tar'
+
+Enter the Xnee directory
+     `cd xnee-3.02'
+
+Generate the makefiles
+     `./configure'
+
+or if you want to specify which directory to install xnee to
+     `./configure --prefix=<PATH TO INSTALLATION DIR>'
+
+Build Xnee
+     `make clean all'
+
+Install (as root) if you want libxnee to be installed. If not, skip the
+following command. Installation of libxnee is not needed to build cnee
+and gnee.
+     `make install'
+
+4.2 Installation from source with default Makefile
+==================================================
+
+To unpack, build and install Xnee from the sourcefiles do the following:
+Download the source files into a directory
+
+   Unzip the source file
+     `gunzip xnee-3.02.tar.gz'
+
+   Untar the source file
+     `tar xvf xnee-3.02.tar'
+
+   Enter the Xnee directory
+     `cd xnee-3.02'
+
+   Build Xnee
+     `make -f Makefile.xnee clean all'
+
+   Copy the Xnee binary (xnee/src/xnee) to a directory
+     `cp xnee/src/xnee /usr/local/bin'
+
+4.3 Installation from CVS
+=========================
+
+Download the xnee source code from the CVS repository at
+`http://savannah.gnu.org'. Instructions on how to do this can be found
+there as well.
+
+Build Xnee
+     `cd xnee'
+     `make -f Makefile.cvs'
+     `./configure --enable-doc'
+     `make'
+     `make install' (optional)
+
+   Build Xnee Documentation
+     `cd doc'
+     `make manual'
+     `make install' (as root)
+     `cd ..'
+
+
+File: xnee.info,  Node: Examples,  Next: Programs,  Prev: Installation,  Up: Top
+
+5 Examples
+**********
+
+5.1 Recorder
+============
+
+5.1.1 Record mouse motions
+--------------------------
+
+Record mouse motions only and save the session to mouse-rec.xnl.
+        `cnee --record --mouse --out-file mouse-rec.xnl'
+   After having typed this you can move your mouse round for a while.
+After Xnee has exited you will be able to replay your motions. Xnee
+will stop after having record 100 events (this is the default
+behaviour).
+
+5.1.2 Record keyboard
+---------------------
+
+Record keyboard events only and save log to kbd-rec.xnl.
+        `cnee --record --keyboard --out-file kbd-rec.xnl'
+   After having typed this Xnee records all your keyboard actions.
+After Xnee has exited you will be able to replay your keyboard actions.
+Xnee will stop after having record 100 events (this is the default
+behaviour).
+
+5.1.3 Record keyboard and mouse
+-------------------------------
+
+Record keyboard and mouse and save log to km-rec.xnl.
+        `cnee --record --keyboard --mouse --out-file kbd-rec.xnl'
+   After having typed this Xnee records all your keyboard and mouse
+actions.  So now move your pointer and write some stuff with your
+keyboard. After Xnee has exited you will be able to replay your
+keyboard and mouse actions. Xnee will stop after having record 100
+events (this is the default behaviour).
+
+5.1.4 Record a gnumeric session
+-------------------------------
+
+Record a gnumeric session. Record 400 events. Save output in file
+gnumeric.xnl Start a terminal emulator (e.g xterm)
+     `xterm&'
+
+   Start Xnee
+        `cnee --record --keyboard --mouse --events-to-record 400 \'
+        ` --out-file gnumeric.xnl&'
+
+   Start gnumeric
+     `gnumeric&'
+   Start using gnumeric. Browse the menus above, reset the fonts etc.
+
+5.1.5 Record a gnumeric session with synchronisation data
+---------------------------------------------------------
+
+Record a gnumeric session. Record 400 events. Save output in file
+gnumeric2.xnl
+
+Start a terminal emulator (e.g xterm) `xterm&'
+
+   Start Xnee
+        `cnee --record --keyboard --mouse --events-to-record 400 \'
+        ` --out-file gnumeric2.xnl\'
+        `--delivered-event-range Expose,MapRequest,LeaveNotify,EnterNotify  &'
+
+Start gnumeric `gnumeric&' Start using gnumeric. Browse the menus
+above, reset the fonts etc.
+
+5.2 Replayer
+============
+
+5.2.1 Replay mouse motions
+--------------------------
+
+Replay mouse motions as found in the file mouse-rec.xnl.
+        `cnee --replay  --file mouse-rec.xnl'
+   Xnee will now imitate exactly what you did when you recorded this
+file.
+
+5.2.2 Replay mouse motions using with half speed
+------------------------------------------------
+
+Replay mouse motions as found in the file mouse-rec.xnl but with the
+speed set to 50% of the recorded.
+        `cnee --replay  --file mouse-rec.xnl --speed-percent 50'
+   Xnee will now imitate exactly what you did when you recorded this
+file, allthough it will be done in 50% of the recorded time.
+
+5.2.3 Replay mouse motions using with double speed
+--------------------------------------------------
+
+Replay mouse motions as found in the file mouse-rec.xnl but with the
+speed set to 200% of the recorded.
+        `cnee --replay  --file mouse-rec.xnl --speed-percent 200'
+   Xnee will now imitate exactly what you did when you recorded this
+file, allthough it will be done twice as fast as when recorded.
+
+5.2.4 Replay keyboard actions
+-----------------------------
+
+Replay keyboard events from file kbd-rec.xnl.
+        `cnee --replay --file kbd-rec.xnl'
+   After having typed this Xnee replays all your keyboard actions.
+After Xnee has exited you will be able to replay your keyboard actions.
+
+5.2.5 Replay keyboard and mouse
+-------------------------------
+
+Replay keyboard and mouse from the file km-rec.xnl.
+        `cnee --replay --keyboard --mouse --file kbd-rec.xnl'
+   After having typed this Xnee replays all your keyboard and mouse
+actions.  Xnee moves your pointer and writes the the same stuff as you
+did when recording.
+
+5.2.6 Replay a gnumeric session
+-------------------------------
+
+Replay the gnumeric session above
+Start a terminal emulator (e.g xterm) `xterm&' Start a new fresh
+gnumeric spreadsheet `gnumeric&'
+
+   Start Xnee
+        `cnee --replay  --file gnumeric.xnl'
+   Xnee will now do the same stuff you did when recording. It may happen
+that some user actions are replayed to early. This is so because Xnee
+has no way of knowing if it is in sync with the recorded session.
+
+5.2.7 Replay a gnumeric session with synchronisation data
+---------------------------------------------------------
+
+Replay the second gnumeric session above.
+Start a terminal emulator (e.g xterm) `xterm&' Start a new fresh
+gnumeric spreadsheet `gnumeric&'
+
+   Start Xnee
+        `cnee --replay  --file gnumeric2.xnl'
+   Xnee will now do the same stuff you did when recording. It may happen
+that the replaying slows down. This is because Xnee is currently out of
+sync.  When being out of sync Xnee slows down a bit and checks the
+thresholds if it is allowed to continue. Xnee will most probably find
+itself in sync after a short while. All recorded user actions should
+have occured the same way as when recording.
+
+5.2.8 Replay a gnumeric session with synchronisation data setting threshold
+---------------------------------------------------------------------------
+
+Replay the second gnumeric session above.
+Start a terminal emulator (e.g xterm) `xterm&' Start a new fresh
+gnumeric spreadsheet `gnumeric&'
+
+5.3 Retyper
+===========
+
+5.3.1 Retype the help printout
+------------------------------
+
+If you want Xnee to fake a user typing the help printout from xnee you
+can use the `--type-help' option.
+Start a terminal emulator (e.g xterm) and an editor (e.g emacs).
+     `xterm &'
+
+     `emacs &'
+   Retype the help printout by starting xnee with a 10 seconds delay
+delay.
+     `cnee --time 10 --type-help'
+   Move your mouse to the editor and make the editor have focus.  Wait
+a few seconds and xnee will type the help. You will now also have a
+copy of help text.
+
+5.3.2 Retype a file
+-------------------
+
+If you want Xnee to fake a user typing the letters as found in a text
+file you can use the retype mode. Note that it isn't possible to retype
+all characters yet. This will be implemented as soon as possible. We'll
+give an example on how to use this mode.
+Start a terminal emulator (e.g xterm)
+     `xterm &'
+   Create a text file
+     `echo "Hi Xnee" > testfile.txt'
+
+   Retype the contents of this file to another file by starting xnee
+with a 10 seconds delay delay.
+     `cnee --time 10 --retype-file testfile.txt'
+   Start the fabulous editor `cat'
+     `cat > copiedfile.txt'
+   Wait a few seconds and xnee will retype the letters in the file
+`testfile.txt'. You will now also have a copy of that file.  The copy
+is called copiedfile.txt. This is a realy a stupid way to copy a file
+but this option opens up a few possibilities.
+
+5.4 Distributor
+===============
+
+With the distribution mode Xnee can send your device events to multiple
+displays.
+
+5.4.1 Distribute your mouse motions
+-----------------------------------
+
+You can distribute your mouse motions to the displays frodo:0.0 and
+sam:0.0
+Start a terminal emulator (e.g xterm)
+     `xterm &'
+   Start xnee
+     `cnee --distribute frodo:0,sam:0.0'
+     ` --record --mouse'
+
+   If you have setup authority correct on frodo and sam you will see
+all you mouse motions being done on those displays as well.
+
+5.4.2 Distribute the replaying of mouse motions
+-----------------------------------------------
+
+Replay and distribute mouse motions as found in the file
+`mouse-rec.xnl'.
+        `cnee --replay  --file mouse-rec.xnl'
+        ` --distribute frodo:0,sam:0.0'
+   Xnee will now imitate exactly what you did when you recorded this
+file on your host as well on frodo and sam.
+
+5.4.3 Distribute the retyping of a file
+---------------------------------------
+
+If you want Xnee to to distribute the fakeing of a user typing the
+letters as found in a text file you can use the retype mode together
+with the distribution mode.
+Start a terminal emulator (e.g xterm) on each of the hosts
+     `xterm &'
+   Create a text file.
+     `echo "Hi again Xnee" > distfile.txt'
+
+   Retype the contents of this file to another file by starting xnee
+with a 10 seconds delay delay.
+     `cnee --time 10 --retype-file distfile.txt'
+     ` --distribute frodo:0,sam:0.0 '
+   Start the fabulous editor `cat' on the terminal emulators on each the
+terminals.
+     `cat > copiedfile.txt'
+
+If you have setup authority correct on frodo and sam you will, after a
+few seconds, see xnee retype the letters in the file `distfile.txt'.
+You will now also have three copies of that file.  On copy on each
+host. The copy is called copiedfile.txt. This might seem like a stupid
+way to copy a file to three locations but this is just an example.
+
+5.5 Key
+=======
+
+5.5.1 Stop Xnee with key
+------------------------
+
+You can stop xnee by specifying a key. Make sure that this key isn't
+grabbed by another X client (e.g by the Window Manager). Let's say that
+you want Xnee to stop recording if you press Control and h.
+        `cnee --record --mouse --events-to-record -1 --stop-key h'
+   This will make xnee record mouse events until you press h.  All
+printouts are done to stdout so you can see that Xnee stops when you
+press the key.
+Move your mouse for a while and you'll see xnee print out lots of lines.
+Press h.
+Xnee will now have stopped recording.
+
+5.5.2 Pausing and resuming Xnee with key
+----------------------------------------
+
+You can pause and resum xnee by specifying a key.  Make sure that this
+key isn't grabbed by another X client (e.g by the Window Manager).
+Let's say that you want Xnee to pause recording if you press p and to
+resume when pressing Comntrol and r.
+        `cnee --record --mouse --events-to-record -1 --pause-key p \'
+        `--resume-key r'
+   This will make xnee record mouse events until you press p.  All
+printouts are done to stdout so you can see that Xnee stops when you
+press the key.
+Move your mouse for a while and you'll see xnee print out lots of lines.
+Press p.
+Xnee will now have paused recording. Move your mouse for a while and
+note that nothing is printed.
+Press r.
+Xnee will now have resumed recording. Move your mouse for a while and
+note that xnee begins its printouts.
+
+5.6 Using macro
+===============
+
+Macors can be used in various applications allthough many applicaions
+have a macro functionality built in (e.g emacs).
+
+5.6.1 Define a simple macro
+---------------------------
+
+There are plenty of tools that bind a key combination to different
+actions. For various reasons the author of this manual is familliar
+with xrebind so we will use xrebind in this example.
+The first thing to do is to decide which key combination to tie to the
+wanted action. Let's say we want to use one of the funtion keys, F1.
+We then have to find out which keycode belongs to that key. The action
+we will bind to this key combination will be the replaying of a recorded
+session from the previous examples.
+We use Xnee to find the keycode for F1. Start xnee.
+        `cnee --record --keyboard --events-to-record 20'
+   Press the F1 key and see what number was printed out. It will look
+something like this:
+     `0,2,0,0,0,67,0,90300078'
+     `0,3,0,0,0,67,0,90300156'
+   The interesting part here is the 6th column. In our example we find
+67, which is the keycode for F1.
+Now we move on to setup xrebind to grab F1 and bind that to replay the
+mouse motions from the file `mouse-rec.xnl'. Open or create a new file
+in your home directory called `.xrbrc' and add the lines.
+     `XrebindGrab'
+     `{'
+     `  Action      = Execute'
+     `  GrabKeycode = 67'
+     `  Modifier    = AnyModifier'
+     `  Command     = xnee  --replay --file mouse-rec.xnl'
+     `  Comment     = Starting xnee replay'
+     `  AutoRepeat  = false'
+     `  Fork        = true'
+     `}'
+   Let's try it. Start xrebind with verbose printouts.
+     `xrebind --verbose'
+   Press F1 and the recorded session from the previous example shall be
+replayed. You can also see in the verbose printouts that xrebind
+executes xnee.
+
+5.6.2 Define another simple macro
+---------------------------------
+
+Let's say we want to bind Control and e to execute the session as in the
+example above. This time setting up xrebind is a bit easier.
+Setup xrebind to grab F1 and bind that to replay the mouse motions from
+the file `mouse-rec.xnl' by opening or create a new file in your home
+directory called `.xrbrc' and add the lines.
+     `XrebindGrab'
+     `{'
+     `  Action      = Execute'
+     `  GrabKey     = e'
+     `  Modifier    = Control'
+     `  Command     = xnee  --replay --file mouse-rec.xnl'
+     `  Comment     = Starting xnee replay'
+     `  AutoRepeat  = false'
+     `  Fork        = true'
+     `}'
+     `e, Control, Exec, xnee,  --replay --file mouse-rec.xnl, \'
+     `Fork, NoAutoRepeat'
+   Let's try it. Start xrebind with verbose printouts.
+     `xrebind --verbose'
+   Press Control and e and the recorded session from the previous
+example shall be replayed.
+
+5.7 Various options
+===================
+
+5.7.1 Using verbose mode
+------------------------
+
+To enable verbose mode, start xnee like this
+     `cnee --verbose --record --mouse'
+   Move the mouse for a while and you'll lots of verbose printouts that
+usualy isn't there.
+
+5.7.2 Using human readable printouts
+------------------------------------
+
+To enable human printout mode, start xnee like this
+     `cnee --human-printout --record --mouse'
+   Move the mouse for a while and you'll see the data printed out in an
+almost human friendly format.
+
+5.7.3 Using a differet screen resolution
+----------------------------------------
+
+If a session was recorded on a screen with another resolution than on
+the one where we replay the session xnee will translate all coordinates
+automagically. However, you can force xnee to use a specific resolution
+when replaying. To do this, start xnee like this
+     `cnee --replay --file mouse-rec.xnl \ '
+     `--replay-resolution  800x600'
+   Xnee will now replay the events recorded in the sessions file
+`mouse-rec.xnl' as if the screen has a resolution of 800x600.
+
+5.7.4 Using a offset when replaying
+-----------------------------------
+
+If a session was recording a centered window with a window manager and
+is to bo replayed without a window manager (still centered) you can use
+the offset switch to make Xnee replay the events in order to get the
+coordinates right.
+     `cnee --replay --file mouse-rec.xnl \ '
+     `--replay-offset 12,-7'
+   Xnee will now replay the events recorded in the sessions file
+`mouse-rec.xnl' and adding 12 to the x coordinate and subtract 7 from
+the y coordinate.
+
+5.7.5 Using a window position recall
+------------------------------------
+
+For some reason a replayed window may pop up at a different position as
+when recorded. Xnee can try to solve this by adding the
+`recall-window-position' option during replay.
+     `cnee --replay --file mouse-rec.xnl \ '
+     `--recall-window-position'
+   If a window pops up at a different position when replaying (as whe
+recorded) Xnee moves the new window to the same position as when
+recorded.
+
+5.7.6 Using no resolution translation
+-------------------------------------
+
+If a session was recorded on a screen with another resolution than the
+on the one where we replay the session xnee will translate all
+coordinates automagically. However, you can force xnee not to use
+translation. To do this, start xnee like this
+     `cnee --replay --file mouse-rec.xnl \ '
+     `--no-resolution-adjustment'
+   Xnee will now replay the events recorded in the sessions file
+`mouse-rec.xnl' as if the screen had the same resolution the recorded
+one.
+
+5.7.7 Record another display than the default
+---------------------------------------------
+
+If you want to record another display than the default, as set in the
+DISPLAY variable, you use the `--display' option.
+     `cnee --record --mouse --display frodo:0.0 '
+   Xnee will now record the mouse events on the display frodo:0.0.
+
+5.7.8 Replay to another display than the default
+------------------------------------------------
+
+If you want to replay to another display than the default, as set in the
+DISPLAY variable, you use the `--display' option.
+     `cnee --replay --display frodo:0.0 --file mouse-rec.xnl '
+   Xnee will now replay the mouse events on the display frodo:0.0.
+
+5.8 Shell scripts using Xnee
+============================
+
+Insted of onvoking Xnee for every time you need to fake events you can
+make use of the shell functions as delivered with Xnee.  With these
+functions you can start one instance of Xnee and fake device events
+whenever you need.
+
+     `#!/bin/bash '
+     ` '
+     `# Source in handy functions '
+     `. /usr/share/xnee/xnee.sh '
+     ` '
+     `# Loop and press buttons '
+     `TMP=0 '
+     `while [ $TMP -le 5]'
+     `do'
+     `  TMP=$(($TMP+1))'
+     `  xnee_fake_button $TMP '
+     `done'
+     ` '
+     `# Just a simple example ....don't bother to understand '
+     `tar cvf /tmp/crap.tar *'
+     `sleep 2'
+     ` '
+     `# Fake ls and Enter '
+     `xnee_fake_key l'
+     `xnee_fake_key s'
+     `xnee_fake_key XK_Return'
+     ` '
+     ` '
+   This example will fake press and release of the mouse button and do
+fake press and release of ls followed by a press and release of
+Enter.... and of course, you'll get a tar file in /tmp.
+
+   Make sure that the path to the `xnee.sh' is correct.
+
+
+File: xnee.info,  Node: Programs,  Next: File format,  Prev: Examples,  Up: Top
+
+6 Xnee Programs
+***************
+
+GNU Xnee consists of three different programs, cnee, gnee and pnee.
+
+6.1 cnee - cnee's not an event emulator
+=======================================
+
+This is the Xnee command line program. This programs contains most
+features and is the basis for this documentation.
+
+   For a user not used to X11 it is probably a good idea to start with
+gnee or pnee instead or start using cnee in demonstration mode: `cnee
+--demo'
+
+6.2 gnee - gnee's not an emulator either
+========================================
+
+This is a GUI (using GTK2/Gnome) with most of the features of cnee. The
+GUI has been designed for ease of use.
+
+   Currently there are no plans for making a separate manual for gnee.
+
+6.3 pnee - pnee's not even emulating
+====================================
+
+This is a Gnome panel applet with a minimal set of features. Ease of
+use is the motto for this program. It is intended for users not being
+experts on X11 but still wants to record and replay a session for what
+ever purpose. By default pnee have settings that need not be changed
+for most cases. You can, however, launch the preferences dialog and set
+your preferred values as in most other applets.
+
+   If you find pnee a bit limited we suggest you switch over to using
+cnee.
+
+   Note: If pnee hangs you can press the stop button twice to make a
+reset. Hopefully this will solve the problem.
+
+6.3.1 Reporting pnee bugs
+-------------------------
+
+By default pnee writes error, verbose printouts and warnings to stderr
+which will not be visible to you as a user, since pnee will be started
+automatically along with the other applets. If you start up the
+preferences dialog you can choose a file for pnee printouts. After that
+you should turn on verbose logging (also in the preferences dialog) and
+then reproduce the bug and send over the file to <[e-mail]>.
+
+
+File: xnee.info,  Node: File format,  Next: Internals,  Prev: Programs,  Up: Top
+
+7 File types and format
+***********************
+
+
 The files used by Xnee are
+   * Xnee Project File
+
+   * Xnee Session File
+   These files must follow the Xnee File Format.
 
+
+7.1 Project file
+================
+
+Xnee can be set either using command line options (when using xnee) or
+by
 clicking the correct buttons etc in the GUI (using gnee). Instead
+of setting 
 the same settings over and over again, you can use the
+Xnee Project File. 
 
 
+
+7.1.1 Create a project file
+---------------------------
+
+You can create a project by yourself. This can be done using 
 the
+`write-settings' option in cnee or the "save settings to file" 
 when
+using gnee or you can use the Xnee GUI (gnee) to write one.
 You can
+also write one by yourself in your favorite editor.  Just make sure you
+
 follow the Xnee format. For information and specification on this
+format read 
 the Xnee format chapter.
  
 
 The authors of Xnee
+suggests you start of with a generated project file. To get one 
 such
+file, type the following
 `cnee --mouse --keyboard --write-settings
+new_proj.xnp'. You will now 
 have a file `new_proj.xnp' with some
+useful values, which you can edit as you wish.
  
 
 To use this
+file to record, simply type
 `cnee --record --project new_proj.xnp'
+
 
+
+7.2 Xnee Session file
+=====================
+
+The Xnee session files are the printouts from a recorded session
+following the Xnee File Format. For information and specification on
+this format read the Xnee File Format chapter.
 
 
 
+
+7.3 Xnee file format
+====================
+
+The Xnee Format is divided into different directives. 
 The format is
+line based, meaning that
 
+   * there is one directive per line
+
+   * one line contains one (and only one) directive
+   These directives are definied as follows. 
 
+
+7.4 Xnee directives
+===================
+
+The following directives are used in Xnee:
+ Directives             Description
+ Comment                This is used to comment the various files
+ Project                These contains information about the session- or
+                        project file
+ Settings               Data used when recording and replaying
+ Replay data            Recorded replayable data (used when replaying)
+ Script replay data     Scriptable primitives
+ Mark                   Lines inserted in the seesion file when a
+                        modifier+key was pressed
+ Execution              Lines that trigger the execution of an external
+                        program
+ Project information    Project
+   
 
 
+
+7.4.1 Comment
+-------------
+
+
 
+ First token    Interpretation                       
+ #              The whole line is ignored.           
+   As long as the first token is `#' the whole line is intrepreted as a
+comment, just
 as in bash.
 
 
+
+7.4.2 Settings
+--------------
+
+
+
 Settings directive              Argument    Interpretation
+data-to-record                   integer     Limits the number of data to record to to
+                                             the integer value
+events-to-record                 integer     Limits the number of events to record to
+                                             to the integer value
+time-to-record                   integer     Limits the number of seconds to record to
+                                             to the integer value
+display                          string      Sets the display to record or replay to
+                                             the string
+distribute                       string      Distribute all recorded or replayed
+                                             replayable events to the display given by
+                                             the string
+file                             string      Read replay data from the file given by
+                                             the string
+out-file                         string      Print recorded data to the file given by
+                                             the string
+plugin                           string      Use the plugin given by the string
+first-last                       boolean     Print only first and last of successive
+                                             MotionNotify events
+verbose                          boolean     Use verbose debugging printout
+buffer-verbose                   boolean     Use verbose buffer verbose printouts (not
+                                             built by default)
+time                             integer     Delay the start of the Xnee action
+all-clients                      boolean     Record all curret and future clients
+                                             (default)
+future-clients                   boolean     Record only future clients
+human-printout                   boolean     Prints the recorded data in a (quite) more
+                                             ser friendly format
+sync-mode                        boolean     Sets recording mode
+speed-percent                    integer     Sets the replaying speed percentage to the
+                                             integer value
+stop-key                         string      Sets the stop key combination to the
+                                             string
+pause-key                        string      Sets the pause key combination to the
+                                             string
+resume-key                       string      Sets the resume key combination to the
+                                             string
+mark-key                         string      Sets the mark key combination to the
+                                             string
+exec-key                         string      Sets the execute key combination to
+                                             string
+replay-resolution                string      Sets the replay resolution to the string
+replay-resolution                string      Sets the replay resolution to the string
+recall-window-position                       Use window position recall during replay
+resolution-adjustment            boolean     Use resolution adjustment, even if the
+                                             recored resolution differs from the one to
+                                             replay to
+event-range                      range       Sets the events to record
+error-range                      range       Sets the errors to record to range*
+request-range                    range       Sets the request to record to range*
+reply-range                      range       Sets the replies to record to range*
+extension-request-major-range    range       Sets the extension requests (major) to
+                                             record to range*
+extension-request-minor-range    range       Sets the extension requests (minor) to
+                                             record to range*
+extension-reply-major-range      range       Sets the extension replies (major) to
+                                             record to range*
+extension-reply-minor-range      range       Sets the extension replies (minor) to
+                                             record to range*
+force-replay                     boolean     Continue to replay even if Xnee is out of
+                                             sync
+max-threshold                    integer     Sets the maximum synchronisation threshold
+min-threshold                    integer     Sets the minimum synchronisation threshold
+total-threshold                  integer     Sets the total maximum synchronisation
+                                             threshold
+events-to-record                 integer     Sets the number of events to record
+data-to-record                   integer     Sets the number of data to record
+time-to-record                   integer     Sets the number of seconds to record
+store-mouse-position                         If set, Xnee records the initial mouse
+                                             position and makes sure that replaying
+                                             starts from there
+retype-press-delay               integer     Xnee delays processing after a faked key
+                                             press (during retype)
 with integer milli
+                                             seconds
+retype-release-delay             integer     Xnee delays processing after a faked key
+                                             press (during retype)
 with integer milli
+                                             seconds
+   
 
+Settings argument      Description                   Example
+`integer'              is an integer value.          1
+`string'               is a string.                  localhost
+`boolean'              is a boolean value given by   true, false, 0, 1
+                       true/1 or false/0             
+`subrange'             Subrange is gives a range of  2-5 or MapNotify
+                       data by specifying a start    
+                       and stop
       data. In       
+                       the case of one data the      
+                       stop data can be omitted.     
+`range'                Ranges are a comma separated  2-3,MotionNotify-MapNotify,GravityNotify,PropertyNotify,30
+                       list of subranges.            
+   
 
 
+
+7.4.3 Replay
+------------
+
+Replay directive              Interpretation
+0,0                           not valid
+0,1                           not valid
+0,2,keycode,time              KeyPress on key with keycode, used to
+                              replay
+0,3,keycode,time              KeyRelease on key with keycode, used to
+                              replay
+0,4,button nr,time            ButtonPress on button nr, used to replay
+0,5,button nr,time            ButtonRelease on button nr, used to
+                              replay
+0,6,x,y,time                  MotionNotify on poistion (x,y), used to
+                              replay
+0,7-XXX,time                  MotionNotify on poistion (x,y), used to
+                              replay
+1,request number, request     Recorded request, used during
+type, length, request id,     synchronisation
+time                          
+2,reply number,time           Recorded reply, used during
+                              synchronisation
+3,error number,time           Recorded error, used during
+                              synchronisation
+time is the time on the server the data was to the recording Xnee
+client. This time is used to keep the speed intact during replay.
 
+
+7.4.4 Script replay data
+------------------------
+
+
+Primitive                     Interpretation
+fake-motion                   Fakes a mouse motion
+fake-button-press             Fakes a button press
+fake-button-release           Fakes a button release
+fake-button                   Fakes a button press and release
+fake-key-press                Fakes a key press
+fake-key-release              Fakes a key release
+fake-key                      Fakes a key press and release
+   
+Primitive      Primitive      Interpretation
+variable       values         
+x=value        integer        Sets the x position used in fake-motion to
+                              value
+x=value        +integer       Set the relative motion (x direction) used
+                              in fake-motion to value
+x=value        -integer       Set the relative motion (x direction) used
+                              in fake-motion to value
+y=value        integer        Sets the y position used in fake-motion to
+                              value
+y=value        +integer       Set the relative motion (y direction) used
+                              in fake-motion to value
+y=value        -integer       Set the relative motion (y direction) used
+                              in fake-motion to value
+button=value   integer        set the button to fake with
+                              fake-button-press, fake-button-release and
+                              fake-button to value
+key=value      integer        set the key to fake with fake-key-press,
+                              fake-key-release and fake-key to value
+   
 
+
+7.4.5 Mark
+----------
+
+First tokens   Arguments      Interpretation
+Mark           time string    Ignored. This feature is intended to let
+                              the user do whatever he/she
       wants
+                              to. This will obviously lead to modifying
+                              the source code etc.
+
 
+
+7.4.6 Exec
+----------
+
+First tokens   Arguments      Interpretation
+Exec           command        This is used during to replay to execute a
+               string         given command. If no
       command
+                              string is found Xnee will try to
+                              read the command from the environment
+                              variable `XNEE_EXEC_COMMAND'
+
 
+
+7.4.7 Project information
+-------------------------
+
+Project information directives   Arguments
+ProjectName                      string s is the project name
+ProjectDescription               string s is the project description
+ProjectCreationDate              string s is the project creation date
+ProjectCreationProgram           string s is the name of the program
+                                 that create the project file
+ProjectCreationProgVersion       string s is the version of the program
+                                 that create the project file
+ProjectLastChangeDate            string s is the date of the last change
+                                 of the project file
+ProjectLastChangeProgram         string s is the name of the program
+                                 that last changed of the project file
+ProjectLastChangeVersion         string s is the version of the program
+                                 that last changed of the project file
+ProjectCurrentChangeDate         string s is the date of the current
+                                 change of the project file
+ProjectCurrentChangeProgram      string s is the name of the program
+                                 that current changed of the project
+                                 file
+ProjectCurrentChangeVersion      string s is the version of the program
+                                 that current changed of the project
+                                 file
+
+
+File: xnee.info,  Node: Internals,  Next: Requirements,  Prev: File format,  Up: Top
+
+8 Xnee Internals
+****************
+
+This chapter is intended to explain the internal design of libxnee.
+Hopefully this will lead to a better understanding of how to use Xnee
+and why some features exists and why some doesn't.
+
+8.1 Synchronisation
+===================
+
+We will try to go through the basics of how Xnee implememnts
+synchronisation and try to tell you, by using examples, why
+synhronisation is important.
+
+8.1.1 Why synchronise
+---------------------
+
+To understand why synchronisation during replay is needed an example is
+given.
+
+   In this example only mouse and keyboard events are recorded. Think
+of a session with a web browser.
+
+   During record the following is done:
+   * Start galeon (or another web browser) via the GNOME panel
+
+   * Press Ctrl-O which pops up a window
+
+   * Press the left button in the textfield of the popup window
+
+   * Enter the URL you want to enter (e.g `http://www.gnu.org')
+
+   * Click on the OK button
+
+   * Then click on another URL (e.g GNU Documentation)
+
+   * Then click on another URL (e.g On-Line Documentation)
+
+   When replaying this session it is often to synchronise the recorded
+session with what's happening "right now" on the display since
+sometimes (or rather always) there can be different response times from
+the same URL.
+
+   During replay the following is done:
+   * Galeon is started
+
+   * Ctrl-O is typed which pops up a window
+
+   * Press the left button in the textfield of the popup window
+
+   * Enter the URL you want to enter (e.g `http://www.gnu.org')
+
+   * Click on the OK button
+
+   * ... due to an enormous amount of visitors the GNU web server can't
+     respond as quick as it did when recording. So when the next thing
+     happens
+
+   * Then click on another URL (e.g GNU Documentation)
+
+   * ... the page hasn't been loaded and when the next event is replayed
+
+   * Then click on another URL (e.g On-Line Documentation)
+
+   * ... the link isn't there and we're really out of sync with the
+     recorded session
+
+8.1.2 How to synchronise
+------------------------
+
+Instead we could record some more data than just the mouse and keyboard
+events.
+
+   During record the following is done:
+   * Start galeon (or another web browser) via the GNOME panel
+
+   * Record some X data that tells us that a window have been created
+
+   * Press Ctrl-O which pops up a window
+
+   * Record some X data that tells us that a window have been created
+
+   * Press the left button in the textfield of the popup window
+
+   * Enter the URL you want to enter (e.g `http://www.gnu.org')
+
+   * Click on the OK button
+
+   * Record some X data that tells us that a window have been destroyed
+
+   * Then click on another URL (e.g GNU Documentation)
+
+   * Record some X data that tells us that a some text has been
+     displayed in a window
+
+   * Then click on another URL (e.g On-Line Documentation)
+
+   * Record some X data that tells us that a some text has been
+     displayed in a window
+   The non-mouse-or-keyboard events recorded (window created & text
+displayed) are record for synchronisation purposes.
+
+   During replay the following is done:
+   * Start galeon (or another web browser) via the GNOME panel
+
+   * wait for: the recorded X data to be sent again
+
+   * Press Ctrl-O which pops up a window
+
+   * wait for: the recorded X data to be sent again
+
+   * Press the left button in the textfield of the popup window
+
+   * Enter the URL you want to enter (e.g `http://www.gnu.org')
+
+   * Click on the OK button
+
+   * wait for: the recorded X data to be sent again
+
+   * Then click on another URL (e.g GNU Documentation)
+
+   * wait for: the recorded X data to be sent again
+
+   * Then click on another URL (e.g On-Line Documentation)
+
+   * wait for: the recorded X data to be sent again
+
+8.1.3 Synchronisation is needed
+-------------------------------
+
+So by recording more data than just the events to be replayed we can
+synchornise what was recorded with what is going on when replaying. But
+the data has to be choosen with respect to that the data:
+   * differs from different sessions (Gimp and Xterm are really
+     different)
+
+   * slows down the replay session if there are too many
+
+   * is hard to choose since the X protocol is rich
+
+   * differs (comparing record and replaying)
+
+   * can have different ordering (comparing record and replaying)
+
+8.1.4 Different data for different kind of sessions
+---------------------------------------------------
+
+If we record an xterm session with all data being recorded and compare
+that to a recorded GIMP session with all data being recordr we can see
+that the data to use as synchronisation data differs. AS an example
+there aren't so many windows created/destryed during an xterm session.
+
+   The solve to the the problem of finding out what data to use as
+synchronisation data one can:
+   * use the project files delivered with Xnee
+
+   * analyse the application (using Xnee's  `--human-printouts' option)
+     and do some "trial and error"
+
+8.1.5 Slow replay session due to too many synchronise data
+----------------------------------------------------------
+
+The synchronisation itself doesn't take much time but there are
+timeouts that makes Xnee paues for a short while (see above). If there
+are many such timeouts it will lead to a slow or shaky replaying
+session.
+
+8.1.6 X protocol is rich and asynchronous
+-----------------------------------------
+
+For an end user (with no X expertise) it is hard to read the X protocol
+specification and make assumptions on what data to use.
+
+8.1.7 Different data sent
+-------------------------
+
+Even if one starts up a machine from scratch (reboot) when recording
+and from scratch when replaying there is no guarantee that the data is
+sent in the same order or that exactly the same amount of data is sent.
+
+8.1.8 Buffers and timeouts
+--------------------------
+
+To enable synchronisation Xnee buffers data:
+   * that was read in the session file but hasn't been sent during
+     replay
+
+   * that was sent during replay but hasn't been seen in the session
+          file being replayed
+   For every data read from session file (during replay) that isn't
+replayable (i e device event) Xnee stores the data in a buffer. Xnee
+also stores the data sent from the X server during playback. The data
+received from the server make the buffer entry for that specific data
+be decremented. If, on the other hand, the same data was read from file
+the buffer entry for that data is incremented.  Before replaying any
+replayable event Xnee makes sure it is in sync. If Xnee is in sync the
+replaying continues. If Xnee is out of sync it will look for its
+thresholds and see if it is inside a user specified range. There are
+three thresholds:
+   * positive maximum  nr data read from session file
+
+   * negative minimum  nr of data sent from X server
+
+   * absolute total maximum sum of the absolute values above
+   If Xnee read one data from file (e.g the event MapNotify) Xnee
+checks if the buffer entry for the specific data is bigger than the
+positive maximum value (after having incremented the buffer value).
+
+   If Xnee receives one data from the X server (e.g the event
+MapNotify) it checks if the  buffer entry for the specific data is
+bigger than the negative minimum value (after having decremented the
+buffer value).
+
+   Xnee also checks if the absolute sum of the differences for every
+entry in the buffer is higher the a total threshold.
+
+   If Xnee is getting out of sync it slows down the speed a bit and
+tries to continue. However after a while it may happen that Xnee
+considers that it no use to continue since we are too much out of sync.
+Xnee compensates for the delay during replay that is caused when being
+out of sync.
+It is possible to tweak the thresholds using the `--maximum-threshold',
+`--negative-threshold' and `--total-diff-threshold' options. Is is also
+possible to turn off synchronisation completely using the `--no-sync'
+option.
+
+
+File: xnee.info,  Node: Requirements,  Next: FAQ,  Prev: Internals,  Up: Top
+
+9 Xnee Requirements
+*******************
+
+9.1 Runtime requirements
+========================
+
+Xnee requirements:
+   * RECORD extension
+
+   * XTest extension
+   You can use Xnee in replaying mode without RECORD extension if
+synchronisation is turned off.
+
+9.2 Development requirements
+============================
+
+For development requirements, please look at the DEVELOPMENT file that
+is distributed with all packages and with CVS.
+
+
+File: xnee.info,  Node: FAQ,  Next: Copying This Manual,  Prev: Requirements,  Up: Top
+
+10 FAQ
+******
+
+`Where do I send questions?'
+     <[e-mail]>
+`Where and how do I report bugs?'
+     Turn on verbose mode `cnee --verbose' and save the printouts.
+     Include all printouts and log files in the mail which is sent to
+     <[e-mail]>
+`Can you add xxx functionality to Xnee'
+     Send an email to <[e-mail]> and we'll consider it.
+
+`Why the name Xnee?'
+     We wanted to use a recursive acronym, as GNU ("GNU's Not Unix').
+     After having read the Wine documentation, we thought that Xnee is
+     not an Event Emulator would work fine since Xnee is Not an Event
+     Emulator but rather a event recorder and faker.
+
+`What does the name cnee mean?'
+     cnee's not an event emulator
+
+`What does the name gnee mean?'
+     gnee's not an emulator either
+
+`What does the name pnee mean?'
+     pnee's not even emulating
+
+`What doesn't the name gnee mean?'
+     gnee's not an Event Emulator
+
+`What license is Xnee released under ?'
+     GPL version two or later. Which can be found at
+     `http://www.gnu.org/copyleft/gpl.html'. Xnee will switch to GPLv3
+     as soon as GPLv3 is released.
+
+`Where is the CVS repository?'
+     You can find a CVS tree at `http://savannah.gnu.org'.  You are
+     more than welcome to join
+
+`Is there a GUI frontend for Xnee ?'
+     Yes! Gnee.
+
+`When setting ranges (integers), how do I know what numbers belong'
+     to X11 data?  You can either type the data name directly (e.g
+     MotionNotify) or you can use the print-xxx-name options.
+        * `--print-data-name'
+
+        * `--print-event-name'
+
+        * `--print-error-name'
+
+        * `--print-reply-name'
+
+        * `--print-request-name'
+
+`When I replay to another display the characters are not correct?'
+     Make sure you use the same keyboard mapping.
+     A typical example:
+     Record local host using Xnee:
+     `cnee --record --out-file recorded_on_local.xnl '
+     Store remote keymap:
+     `xmodmap -pke -display remote:0 > remote.map '
+     Store local keymap:
+     `xmodmap -pke   > local.map '
+     Copy local keymap to remote host:
+     `cat local.map | xmodmap -display remote:0 - '
+     Replay previously recorded session:
+     `cnee --replay --file recorded_on_local.xnl --display remote:0 '
+     Copy the original remote keymap to remote host:
+     `cat remote.map | xmodmap -display remote:0 - '
+`When starting Xnee I am informed that I am missing the RECORD extension'
+     Your X server doesn't have the RECORD extension either loaded or
+     compiled. To solve this you have to, depending on what Xserver you
+     have do the following:
+
+`Can Xnee record more than one display?'
+     No, we used to consider adding the functionality but have no plans
+     to implement it anymore.
+
+`When starting Xnee I am informed that I am missing the RECORD extension'
+     Your X server doesn't have the RECORD extension either loaded or
+     compiled. To solve this you have to, depending on what Xserver you
+     have do the following:
+
+        * XFree86 4.0 and higher Make sure that the RECORD extension is
+          loaded. This is done by letting the Module section in the X
+          config file (e.g /etc/X11/XF86Config-4) look something like:
+
+          `Section "Module"'
+          `Load  "dbe"         # Double-buffering'
+          `Load  "GLcore"      # OpenGL support'
+          `Load  "dri"         # Direct rendering infrastructure'
+          `Load  "glx"         # OpenGL X protocol interface'
+          `Load  "extmod"      # Misc. required extensions'
+          `Load  "v4l"         # Video4Linux'
+          `# Load  "pex5"      # PHIGS for X 3D environment (obsolete)'
+          `Load  "record"      # X event recorder'
+          `# Load  "xie"       # X Image Extension (obsolete)'
+          `# You only need the following two modules if you do not use
+          xfs.'
+          `# Load  "freetype"  # TrueType font handler'
+          `# Load  "type1"     # Adobe Type 1 font handler'
+          EndSection
+
+          The important load directive (in this case) is the following
+          line
+          `Load  "record"  # X event recorder'
+        * X.org, XFree86 (3.3 and lower)  or any other Xserver
+          Recompile and reinstall the Xserver and make sure that RECORD
+          extension is built into the Xserver. Please look at the
+          documentation from your Xserver "vendor" on how to do that.
+
+`How do I build VNC so that I can use Xnee together with it?'
+     Download vnc source from:
+     `http://www.uk.research.att.com/vnc/xvnchistory.html'
+     In the file `Xvnc/config/cf/vnc.def' change NO on the following
+     items to YES as below:
+     `#define BuildRECORD YES'
+     `#define BuildRECORDlib YES'
+     Download the Xfree86 distribution from `http://www.xfree86.org'.
+     Specifically, the following dir, (currently in the file
+     `X430src-3.tgz file' ):
+     `tar zxvf \'
+     `X430src-3.tgz '
+     `xc/programs/Xserver/record/'
+     `xc/programs/Xserver/record/Imakefile'
+     `xc/programs/Xserver/record/record.c'
+     `xc/programs/Xserver/record/recordmod.c'
+     `xc/programs/Xserver/record/set.c'
+     `xc/programs/Xserver/record/set.h'
+     `xc/programs/Xserver/record/module/'
+     `xc/programs/Xserver/record/module/Imakefile'
+     `cp -rf \'
+     `xc/programs/Xserver/record \'
+     `vnc_unixsrc/Xvnc/programs/Xserver'
+     `cd libvncauth/' `xmkmf' `make all'
+     `cd Xvnc' `make World |& tee LOG'
+     Verify the build by running `xdpyinfo' in an xterm in the vncserver
+     and verify that RECORD and XTEST extensions are loaded.
+
+`How do I ensure that the mouse, during replay, is at the same position (x,y) as when recorded?'
+     Use the `--store-mouse-pos' option.  This will cause Xnee to store
+     the mouse position before starting to record. This position will
+     be used to set the start position before replaying of recorded
+     data starts.
+
+`How do I ensure that the same window is focused as when recorded?'
+     It's simple, just make sure that you record the window getting
+     focus.
+
+`The window pops up at different positions when replaying, can Xnee handle that?'
+     Yes, use the `--recall-window-position' option when replaying
+     (with cnee). This makes cnee try yo reposition the window as it
+     was positioned when recording the session.
+
+`Xnee seems to mess up my entire session after replaying a sessions which was interupted by Control-C?'
+     Xnee records the KeyPress belonging to Control. After that the
+     system sends Xnee a signal which makes Xnee stop recording. So you
+     end up having a Control KeyPress recorded, with no coresponding
+     KeyRelease. To solve the screwed up session, press Control (which
+     generates a KeyPress and the wanted KeyRelease). If you want to
+     keep your recorded session and not want this to happen again,
+     remove the last line in the recorded file starting with `2,'.
+
+     A better way to interrupt Xnee is to use the stop key option, e.g
+     in cnee `--stop-key F1'. This prevents the above situation.
+
+`Autorepeat is turned off by Xnee, how do I turn it on again?'
+     `xset r on'
+
+
+
+File: xnee.info,  Node: Copying This Manual,  Next: Index,  Prev: FAQ,  Up: Top
+
+Appendix A Copying This Manual
+******************************
+
+A.1 GNU Free Documentation License
+==================================
+
+                      Version 1.2, November 2002
+
+     Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
+     51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+
+     Everyone is permitted to copy and distribute verbatim copies
+     of this license document, but changing it is not allowed.
+
+  0. PREAMBLE
+
+     The purpose of this License is to make a manual, textbook, or other
+     functional and useful document "free" in the sense of freedom: to
+     assure everyone the effective freedom to copy and redistribute it,
+     with or without modifying it, either commercially or
+     noncommercially.  Secondarily, this License preserves for the
+     author and publisher a way to get credit for their work, while not
+     being considered responsible for modifications made by others.
+
+     This License is a kind of "copyleft", which means that derivative
+     works of the document must themselves be free in the same sense.
+     It complements the GNU General Public License, which is a copyleft
+     license designed for free software.
+
+     We have designed this License in order to use it for manuals for
+     free software, because free software needs free documentation: a
+     free program should come with manuals providing the same freedoms
+     that the software does.  But this License is not limited to
+     software manuals; it can be used for any textual work, regardless
+     of subject matter or whether it is published as a printed book.
+     We recommend this License principally for works whose purpose is
+     instruction or reference.
+
+  1. APPLICABILITY AND DEFINITIONS
+
+     This License applies to any manual or other work, in any medium,
+     that contains a notice placed by the copyright holder saying it
+     can be distributed under the terms of this License.  Such a notice
+     grants a world-wide, royalty-free license, unlimited in duration,
+     to use that work under the conditions stated herein.  The
+     "Document", below, refers to any such manual or work.  Any member
+     of the public is a licensee, and is addressed as "you".  You
+     accept the license if you copy, modify or distribute the work in a
+     way requiring permission under copyright law.
+
+     A "Modified Version" of the Document means any work containing the
+     Document or a portion of it, either copied verbatim, or with
+     modifications and/or translated into another language.
+
+     A "Secondary Section" is a named appendix or a front-matter section
+     of the Document that deals exclusively with the relationship of the
+     publishers or authors of the Document to the Document's overall
+     subject (or to related matters) and contains nothing that could
+     fall directly within that overall subject.  (Thus, if the Document
+     is in part a textbook of mathematics, a Secondary Section may not
+     explain any mathematics.)  The relationship could be a matter of
+     historical connection with the subject or with related matters, or
+     of legal, commercial, philosophical, ethical or political position
+     regarding them.
+
+     The "Invariant Sections" are certain Secondary Sections whose
+     titles are designated, as being those of Invariant Sections, in
+     the notice that says that the Document is released under this
+     License.  If a section does not fit the above definition of
+     Secondary then it is not allowed to be designated as Invariant.
+     The Document may contain zero Invariant Sections.  If the Document
+     does not identify any Invariant Sections then there are none.
+
+     The "Cover Texts" are certain short passages of text that are
+     listed, as Front-Cover Texts or Back-Cover Texts, in the notice
+     that says that the Document is released under this License.  A
+     Front-Cover Text may be at most 5 words, and a Back-Cover Text may
+     be at most 25 words.
+
+     A "Transparent" copy of the Document means a machine-readable copy,
+     represented in a format whose specification is available to the
+     general public, that is suitable for revising the document
+     straightforwardly with generic text editors or (for images
+     composed of pixels) generic paint programs or (for drawings) some
+     widely available drawing editor, and that is suitable for input to
+     text formatters or for automatic translation to a variety of
+     formats suitable for input to text formatters.  A copy made in an
+     otherwise Transparent file format whose markup, or absence of
+     markup, has been arranged to thwart or discourage subsequent
+     modification by readers is not Transparent.  An image format is
+     not Transparent if used for any substantial amount of text.  A
+     copy that is not "Transparent" is called "Opaque".
+
+     Examples of suitable formats for Transparent copies include plain
+     ASCII without markup, Texinfo input format, LaTeX input format,
+     SGML or XML using a publicly available DTD, and
+     standard-conforming simple HTML, PostScript or PDF designed for
+     human modification.  Examples of transparent image formats include
+     PNG, XCF and JPG.  Opaque formats include proprietary formats that
+     can be read and edited only by proprietary word processors, SGML or
+     XML for which the DTD and/or processing tools are not generally
+     available, and the machine-generated HTML, PostScript or PDF
+     produced by some word processors for output purposes only.
+
+     The "Title Page" means, for a printed book, the title page itself,
+     plus such following pages as are needed to hold, legibly, the
+     material this License requires to appear in the title page.  For
+     works in formats which do not have any title page as such, "Title
+     Page" means the text near the most prominent appearance of the
+     work's title, preceding the beginning of the body of the text.
+
+     A section "Entitled XYZ" means a named subunit of the Document
+     whose title either is precisely XYZ or contains XYZ in parentheses
+     following text that translates XYZ in another language.  (Here XYZ
+     stands for a specific section name mentioned below, such as
+     "Acknowledgements", "Dedications", "Endorsements", or "History".)
+     To "Preserve the Title" of such a section when you modify the
+     Document means that it remains a section "Entitled XYZ" according
+     to this definition.
+
+     The Document may include Warranty Disclaimers next to the notice
+     which states that this License applies to the Document.  These
+     Warranty Disclaimers are considered to be included by reference in
+     this License, but only as regards disclaiming warranties: any other
+     implication that these Warranty Disclaimers may have is void and
+     has no effect on the meaning of this License.
+
+  2. VERBATIM COPYING
+
+     You may copy and distribute the Document in any medium, either
+     commercially or noncommercially, provided that this License, the
+     copyright notices, and the license notice saying this License
+     applies to the Document are reproduced in all copies, and that you
+     add no other conditions whatsoever to those of this License.  You
+     may not use technical measures to obstruct or control the reading
+     or further copying of the copies you make or distribute.  However,
+     you may accept compensation in exchange for copies.  If you
+     distribute a large enough number of copies you must also follow
+     the conditions in section 3.
+
+     You may also lend copies, under the same conditions stated above,
+     and you may publicly display copies.
+
+  3. COPYING IN QUANTITY
+
+     If you publish printed copies (or copies in media that commonly
+     have printed covers) of the Document, numbering more than 100, and
+     the Document's license notice requires Cover Texts, you must
+     enclose the copies in covers that carry, clearly and legibly, all
+     these Cover Texts: Front-Cover Texts on the front cover, and
+     Back-Cover Texts on the back cover.  Both covers must also clearly
+     and legibly identify you as the publisher of these copies.  The
+     front cover must present the full title with all words of the
+     title equally prominent and visible.  You may add other material
+     on the covers in addition.  Copying with changes limited to the
+     covers, as long as they preserve the title of the Document and
+     satisfy these conditions, can be treated as verbatim copying in
+     other respects.
+
+     If the required texts for either cover are too voluminous to fit
+     legibly, you should put the first ones listed (as many as fit
+     reasonably) on the actual cover, and continue the rest onto
+     adjacent pages.
+
+     If you publish or distribute Opaque copies of the Document
+     numbering more than 100, you must either include a
+     machine-readable Transparent copy along with each Opaque copy, or
+     state in or with each Opaque copy a computer-network location from
+     which the general network-using public has access to download
+     using public-standard network protocols a complete Transparent
+     copy of the Document, free of added material.  If you use the
+     latter option, you must take reasonably prudent steps, when you
+     begin distribution of Opaque copies in quantity, to ensure that
+     this Transparent copy will remain thus accessible at the stated
+     location until at least one year after the last time you
+     distribute an Opaque copy (directly or through your agents or
+     retailers) of that edition to the public.
+
+     It is requested, but not required, that you contact the authors of
+     the Document well before redistributing any large number of
+     copies, to give them a chance to provide you with an updated
+     version of the Document.
+
+  4. MODIFICATIONS
+
+     You may copy and distribute a Modified Version of the Document
+     under the conditions of sections 2 and 3 above, provided that you
+     release the Modified Version under precisely this License, with
+     the Modified Version filling the role of the Document, thus
+     licensing distribution and modification of the Modified Version to
+     whoever possesses a copy of it.  In addition, you must do these
+     things in the Modified Version:
+
+       A. Use in the Title Page (and on the covers, if any) a title
+          distinct from that of the Document, and from those of
+          previous versions (which should, if there were any, be listed
+          in the History section of the Document).  You may use the
+          same title as a previous version if the original publisher of
+          that version gives permission.
+
+       B. List on the Title Page, as authors, one or more persons or
+          entities responsible for authorship of the modifications in
+          the Modified Version, together with at least five of the
+          principal authors of the Document (all of its principal
+          authors, if it has fewer than five), unless they release you
+          from this requirement.
+
+       C. State on the Title page the name of the publisher of the
+          Modified Version, as the publisher.
+
+       D. Preserve all the copyright notices of the Document.
+
+       E. Add an appropriate copyright notice for your modifications
+          adjacent to the other copyright notices.
+
+       F. Include, immediately after the copyright notices, a license
+          notice giving the public permission to use the Modified
+          Version under the terms of this License, in the form shown in
+          the Addendum below.
+
+       G. Preserve in that license notice the full lists of Invariant
+          Sections and required Cover Texts given in the Document's
+          license notice.
+
+       H. Include an unaltered copy of this License.
+
+       I. Preserve the section Entitled "History", Preserve its Title,
+          and add to it an item stating at least the title, year, new
+          authors, and publisher of the Modified Version as given on
+          the Title Page.  If there is no section Entitled "History" in
+          the Document, create one stating the title, year, authors,
+          and publisher of the Document as given on its Title Page,
+          then add an item describing the Modified Version as stated in
+          the previous sentence.
+
+       J. Preserve the network location, if any, given in the Document
+          for public access to a Transparent copy of the Document, and
+          likewise the network locations given in the Document for
+          previous versions it was based on.  These may be placed in
+          the "History" section.  You may omit a network location for a
+          work that was published at least four years before the
+          Document itself, or if the original publisher of the version
+          it refers to gives permission.
+
+       K. For any section Entitled "Acknowledgements" or "Dedications",
+          Preserve the Title of the section, and preserve in the
+          section all the substance and tone of each of the contributor
+          acknowledgements and/or dedications given therein.
+
+       L. Preserve all the Invariant Sections of the Document,
+          unaltered in their text and in their titles.  Section numbers
+          or the equivalent are not considered part of the section
+          titles.
+
+       M. Delete any section Entitled "Endorsements".  Such a section
+          may not be included in the Modified Version.
+
+       N. Do not retitle any existing section to be Entitled
+          "Endorsements" or to conflict in title with any Invariant
+          Section.
+
+       O. Preserve any Warranty Disclaimers.
+
+     If the Modified Version includes new front-matter sections or
+     appendices that qualify as Secondary Sections and contain no
+     material copied from the Document, you may at your option
+     designate some or all of these sections as invariant.  To do this,
+     add their titles to the list of Invariant Sections in the Modified
+     Version's license notice.  These titles must be distinct from any
+     other section titles.
+
+     You may add a section Entitled "Endorsements", provided it contains
+     nothing but endorsements of your Modified Version by various
+     parties--for example, statements of peer review or that the text
+     has been approved by an organization as the authoritative
+     definition of a standard.
+
+     You may add a passage of up to five words as a Front-Cover Text,
+     and a passage of up to 25 words as a Back-Cover Text, to the end
+     of the list of Cover Texts in the Modified Version.  Only one
+     passage of Front-Cover Text and one of Back-Cover Text may be
+     added by (or through arrangements made by) any one entity.  If the
+     Document already includes a cover text for the same cover,
+     previously added by you or by arrangement made by the same entity
+     you are acting on behalf of, you may not add another; but you may
+     replace the old one, on explicit permission from the previous
+     publisher that added the old one.
+
+     The author(s) and publisher(s) of the Document do not by this
+     License give permission to use their names for publicity for or to
+     assert or imply endorsement of any Modified Version.
+
+  5. COMBINING DOCUMENTS
+
+     You may combine the Document with other documents released under
+     this License, under the terms defined in section 4 above for
+     modified versions, provided that you include in the combination
+     all of the Invariant Sections of all of the original documents,
+     unmodified, and list them all as Invariant Sections of your
+     combined work in its license notice, and that you preserve all
+     their Warranty Disclaimers.
+
+     The combined work need only contain one copy of this License, and
+     multiple identical Invariant Sections may be replaced with a single
+     copy.  If there are multiple Invariant Sections with the same name
+     but different contents, make the title of each such section unique
+     by adding at the end of it, in parentheses, the name of the
+     original author or publisher of that section if known, or else a
+     unique number.  Make the same adjustment to the section titles in
+     the list of Invariant Sections in the license notice of the
+     combined work.
+
+     In the combination, you must combine any sections Entitled
+     "History" in the various original documents, forming one section
+     Entitled "History"; likewise combine any sections Entitled
+     "Acknowledgements", and any sections Entitled "Dedications".  You
+     must delete all sections Entitled "Endorsements."
+
+  6. COLLECTIONS OF DOCUMENTS
+
+     You may make a collection consisting of the Document and other
+     documents released under this License, and replace the individual
+     copies of this License in the various documents with a single copy
+     that is included in the collection, provided that you follow the
+     rules of this License for verbatim copying of each of the
+     documents in all other respects.
+
+     You may extract a single document from such a collection, and
+     distribute it individually under this License, provided you insert
+     a copy of this License into the extracted document, and follow
+     this License in all other respects regarding verbatim copying of
+     that document.
+
+  7. AGGREGATION WITH INDEPENDENT WORKS
+
+     A compilation of the Document or its derivatives with other
+     separate and independent documents or works, in or on a volume of
+     a storage or distribution medium, is called an "aggregate" if the
+     copyright resulting from the compilation is not used to limit the
+     legal rights of the compilation's users beyond what the individual
+     works permit.  When the Document is included an aggregate, this
+     License does not apply to the other works in the aggregate which
+     are not themselves derivative works of the Document.
+
+     If the Cover Text requirement of section 3 is applicable to these
+     copies of the Document, then if the Document is less than one half
+     of the entire aggregate, the Document's Cover Texts may be placed
+     on covers that bracket the Document within the aggregate, or the
+     electronic equivalent of covers if the Document is in electronic
+     form.  Otherwise they must appear on printed covers that bracket
+     the whole aggregate.
+
+  8. TRANSLATION
+
+     Translation is considered a kind of modification, so you may
+     distribute translations of the Document under the terms of section
+     4.  Replacing Invariant Sections with translations requires special
+     permission from their copyright holders, but you may include
+     translations of some or all Invariant Sections in addition to the
+     original versions of these Invariant Sections.  You may include a
+     translation of this License, and all the license notices in the
+     Document, and any Warrany Disclaimers, provided that you also
+     include the original English version of this License and the
+     original versions of those notices and disclaimers.  In case of a
+     disagreement between the translation and the original version of
+     this License or a notice or disclaimer, the original version will
+     prevail.
+
+     If a section in the Document is Entitled "Acknowledgements",
+     "Dedications", or "History", the requirement (section 4) to
+     Preserve its Title (section 1) will typically require changing the
+     actual title.
+
+  9. TERMINATION
+
+     You may not copy, modify, sublicense, or distribute the Document
+     except as expressly provided for under this License.  Any other
+     attempt to copy, modify, sublicense or distribute the Document is
+     void, and will automatically terminate your rights under this
+     License.  However, parties who have received copies, or rights,
+     from you under this License will not have their licenses
+     terminated so long as such parties remain in full compliance.
+
+ 10. FUTURE REVISIONS OF THIS LICENSE
+
+     The Free Software Foundation may publish new, revised versions of
+     the GNU Free Documentation License from time to time.  Such new
+     versions will be similar in spirit to the present version, but may
+     differ in detail to address new problems or concerns.  See
+     `http://www.gnu.org/copyleft/'