Menu File New Open Save Document Manager Delete Close Import XML ReImport Export XML Export Options Recent ... Import RTF Import from URL Import Text Export Text Multi-Import Multi-Export Exit |

### Menu File

> This menu item includes sub items for management of documents in the CLaRK system. The documents that the system recognizes are XML well-formed documents. These documents can be divided into two kinds. The documents of the first kind are outside of the system. The system can work with these documents if they are imported inside the system. The external documents must have one of the following character encodings: ASCII, UNICODE (UTF-8), UNICODE (UTF-16BE) or UNICODE (UTF-16LE). The documents of the second kind are imported into the system and stored in an internal representation. When a document is processed inside the system, it has to be connected with a document type definition (DTD). The DTD has to be compiled in an internal representation before being assigned to the document. The document loaded in the active view of the system is called a current document.

> Sub-Menus:

> ### New

> A default shortcut Ctrl+N
> An icon on the toolbar

> Choosing this item, the user creates a new empty document. First, a menu for choosing a DTD appears. The user can create a document with respect to one of the DTDs compiled into the system. If the appropriate DTD is not compiled, then the user has to close the dialog and compile the required DTD. After choosing the DTD, a new document, containing only the root element with empty content is created. In most cases this document will not be valid.

> ### Open

> A default shortcut Ctrl+O
> An icon on the toolbar

> By choosing this item, the user opens document(s) saved in the internal document database of the system. A Document Manager window is opened on the screen.

> The user has to point out to a certain document and click the Open button. Then the corresponding document is loaded into the system. The internal documents are stored together with information for their DTD. If their DTD is compiled in the system, then they are opened with respect to it. If the DTD is deleted (for some reason) from the DTD database of the system, the user is asked to choose a DTD from the available ones.

> The user can choose document(s) to open in two modes:

> - selecting one or more documents from a list of all internal documents. It is an option provided by the Document Manager;
> - the internal documents are arranged in hierarchically organized groups. The user can select document(s) from the current group.

> If the Cancel button is chosen, the manager window closes and no document is loaded into the system.

> The user can also open a document in the manager by performing a double click on a certain document name either in the list of all documents or in the list of the current group.

> Note that Open menu does not open text files. If the you want to load an XML document from a text file, then choose Import XML item.

> ### Save

> A default shortcut Ctrl+S
> An icon on the toolbar

> By choosing this item, the user saves the current document in the internal document database of the system. The user has to give a name to the document in a dialog box. Optionally the user can specify a document group in which the document should be included. Then the system tries to save the document. If there exists a document with the specified name, the user is asked to confirm the overwriting of the document or to choose a new name.

> ### Document Manager

> This component is responsible for the management of the internal documents in the CLaRK System.

> The Internal Documents Database is an essential part of the CLaRK system. It is the place where all documents saved in the system are stored. The main reason for maintaining such a database is that the system can work only with well-formed XML documents and having them stored in an internal format prevents the system from malfunctioning because of incorrect data. This database protects the documents from being corrupted. In addition, keeping the documents "invisible" for other applications allows saving additional system specific information with them. The interface of the documents with external applications can be done by import/export operations. A successfully imported document in the system has a guaranteed well-formed structure. An exported document from the system is always a well-formed XML document stored in a file, which can be used by other XML oriented applications.

> The Internal Document Database represents a set of repositories, called Corpora which contain the saved documents in the system. The different corpora are identified by unique (user supplied) names. Each corpus contains a set of documents which are stored independently from the documents of other corpora. No documents can be saved outside a corpus. The documents within a corpus are identified by unique names, i.e. no two documents can have the same name. If it is necessary that two or more documents should have the same name, they must be stored in different corpora.

> The possible operations on corpora are:

> - Creating a new corpus

>   The user supplies a new corpus name which hasn't been used yet for another corpus.

> - Removing a corpus

