We generally recommend that file names (including session names and media files) avoid using “special characters” (Unicode characters that are outside of the ASCII character range. SayMore tries to deal with files that do not follow this guideline, but there are limitations, and you can avoid problems by following this guideline. The biggest problem we are aware of is when media files use non-ASCII characters. SayMore generates session names based on media file names, and also creates derived media files based on session names (and occasionally person names). If the SayMore files are stored on a disk volume that does not support these Unicode characters or is not set up to generate “8.3” (short) file names in addition to the long names provided by users, then media file playback or conversion operations will fail.