Modification conditions

It is possible that you need to produce a document processing system based on standard L^ATEX but with functionality that cannot be implemented by using the approved configuration files and complying with the restriction on the code that is allowed in them. In other words, you may need a system which is sufficiently distinct from Standard L^ATEX that it is not feasible to do this simply by using the configuration options we provide or by producing new classes and packages.

If you do produce such a system then, for the reasons described above, you should ensure that your system is clearly distinguished from Standard L^ATEX in every possible way, including the following.

1.

Give your system a distinguished name, such as NS-TeX, which clearly distinguishes it from L^ATEX.

2.

Ensure that it contains no file with a name the same as that of a file in the standard distribution but with different contents. (If this is not possible then you must:

• ensure that files from the non-L^ATEX system cannot be accidentally accessed whilst using a standard L^ATEX;
• ensure that each file from the non-L^ATEX system clearly identifies itself as a non-L^ATEX file on the terminal and in the log file.)

3.

Ensure that the method used to run your system is clearly   distinct from that used to run Standard L^ATEX; e.g. by using a command name or menu entry that is clearly not latex (or LaTeX etc).

4.

Ensure that, when a file is being processed by your system, the use of non-standard L^ATEX is clearly proclaimed to the user by whatever means is appropriate.

5.

Ensure that what is written at the beginning of the log file clearly shows that your system has been used, and that it is not Standard L^ATEX. See the file cfgguide.tex for how to achieve this.

6.

Clearly explain to users that bug reports concerning your system should not be sent to the maintainers of Standard L^ATEX.