>   The user selects a corpus to be removed. All documents contained in the selected corpus are removed as well. The removal is preceded by a confirmation warning message. There is one system protected corpus ('Root') which can not be removed. It is always presented in the system and it is used as a default corpus.

> - Renaming a corpus

>   The user can rename an existing corpus by supplying a new unique name. The 'Root' corpus is protected from renaming.

> Corpora are document containers only, so it is not possible a corpus to contain another corpus. Each corpus has its own internal logical structure which facilitates the maintenance of many documents at the same time. The documents within a corpus are organized in groups. Each group can contain a set of documents, as well as a set of subgroups. Each group is identified by an unique name within the group in which it is included, but not necessary unique for the containing corpus. The supported operations on groups are: creating a new group or a subgroup of a group; renaming a group and removing a group. The user can include or exclude documents in a group.

> The groups are logical unions of documents which do not impact physically the documents themselves. This means that if a document is removed (excluded) from a group, the document itself is not deleted from the database, but just excluded from this union. Thus the same document can be included in more than one group, as well as a document can be included in none.

> Note: technically said, the groups contain not documents, but references to documents. In this way, if a document is presented in more than one group, the document itself is not multiplied for each containing group, but the single instance is referred by links from each group entry.

> Observing the documents in the Internal Documents Database can be done in three views:

> - by logical tree structure - the hierarchical structure is visualized in a way that on the topmost level the set of available corpora is shown and under each of them the groups tree structure is visualized. Selecting a point in the hierarchy causes a visualization of its content in a separate window.
> - by all documents in a corpus - all documents which are presented in a certain corpus are represented in a table, showing the document names and some other information. The user can switch to another corpus in order to see its content in a table. In this view the groups information can not be observed.
> - by all documents in the whole database - all documents from all corpora are represented in one table. The information shown in the table is the same as the one from the previous view, plus a source corpus name for each document.

> The main dialog is Entry Manager with some additional functionality buttons. The manager keeps records of all documents saved in the system. The documents are contained in system of document groups which are arranged in trees, similar to the directory structure. On the top of each document groups hierarchy there stands a node, which represents thecorpus container. Thus the topmost level of the hierarchy of the Internal Documents database consists of corpora nodes only. From these nodes, the hierarchies of groups begin.

> Each corpus contains one system reserved group, named SYSTEM. It contains documents for special purposes in the system. This group contains the following system protected sub-groups:

> - Results - This group contains a sub-group for each tool in the system. Each such group stores the results from the application of the tools by default. The internal structure of each such tool group is user manageable.
> - Queries - This group contains a sub-group for each tool in the system. These groups store the query documents for each tool (a query document includes all the settings for the tool in order to it to be applied without additional data). The internal structure of each tool group is again user manageable. The documents included here must have certain system DTDs and must be valid according to them.

> None of the above groups can .be deleted or renamed by the user.

> Here follows one example picture of the Document Manager window:

> The By Groups view of the manager window consists of two main parts:

> 1. The panel on the left. It contains a tree representation of the documents hierarchy: Root, SYSTEM, Queries, etc. When the user selects a node in this tree, the content of the corresponding group or corpus is loaded in the component on the right side.
> 2. Current group monitor. This is the panel situated on the right side of the window. It is a list with the content of the currently selected group in the tree. The list components, which are in blue color, are sub-groups. The other ones are the entries included in this group. They are colored in black or red, depending on whether they are valid or not, according to their DTDs. The user can sort all the entries in a group by clicking on the Name column of the table header. It is possible to rearrange the entries in a group by simply using drag-and-drop technique, i.e. pressing a document and moving upwards or downwords until the desired position is reached.

> There are seven buttons which can be used for manipulation of the content of the current group:

