The <Misc> option is used for miscellaneous settings.
Gigatrees5 treats all carriage returns (or newlines) found in text as HTML break characters. When embedding HTML, unexpected line breaks can occur because many HTML tags such as the header ( <h> ), page ( <p> ), and blockquotes have implied line breaks built into their opening and closing elements. To minimize these unexpected breaks, you generally need to butt HTML tags up against one another rather than putting them on separate lines. If you enable the <CleanLineBreaks> option, it will attempt to convert these multiple breaks to single breaks, and then remove extra breaks around some of the more common HTML opening and closing tags. You can still force extra breaks by adding the HTML non-breaking space character entity ( ) to a blank line. The <CleanLineBreaks> option will not remove extra line breaks if there is white-space between the HTML tags. have a separate option to control newlines and breaks on a per post basis.
|<CleanLineBreaks>||[ false ]||Many of the HTML tags have implied carriage returns (breaks) built into them such that when using HTML in a GEDCOM text record (note, source citation, etc.), it can result in extra breaks occuring on the page. During record field editing, users may also insert extra blank lines in plain text for readability reasons. Enabling this option will convert multiple blank lines into single blank lines, then convert blank lines to HTML break characters ( <br/< ), then convert multiple break characters into single break characters, and then finally remove breaks around some of the more common HTML opening and closing tags that have implied breaks built-in. The option will only remove extra new lines and break characters if no white-space lies between them. This option does not effect.|
|<ReportUnsupportedRecords>||[ true ]||Many vendors use non-standard GEDCOM tags for a variety of resons. Gigatrees5 supports thousands of vendor specific non-standard tags, but it does not support every one. If do not want to see these warnings, disable this option.|
|<ReportUniqueWarningsOnly>||[ true ]||During GEDCOM parsing, when a warning is generated, Gigatrees5 will by default supressed any subsequent similar warnings that differ only in that they occur on another line. Enabling this can results in hundreds of similar warnings being generated and filling the build log.|
|<ShowReliabilityAssessments>||[ false ]||assessments are automatically determined for every claim in your database. Displaying these alongside every claim can and should be enabled.|
|<AutoHyperlinkUrls>||[ true ]||By default, Gigatrees5 will attempt to automatically setup URL links for stray URLs, that is, URLs that are not contained within an HTML anchor element ( <a> ), image element ( <img> ) or form elements ( <form> ). In order to create the hyperlink, the software looks to see if the URL is preceded by any of the following: ">, href=", href=', href="e;, src=", action=". If it is, it will not create the hyperlink, but since the HTML elements can be structured in various ways, it may accidentally embed a hyperlink inside an existing one, breaking the hyperlink. This option allows you to disable this feature.|
|<AppendNicknames>||[ false ]||Enable this option to append nicknames to names throughout.|
<CleanLineBreaks> false </CleanLineBreaks>
<ReportUnsupportedRecords> true </ReportUnsupportedRecords>
<ReportUniqueWarningsOnly> true </ReportUniqueWarningsOnly>
<ShowReliabilityAssessments> false </ShowReliabilityAssessments>
<AutoHyperlinkUrls> true </AutoHyperlinkUrls>
<AppendNicknames> true </AppendNicknames>