> <\body> to > A document can be exported to using . \ In the case of certain journal styles like or , the user should also make sure that the appropriate style files can be found by , when compiling the result of the conversion. Please consult your documentation for how to do this; one solution which usually works is to put the style file in the same directory as your file. Notice that the exportation of a document with images may cause the creation of additional image files. If your destination file is called , these files are named , >, and they are stored in the same directory. In particular, all pictures drawn with the editor and all images which are not already in format will be converted to encapsulated files. In order to ensure that the generated document compiles, style files and packages or macros with no equivalents are either ignored or replaced by a reasonable substitute. The precise behaviour of the converter may be customized using several user preferences in the LaTeX> menu: <\description-long> >This option (which is set by default) tells to replace style files with no equivalents by the style. Furthermore, all additional style packages are ignored. In case you know how to , you might wish to create equivalents of those journal styles which you use often. Similarly, you might wish to create a style package with your own macros together with its counterpart. In both cases, you might want to disable the style replacement option. >By default, all macros are expanded until they admit direct counterparts. Primitives with no counterparts (like graphics or trees) are ignored. Moreover, in order to convert certain frequently used macros like or , may put additional definitions in the preamble. In some cases, the user may wish to keep unrecognized macros in their unexpanded form. For instance, this may be convenient if you want to import the generated document back into . Another typical situation is when you defined additional macros in a style package. In these cases, you may disable to macro replacement option. Of course, any missing macro definitions may result in errors during the compilation. >When your document or its preamble contains macro definitions, then will convert these macro definitions into macro definitions and keep all macro applications in their unexpanded forms. This allows you to preserve as much structure of your document as possible. When enabling the option, all macro definitions in your document will be ignored and all macro applications will be expanded. >In order to produce stand-alone files whenever possible, it is assumed that you generateyour bibliographies from within . When exporting to , the generated bibliography will be directly included into your file. In some cases however, the user might wish to regenerate the bibliography from the and the bibliography files, using >. In this case, you need to enable the option. >Certain macros like have no direct analogues. For a certain number of frequently used macros, automatically generates macro definitions in the preamble of the target file. This allows you to preserve as much structure as possible of your document, which is for instance useful if you import the document back into . However, certain journals instruct authors to refrain from the definition of additional macros in the preamble. When disallowing for macro definitions in preambles, will automatically expand all corresponding macro applications. document into code>When this option is set, a copy of the document is appended to the export in a lossless kind. This allows to re-import the document with as few conversion artifacts as possible . This option defines the behavior of the converter with respect to character encoding. There are three possible choices: <\description> This will generate document with the package loaded. If for any reason you don't want to rely on , you should consider other options. Keeps accented characters ``as is''. This can be achieved by allowing to put additional catcode definitions into your preamble. This provides a good trade-off between readability (accented characters are kept in an 8 bit charset) and simplicity (you don't need the package). This will generate pure characters, using plain sequences to compose non- symbols. Sometimes, the converter does not produce a satisfactory file even after some tinkering with the above preferences. The most frequent problem concerns bad line breaks. Occasionally, certain document fragments are also better converted by hand. In order to minimize the need for corrections in the generated file (which would be lost when re-exporting the source file after some modifications), provides a mechanism to specify manual conversions to in the source file: using and , you may force certain document fragments to appear only in the source file or the target. For instance, assume that the word \Pblauwbilgorgel\Q is hyphenated correctly in the source, but not in the conversion. Then you may proceed as follows: <\enumerate> Select \Pblauwbilgorgel\Q. Click on to make the text \Pblauwbilgorgel\Q -specific. Click on . Type the latex code with the correct hyphenation. Press to activate the -specific text. In a similar fashion, you may insert -specific line breaks, page breaks, vertical space, style parameter modifications, etc. You may also force arbitrary content to be exported as an image using . >