1All you need to know when hacking (modifying) GNU libtextstyle or when building
2it off the git repository.
3
4
5Requirements
6============
7
8You will need reasonably recent versions of the build tools:
9
10  * A C compiler; on Cygwin or mingw also a C++ compiler. Such as GNU GCC.
11    + Homepage:
12      https://gcc.gnu.org/
13
14  * GNU automake 1.13 or newer
15    + Homepage:
16      https://www.gnu.org/software/automake/
17
18  * GNU autoconf
19    + Homepage:
20      https://www.gnu.org/software/autoconf/
21
22  * GNU m4
23    + Homepage:
24      https://www.gnu.org/software/m4/
25
26  * GNU texinfo
27    + Homepage:
28      https://www.gnu.org/software/texinfo/
29
30  * Perl
31    + Homepage:
32      https://www.perl.org/
33
34  * TeX (for making the doc in .dvi, .ps or .pdf format)
35    + Homepage:
36      https://tug.org/teTeX/
37
38  * Either an internet connection or a recent copy of GNU gnulib.
39    + Homepage:
40      https://www.gnu.org/software/gnulib/
41
42  * GNU tar (for creating distributable tarballs)
43    + Homepage:
44      https://www.gnu.org/software/tar/
45
46  * GNU Wget
47    + Homepage:
48      https://www.gnu.org/software/wget/
49
50And, of course, the packages listed in the DEPENDENCIES file.
51
52
53Building off the git repository
54===============================
55
56Access to the git repository is described at
57  https://savannah.gnu.org/git/?group=gettext
58
59After fetching the sources from the repository, go into the 'libtextstyle'
60directory, peek at the comments in autogen.sh, then run "./autogen.sh";
61then you can proceed with "./configure" as usual.
62
63
64Submitting patches
65==================
66
67Patches should be sent to bug-gettext@gnu.org, the bug/feature mailing
68list.  You can subscribe to the mailing list, or see the list
69archives, by following links from
70https://savannah.gnu.org/mail/?group=gettext .
71
72To email a patch you can use a shell command like 'git format-patch
73-1' to create a file, and then attach the file to your email.
74
75Changes you commit should contain the log entries in the commit message.
76For the style of a ChangeLog entry, see the "Change Logs" section of
77the GNU coding standards:
78
79  https://www.gnu.org/prep/standards/html_node/Change-Logs.html
80
81
82Testing
83=======
84
85The unit tests don't cover much of the functionality.
86
87To test the output on various terminal emulators, use the --color=test
88option on the 'color-hello' or 'color-filter' program.
89
90To test the signal handling, use the 'color-filter' program: run
91  yes | ./filter '.*'
92and exercise the various signals.
93