> - New Group - creates a new sub-group of the current one. The user is asked to give a name for it;
> - Remove - removes the selected documents and/or groups from the list. The removal is preceded by a confirmation message. If the selection includes sub-groups, they are also removed with their entire contents.
> - Rename - changes the name of the selected document or group from the list.
> - Copy - makes a copy of the selected document from the list with a different name supplied by the user.
> - Add Document - gives a list of all documents which are not presented in the current group. The user is expected to choose one or more documents to be included in the current group.
> - Delete! - this function can be used for removing documents from the internal documents database. It can be applied only to single documents, not to whole groups. Groups are excluded from any selections. The removal of documents is preceded by a confirmation message. The documents to be removed, are excluded from all the groups they may belong to.
> - Apply - this function is used when applying saved tool queries. For details about the predefined tool queries see section XML Tool Queries. The user can choose one or more query documents to be applied. This is performed by selecting entries from the right panel. The "Apply" button is enabled only if the selected documents are queries. Pressing the button, the MultyQuery Tool manager opens and all the selected queries are inserted automatically.

> Navigation in the group structure can be made also in the panel on the right. When the user wants to see the content of a certain sub-group of the current group, s/he just has to perform a double click on the desired sub-group name. This will change the current group to the new one. This represents the movement from a group to a sub-group. The movement in the other direction is also possible. For each document group (excluding the Root), a special sub-group is included, named: ". .". By performing a double click on it, similarly to most file systems, the current group is changed to its parent one.

> The Document Manager also provides two other views of the internal documents:

> - All Documents in a Corpus

>   This view shows all documents within a single corpus in a table. The user can control the current corpus by selection in Choose a Corpus field.

> - All Documents in the System

>   This view shows all documents from all corpora in one table.

> From now on, these two view will be described together as they share many common features.

> The content of the tables in these views contain the following information about the documents:

> - Corpus Name (only for the second view here) - the corpus in which the document is contained;
> - Name - the name of the document;
> - Time - the date and the time of the last document modification;
> - Status - if the document represents a tool query, the corresponding tool name;
> - DTD - the DTD assigned to the document;
> - Validity status - whether the document is valid according to its DTD. The invalid status can be detected by the red color of the table entry.

> The documents in the table can be manipulated by using the right mouse button. Having selected a document or a set of documents and performed a right-mouse click, the following functions menu appears:

> - Info - This item shows the following information about the selected documents:
>   - document name;
>   - document size (in characters);
>   - document's dtd name;
>   - validity status of the document;
>   - group(s) in which the document is included.

> - Add In Group... - This item shows a dialog with the hierarchical structure for the groups in the system and the user can choose a group in which to place the selected files.
> - Delete! - deletes the selected document(s) (see above);
> - Rename - renames the selected document (see above);
> - Copy - copies the selected document (see above);
> - Change DTD - changes the DTD assignments of the selected documents.

> Here is one example view of all internal documents from corpus Root in CLaRK:

> ### Delete

> By choosing this item, the user deletes document(s), saved in the internal document database of the system. A Document Manager window is opened on the screen.

> The user has to point out to a document (or a set of documents) and click the Remove button. Then a confirmation dialog appears. If the user clicks on the Yes button, the chosen document(s) is(are) permanently deleted from the database. If the user clicks on the No button the document(s) is(are) not deleted.

> Similarly to the "Open" function, the user can choose documents in two modes: from all documents or from a certain group. When documents are removed from the list of all documents, the groups they belong to are also updated.

> The user can also delete a document in the manager by performing a double click on a certain document name either in the list of all documents or in the list of the current group.

> ### Close

> A default shortcut Ctrl+F4

> By choosing this item, the user closes the current document and all views of it and removes it from the memory.

> If this is the only view of the current document and the document has been edited, then the user is asked whether he/she wants to save the changes.

> When the view is closed, if there is at least one more view, loaded in the system, the previous active view becomes a current view. If there is no more documents, the system blank view appears.

> ### Import XML

> An icon on the toolbar

> By choosing this item, the user loads a text file containing an XML document within the system. A standard dialog for choosing a file appears. The user has to specify the name of the file to load and its character encoding in Files of type: choice box. The possible encodings for files are: ASCII, UNICODE (UTF-8), UNICODE (UTF-16BE) or UNICODE (UTF-16LE). Then the user is asked to choose a DTD from the DTD database of the system. If the document contains a DTD, the user is asked which one to be used during parsing/validation.

