<\body> to > In order to import a document into , you may use . Don't forget to save the file under a new name with the extension, if you want to edit it. As explained in the introduction, the conversion of documents into is more problematic than conversions the other way around. As long as you restrict yourself to using the most common commands, the conversion process should not give rise to any major difficulties. However, as soon as your documents contain ``weird macro definitions'', then the converter may get confused. We also notice that is currently unable to convert style files and no plans exist to enhance the converter in this direction. There are two major reasons for documents to get imported in an inappropriate way, and which can easily be corrected by the user. First of all, the parser may get confused because of some exotic syntactic construct. This typically happens in presence of catcodes or uncommon styles of macro definitions. Sometimes, the parser may also be mistaken about the current mode, in which case text gets parsed as a mathematical formula or . In both cases, the imported document usually becomes ``weird'' at a certain point. In order to solve the problem, we suggest you to identify the corresponding point in the source file and to make an appropriate change which avoids the parser of getting confused. A second common error is that certain macros are not recognized by the converter, in which case they will appear in red. This typically happens if you use one of the hundreds additional packages or if you defined some additional macros in another document. In the case when the troublesome macro occurs only a few times, then we suggest you to manually expand the macro in the source file before importation. Otherwise, you may try to put the definitions of the missing macros in the preamble of the document. Alternatively, you may create a small style package with counterparts for the macros which were not recognized. <\initial> <\collection>