Menu "File" - "Export to:" - "HTML file" exports the information from the tree into an interactive HTML page. Family communications between relatives in this page will be presented by hyperlinks, so the user will be able to navigate in the entire family tree, and the hyperlinks to documents and web pages can be opened directly in the browser.

"Export to HTML" dialog interface:

Checkbox "CREATE:" defines the output file form:

  1. One big file - only one HTML file will be created in which lists of both persons and families will be placed, along with information about them.
  2. Main file + files for each record - the lists of relatives and families will be saved in the main HTML file, and the information about each record will be saved in separate HTML files in a directory file_name-infos. This can add up to quite a large number of files. One file for each record (person, family and shared record).

Checkbox "INCLUDE person's/family's information:" defines what information from the records will be included:

  1. All (GEDCOM-like structure) - every record will be saved with all its elements.
  2. Notes and Links only - only notes and links will be included.

Radio buttons "Export: All/Selected" specifies if entire tree or only a selected part will be exported. In this case, as well as in case of saving selected, references to persons and families which are not among selected, will not be exported if "Keep external references" is not checked.

Dropdown list "Encoding" allows to set the encoding (language) of the output file(s).

Note: What if your file contains symbols of several different languages besides English, for example, Turkish and Russian? What encoding should you specify? In general the answer is: choose the one which is the most prevalent. When exporting to HTML the program processes the text as follows:
1) English symbols are saved as is, one byte per symbol;
2) Symbols of the alphabet, which coding is specified also are saves one byte per symbol in corresponding encoding;
3) Symbols of all other alphabets will be transformed to sequences "&#xxxx;", where xxxx is a UNICODE standard numerical code of the symbol.
So actually it would be possible to not specify encoding at all - the program will code all non-English into &#-symbols, and the browser will show them properly. The only problem with this approach is that such an HTML file would be much bigger in size...
You can also export the file in UTF-8 encoding, but that too will increase the file size by 1.5 to 2 times.