> > Remark: If a document is opened in ASCII format (and it is sure it is an ASCII file) and in the system it contains different symbols from the expected ones, the possible problems are two:

> > 1. Inappropriate system font (for details see Options/Fonts);
> > 2. Inappropriate character encoding converter from ASCII to Unicode (for details see Options/Encoding Correction).

> The system tries to parse the document. If the document is well-formed, then it is parsed into the internal representation. The system creates a view of the document, validates the document and if the document is not valid with respect to the chosen DTD, a list of errors is printed in the error window. A description of all validation errors can be found in Validation error messages section.

> If the document is not well-formed, then the system reports an error. A detailed description of all parsing errors can be found in Parse error messages section. The errors of this kind have to be repaired within an external to the system editor. The error message reported by CLaRK system can help the user to find the error in the document.

> ### ReImport

> A default shortcut Ctrl+R

> When the user tries to load a document, which is not well-formed, an error message is reported by the CLaRK system and the user has to edit the document outside the CLaRK system. Then he/she would like to load the same document. In order not to go throughout the whole process of choosing the file and so on, the user can use ReImport item to load the last chosen document.

> The system tries to parse the document. If the document is well-formed, it is parsed into the internal representation. The system creates a view of the document, validates the document and if the document is not valid with respect to the chosen DTD, a list of errors is printed in the error window. A description of all validation errors can be found in Validation error messages section.

> If the document is not well-formed, then the system reports an error. A detailed description of all parsing errors can be found in Parse error messages section. The errors of this kind have to be repaired with an editor outside the system. The error message reported by CLaRK system can help the user to find the error in the document.

> ### Export XML

> An icon on the toolbar

> By choosing this item, the user can save the current document into a text file outside the system. A standard dialog for choosing a file appears. The user has to specify the name of the file which will contain the document and the character encoding of the exported text in Files of type: choice box. The possible encodings for files are: ASCII, UNICODE (UTF-8), UNICODE (UTF-16BE) or UNICODE (UTF-16LE). If the files already exist the user is asked whether he/she wants to overwrite it.

> > Remark: If a document is exported in ASCII format but the content of the output file is not comprehensible for other programs or even for the CLaRK System, then the problem can be in an inappropriate character encoding converter from Unicode to ASCII (for details see Options/Encoding Correction).

> The text in the file can be formatted according to the layout specified for the DTD of the document or to the current view's layout. These settings can be specified in section Export Options.

> ### Export Options

> By choosing this item, the user can specify the information to be added in the external file.
> Here is a screen shot of the dialog :

> The dialog contains the following sections:

> Layout source options

> - None - by selecting this radio button, no information about the document layout is added in the file and all tags are written without line breaks in-between.
> - DTD Layout - by selecting this radio button, the DTD layout of the internal document is preserved in the external file.
> - Current Document Layout - by selecting this radio button, the text layout of the current document view is preserved in the external file.

> Export options

> - Export Line Offsets - by selecting this checkbox, the leading offsets of the tags in the document are printed in the external file, depending on the chosen layout.
> - Spaces Count per Generation - determines the amount of space characters which will be written before the tags for each generation. Here each generation is a set of nodes with equal depth in the document tree structure. The total count of leading spaces before the tags is: <generation_depth> x <spaces per generation>
> - Print DTD in Document - determines whether the DTD of the document will be exported as well in the heading part of the exported file.
> - Normalize whitespace in invisible text nodes - this option enables encoding of the whitespace characters with numerical entities when they appear in text nodes without visible characters in their content. This prevents their further removal by XML parsers assuming that it is a garbage or layout data. This can be crucial for such text nodes situated between tags.

> ### Recent ...

> This option gives a quick access to documents which were used recently in the system. The system keeps track of up to seven documents back. By choosing an item here, a document (if it is still available) is immediately opened in the editor. The Recent ... section is split into two sections:

