Use of TeX in CIFs
------------------

CIF allows the use of pure TeX in text-based data items.
A text field delimited by semicolons (;) may contain
pure TeX code if the opening semicolon is followed 
immediately by the tokens %T<newline>
e.g.

_publ_section_comment
;%T
This text is written in \TeX{}
and may contain any {\bf Plain} \TeX{}\par

It is assumed that authors using such constructs are
{\it \TeX{}perts}!

The main advantage of using \TeX{} in CIFs is for setting
mathematical type, {\it e.g.} 
$$ q =  4\pi\sin \left({\theta\over \lambda}\right) \eqno(1)$$
In the majority of {\it Acta Cryst. C}/{\it E} papers, the need
 for such mathematical typesetting is unlikely, or may adequately
 be represented using CIF syntax. 
% sin\q/\l in CIF format
;

The current release of publCIF is unable to handle the use of 
TeX in CIF data items in the same way that it handles text in
CIF syntax, i.e. it will not include it in the Preprint.

However, for convenience, this version of publCIF enables you 
to 'TeX' and preview such TeX items:

1) In the CIF window, select the text to be 'TeXed' (using 
the mouse).
2) Press 'F5'

This will write the selected text to a temporary file and then 
'TeX' the file and preview the resulting .dvi file.

This is achieved by running an external script or batch file -
'publtex' or 'publtex.bat' (depending on the operating system),
located in the /xpublcif/py/ folder.

This script/batch file should simply execute whatever commands
you usually use to 'TeX and preview'. As this version of publCIF 
makes no attempt to identify the relevant commands for your 
system, you will most probably need to be edit the script/batch 
file to ensure that the appropriate TeX and DVI commands are passed 
to the temporary files.

Please see the script/batch file (publtex) in the 
/xpublcif/py/ folder for more information. 

IMPORTANT NOTES:

1) The use of TeX in this manner for Acta C and E papers 
should be avoided if possible as it can significantly increase 
manuscript processing time. 

2) publCIF is NOT a TeX editor/parser, so it is up to the author
to make sure that the TeX is both interpretable and portable
(the 'Ctrl+T' function is not interactive and 
does not report errors - BUT it could !:).

3) Only PLAIN TeX is supported (not LaTeX etc.) 
and any local macro definitions must
be provided within the data item 







