Include speaker labels: if this is selected a label based on the participant attribute or the tier name will be printed in front of the text. The label has a fixed maximum length of 3 characters.

Repeat the label of the same speaker: sets whether or not the label should be printed if the speaker of the current utterance is the same as the one of the previous utterance.

Merge annotations of the same speaker into paragraph: if not selected, each annotation will be on a new line in the output. If this options is selected, the annotations of one speaker will be on the same line in the output, separated by a whitespace. Until an utterance of a different speaker appears, this will always be on a new line.

Note

A special case are subdivision tiers; if these are selected as transcript tiers, annotations under the same parent will always be merged in the export (separated by whitespaces), regardless of this setting. If a depending tier of a subdivision tier is selected as a coding tier, the resulting code of each depending annotation will still be linked to that part of the transcript text that corresponds to its parent annotation.

Include silence duration indicators: if this is selected an indicattion of the duration of the gap between utterances is printed in the output text, with a (currently hardcoded) minimum of 200 milliseconds. There won't be silence duration indicators within a paragraph.

Include begin (and/or end) time stamps in the text: if selected, a formatted time stamp will be printed at the beginning (or end) of a line or paragraph. Importing QDA applications may or may not show these time stamps in their text view.

	Note
	Regardless of these time stamp settings, there will be Syncpoint elements in the REFI project XML file, ensuring that the time links between segments of the text and the media file are available to and in the importing QDA application.

Copy the media files into the export file: if this is selected the linked media files are copied into the Sources folder of the .qdpx file. In the REFI project's .qde file, the media files are then referenced with internal:// URL's. The big disadvantage is that this increases the size of the .qdpx file considerably. Unfortunately, it seems that the best chance of successful import into a QDA application, including the media files and links between text and media, is with this option selected.

	Note
	This export function does not check possible maximum sizes of the files to add or of the resulting file.

Set a base path and use relative paths: with this option a base path for the media files should be specified. The base path should be (the path to) a folder containing the media files and/or the sub-folders containing the media files. The media files will not be copied into the .qdpx file, in the project's .qde file they will be referenced with relative:// URL's. Even though this could be sufficient for importing QDA applications to find the media files, if importing takes place on the same computer, this often doesn't work. The QDA application might prompt the user to locate or select the base path folder (this can be a different folder e.g. if importing happens on a different computer).

Use absolute paths of the media files: with this option the media files are not included in the .qdpx file and are referenced in the project's .qde file with absolute:// URL's, their current absolute path. When the export from ELAN and the import into a QDA application is performed on the same computer, that could theoretically give a good chance of the media files being found and imported. But the three tested applications did not support this.