> 1. Internal Documents

>    It stores the names of the last seven documents which have been opened from the Internal Documents database in the system editor.

> 2. External XML

>    It stores the names of the last seven documents which have been imported from external XML files in the system editor.

> ### Import RTF

> By choosing this item, the user loads a RTF file within the system. A standard dialog for choosing a file appears. The user is asked to point to the RTF file to load. The expected file encoding is ASCII as it is specified in the RTF specification. The result from importing an RTF file is an XML document whose structure follows the TEI.2 DTD. During importing the user is asked to point to a DTD name where the TEI.2 DTD is stored. If there is no such DTD available, any other DTD can be selected and the result document will not be valid (which is not a problem).

> #### RTF to XML Conversion

> Not all the data from an RTF document is detected and transferred into XML. From the structures which are not recognized in the RTF file only the text content is taken. The types of data for which the system is aware are: heading information (title, author, keywords, creation/last modification date and time), structural information (headers, paragraphs, sections) and text layout information (bold, italics, underlined). Here follows the correspondence table from RTF to XML (TEI.2).

> RTF Heading Data | XML(TEI.2) Corresponding Data
> title | TEI.2 > teiHeader > fileDesc > titleStmt > title
> author | TEI.2 > teiHeader > fileDesc > titleStmt > author
> operator | TEI.2 > teiHeader > fileDesc > titleStmt > respStmt > name
> company | TEI.2 > teiHeader > fileDesc > publicationStmt > publisher
> category | TEI.2 > teiHeader > encodingDesc > classDecl > taxonomy > category
> keywords | TEI.2 > teiHeader > profileDesc > textClass > keywords > term
> creation date/time | TEI.2 > teiHeader > profileDesc > creation > date / time
> words count | TEI.2 > teiHeader > fileDesc > sourceDesc > bibl > extent > XXX words
> characters count | TEI.2 > teiHeader > fileDesc > sourceDesc > bibl > extent > XXX characters
> characters count incl. whitespaces | TEI.2 > teiHeader > fileDesc > sourceDesc > bibl > extent > XXX characters with ws.
> Structure & Layout Data | XML Tags
> paragraph | <p> ... </p>
> section | <div> ... </div>
> header | <head> ... </head>
> footer | <trailer> ... </trailer>
> bold | <hi rend="Bold"> ... </hi>
> italics | <hi rend="Italics"> ... </hi>
> underlined | <hi rend="Underlined"> ... </hi>

> Remark: The notation in the table above: "xxx > yyy > zzz" stands for the following XML markup: "<xxx><yyy><zzz></zzz></yyy></xxx>"

> The system supports Unicode encoded RTF documents as well as 23 different ASCII text encodings. If no ASCII encoding is detected, the system defaults to US Codepage (OEM-437).

> ### Import from URL

> By choosing this item, the user can load an XML document from an URL address. The user should write: URL address, file encoding: ASCII, UNICODE (UTF-8), UNICODE (UTF-16BE) or UNICODE (UTF-16LE). Then the user is asked to choose a DTD from the DTD database of the system. If the document contains a DTD, this DTD is ignored during the parsing.

> > Remark: If a document is opened in ASCII format (and it is sure it is an ASCII file) and in the system it contains different symbols from the expected ones, the possible problems are two:

> > 1. Inappropriate system font (for details see Options/Fonts);
> > 2. Inappropriate character encoding converter from ASCII to Unicode (for details see Options/Encoding Correction).

> The system tries to parse the document. If the document is well-formed, then it is parsed into the internal representation. The system creates a view of the document, validates the document and if the document is not valid with respect to the chosen DTD, a list of errors is printed in the error window. A description of all validation errors can be found in Validation error messages section.

> If the document is not well-formed, then the system reports an error. A detailed description of all parsing errors can be found in Parse error messages section. The errors of this kind have to be repaired with an editor outside the system. The error message reported by CLaRK system can help the user to find the error in the document.

