--- /dev/null
+All you need to know when hacking (modifying) GNU gettext or when building
+it off the CVS.
+
+
+Requirements
+============
+
+You will need reasonably recent versions of the build tools:
+
+ * A C compiler; on Cygwin or mingw also a C++ compiler. Such as GNU GCC.
+ + Homepage:
+ http://gcc.gnu.org/
+
+ * GNU automake
+ + Homepage:
+ http://www.gnu.org/software/automake/
+
+ * GNU autoconf
+ + Homepage:
+ http://www.gnu.org/software/autoconf/
+
+ * GNU m4
+ + Homepage:
+ http://www.gnu.org/software/m4/
+
+ * GNU bison
+ + Homepage:
+ http://www.gnu.org/software/bison/
+
+ * GNU gperf
+ + Homepage:
+ http://www.gnu.org/software/gperf/
+
+ * GNU texinfo
+ + Homepage:
+ http://www.gnu.org/software/texinfo/
+
+ * GNU emacs or XEmacs
+ + Homepage:
+ http://www.gnu.org/software/emacs/
+ http://www.xemacs.org/
+
+ * Perl
+ + Homepage:
+ http://www.perl.org/
+
+ * TeX (for making the doc in .dvi, .ps or .pdf format)
+ + Homepage:
+ http://tug.org/teTeX/
+
+ * Either an internet connection or a recent copy of GNU gnulib.
+ + Homepage:
+ http://www.gnu.org/software/gnulib/
+
+And, of course, the packages listed in the DEPENDENCIES file.
+
+
+Building off the CVS
+====================
+
+Access to the CVS is described at http://savannah.gnu.org/cvs/?group=gettext .
+
+After fetching the sources from the CVS, peek at the comments in autogen.sh,
+then run "./autogen.sh"; then you can proceed with "./configure" as usual.
+