> Here is a screen shot of the dialog :

> ### Import Text

> This item allows the user to import pure text documents (without XML markup) in the system. The input documents can be encoded in ASCII or Unicode. The text from the input file is represented as one big text node. For compatibility, the CLaRK System puts an auxiliary tag (textdata) as root of the document and the text node is its only child. This auxiliary tag has an attribute source which keeps information about the location of the source file for this text. Having chosen this item, the user is asked to point to a DTD for the new document.

> ### Export Text

> This item allows the user to export the text content of XML document as pure text. The text is serialized in a file without any preprocessing like the substitution of special control symbols ('<', '>', '&', etc.) with entities and others. Only the text nodes are printed in the order they appear in the document. All other data is ignored. The encoding of the text data can be either ASCII or Unicode.

> ### Multi-Import

> This tool is used to perform a multiple Import XML operations, i.e. to import XML documents from external files into the internal document database of the system. The documents importing is done without opening them in the system editor. The imported documents are automatically saved in a corpus of the internal database and they are included (optionally) in a certain group.

> Here follows a view of the Multi-Import Manager window:

> The manager dialog window contains a list of all documents to be imported (initially it is empty) and some other options controlling the document processing. The components of the dialog are:

> - Default DTD for documents - this component suggests a DTD for the documents selected for importing in the system. This chooser is default, because the user can specify a DTD for each document separately and if the DTD of the document is not specified, the system takes the DTD from here. The initial selected value in this chooser is the last DTD used in the system.
> - Send documents to: - This option allows the user to specify a location in the internal documents database where the imported documents to be stored. This item is disabled if item Save Documents is not selected.
> - Use directory "valid" - This item, if selected, moves all files which are valid according to the corresponding DTD to a sub-directory "valid" of the selected directory in field Valid/Well-formed Directory. If such a directory does not exist, the user is prompted to confirm its creation. If the user cancels, this option is disabled.
> - Use directory "well-formed" - This item, if selected, moves all files which are well-formed but not valid according to the corresponding DTD to a sub-directory "well-formed" of the selected directory in field Valid/Well-formed Directory. If such a directory does not exist, the user is prompted to confirm its creation. If the user cancels, this option is disabled.
> - Valid/Well-formed Directory - This field determines the base directory in which sub-directories "valid" and "well-formed" will be created/used. This information is strongly connected with the usage of the previous two options. If none of them is selected, this field is disabled. When it is enabled, the user can use button Change Directory to select a new base directory.
> - Documents Preview Table - this component shows all documents which will be imported in the system. It is a table with four columns:
>   1. File Name

>      This is a list of all files to be imported with their full directory paths. This column is not editable.

>   2. DTD Name

>      This column assigns a DTD to each document to be imported. By clicking on each cell, a list of all DTDs in the system appears. If for a document there is no DTD selected, the system takes the default selected DTD (field Default DTD for documents).

>   3. Document Name

>      This column determines the internal name, under which the document will be saved in the system. This column is editable and the user can select an arbitrary name for each document. If a name is painted in red, this means that the selected name is already used by another document. The behaviour of the processing component for such documents is determined by field Overwrite.

>   4. Encoding

>      This column determines which supported character encoding to be used when reading each of the selected documents(files). The initial values depend on the selected encoding in the file chooser dialogs which are used during the selection of files. These values can be changed later by clicking on the corresponding cells in this column which causes the visualization of encoding chooser menu.

>   The management of the selected documents can be done by buttons: Add - allows the user to select documents for importing with the help of a standard file chooser; Remove - removes the selected documents in the table; Clear - clears the table content.

> - Start - Starts to import the selected documents one by one. While importing, the status bar indicates which document is being currently processed. When the operation is completed a result message window appears with detailed information about each imported document: whether it is valid, well-formed and so on.
> - Cancel - Cancels the operation of multi-importing documents.
> - Save Documents - This checkbox determines whether or not the imported documents will be saved in the system. Not saving the documents is useful for checking the validity and the well-formedness of a set of documents. By default this item is selected.
> - Overwrite - This item determines the treatment of documents which will be imported in the system with names which are already used by other documents (painted in red in the table). If this option is selected, all problematic documents are saved, overwriting the previous ones. Otherwise, having pressed the Start button the user is shown the following warning/confirmation message:

>   The choices given here are:

>   - Overwrite - overwrites the old documents with the new ones (the same behaviour as if the Overwrite option is selected).
>   - Add suffix - generates automatically new names for the problematic documents by adding an index in brackets to the end of the document names.
>   - Cancel - cancels the import operation for the selected documents
> - Auto Detect DTD - if this option is selected, the system will try to detect the DTD of the input documents, unless a certain DTD is chosen in the corresponding DTD Name cell in the table. If the detection fails, the system will refer to the Default DTD for documents.

> If a document is not well-formed, then the system reports an error. A detailed description of all parsing errors can be found in Parse error messages section. The errors of this kind have to be repaired with an editor outside the system. The error message reported by CLaRK system can help the user to find the error in the document.

> ### Multi-Export

> This item allows the user to export a set of internal documents: whole group or/and single documents. The user selects an output directory and encoding for all selected documents. Here is a screen-shot of the Multi-Export Manager window:

> The manager window consists of:

> - Output Directory section

>   This section contains two parts: Directory chooser and Encoding chooser. The Directory chooser shows the output directory, where the document will be stored in XML files. The file names are generated automatically on the basis of the internal document names. If an internal name contains symbols which are not allowed to be in a file name, they are substituted by an underscore symbol ('_'). The output directory can be changed by using button "Change Directory". Having pressed this button, the user is shown a standard file chooser to point to a new output directory. The second component is used for setting an output character encoding. The options are four:

>   - ASCII Text File
>   - UNICODE (UTF-8) Text File
>   - UNICODE (UTF-16BE) Text File
>   - UNICODE (UTF-16LE) Text File.
> - Internal Documents chooser

>   This component is used for selecting documents to be exported. The component itself represents a standard for CLaRK system Document Selector, which will be described in details below. This selector is used not only in this part of the system, but in all places where a multiple selection of documents is needed. Having selected documents for exporting, the user must use one of the following buttons:

> - Export button

>   Starts exporting the selected documents one by one in to the selected directory with the selected character encoding. The status bar of the system shows which file is being currently processed. After completion of the operation an information message about the result of the exported documents is shown to the user.

>   > Remark: If a document is exported in ASCII format but the content of the output file is not comprehensible for other programs or even for the CLaRK System, then the problem can be in an inappropriate character encoding converter from Unicode to ASCII (for details see Options/Encoding Correction).

> - Cancel button

>   Cancels the whole operation.

> - No Overwrite Warnings

>   If this item is selected, no confirmation messages for overwriting the existing files will be shown.

> ### Document Selector

> The Document Selector is an universal component which is used in almost all system tools, it can work with more than one document. The selector provides the possibility for the user to point to the internal documents a particular tool will be applied to. It consists of two sub-components: a selection list and a selecting dialog window. The selection list shows the currently selected documents. Initially this list is empty. Here follows a picture of the selection list. Usually it is embedded in another dialog window.

> Three operations can be applied to this list: adding new list entries, removing selected list entries, clearing the whole list. These operations can be applied by using the buttons on the right:

> - Add Documents - By using this button the Document Manager dialog is shown. When new documents are selected, they are added to the list on the left. If a document is selected, but it already is presented in the list, it is not added again.
> - Remove Documents - Removes the selected items in the list on the left. If no selection is made, nothing is done.
> - Clear All - Removes all the entries from the list on the left. If the list is empty, nothing is done.

> ### Exit

> By choosing this item, the user closes all opened files and exits the system. If there are unsaved documents, the user is asked whether to save the changes or not.