Ribbons

example

Here is the user interface with the ribbon layout displayed.

Here is the View ribbon.

And here is the Source Control ribbon, viewed for a project bound to Git. Notice that it has different options.

characteristics of ribbons

Following are some characteristics of ribbons.

Switch Views By default ribbons are used when you install and launch Analyzer for the first time. However, you can use the Options dialog to switch back to the classic tool strip.

See Switching Between Ribbons and the Tool Strip and Options Dialog.
Minimize You can minimize the ribbons so that you only see the top portion of the ribbons until you select an option.

To do this, right-click anywhere in a ribbon and select Minimize the Ribbon from the context menu.

See Minimizing Ribbons.
Hidden Ribbons Some ribbons are not always shown. For example, the Source Control ribbon is displayed only if your project is bound to version control.
Icons/Text Ribbons consist of icons and text, which let you perform various tasks. Larger icons are shown for the most common tasks.
Sections Ribbons are split into sections to make it easier to locate the options on them. For example, the View ribbon contains the following sections: Dynamic Reports, Analysis, Common, and Info.
Reducing Application Window Size When you reduce the size of the entire application window, the ribbons are also reduced in a way that lets you continue to access hidden options by clicking on the section name.

example

example

Let's say you have the application window maximized, and this is what you see when opening the View ribbon.

If you reduce the size of the application window, the ribbon may shrink along with it. You can still access all of the options. Some icons are simply smaller, and others are accessible from section drop-downs.

file drop-down

	Opens the Analyzer Summary window pane, which is the primary window pane in the interface. This window pane displays a list of current issues in the project being analyzed. See Analyzer Summary Window Pane and Viewing Current Issues.
	Opens a dialog, which lets you search for and select a Flare project to open so that you can analyze it.
	Click the face of the button to save changes to the active file. You can also select the following from the submenu: Save Saves changes to the active file. Save As Opens the Save As dialog, which lets you save the active file under a different name and/or file type and to a particular location. The new file is then displayed in the editor. Save To Opens the Save As dialog, which lets you save the active file under a different name and/or file type and to a particular location. The new file is not automatically displayed in the editor.
	Opens the selected file so that you can work on it. For example, if you select a row in the Broken Links window pane and then click this button, the topic where the broken link occurs is opened. You can then fix the broken link in that topic. The button label changes, depending on whether you are analyzing a Flare project.
	Click the face of the button to open the Print dialog and send a file to a printer. You can also select the following from the submenu: Print Opens the Print dialog, which lets you send a file to a printer. Make sure that the item that you want to print is selected. For example, if you want to print a topic from the online Help, first click somewhere inside the topic so that it is the active element in the interface. Page Setup Opens the Page Setup dialog, which lets you specify the page settings (e.g., paper, orientation, margins) to be used when you print an image file. Print Preview Opens the Print Preview dialog, which lets you see how a document looks before you send it to a printer. Make sure that the item that you want to preview is selected. For example, if you want to preview a topic from the online Help, first click somewhere inside the topic so that it is the active element in the interface.
	Click the face of the button to create a temporary copy of the active file. You can also select the following from the submenu: Send Copy to the "Backups Folder" Creates a temporary copy of the file that is open and active in the interface. The file is placed in the Backups window pane. See Backing Up Files. Clear the "Backups Folder" Removes all temporary backup files from the Backups window pane. See Clearing the Backups Folder. example example You might use this feature, for example, if you want to make some changes to a file but are not certain if you will want to keep them when you are finished. Therefore, you can make a backup of the file in question. When you are finished making your changes, you might decide that you prefer the file the way it was. If so, you can quickly roll back to the backup file, which overwrites the changes that you made.
	Opens the Properties dialog for the selected item.
	Click the face of the button or the right-facing arrow to select from the following. Import Project Opens the Import From Source Control Wizard, which lets you create a new project by importing an existing project that is located in a source control application. You will see this option for all source control providers. This option is disabled in Analyzer. Add Opens the Check In dialog, which lets you add the selected files to the integrated source control application. When working in a project that is connected to source control, there may be occasions when you have files in your local copy of the project that are not yet part of the source control copy. For example, when you add a new topic in your local copy of the project, that file will not be included in the source control copy of the project until you add it. You will see this option for all source control providers See Adding Files to Source Control. Check In Opens the Check In dialog, which lets you check files into source control. When you are finished editing files, you can check them in to source control. Checking in a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically check in files so that you have a backup in source control. You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe. Commit Opens the Commit dialog, which lets you commit files into source control. When you are finished editing files, you can commit them to source control. If you are working with Git, committing a file adds your changes to the local database. When you are ready to add your local commits to the remote repository, you can push these files to the remote. If you are working with Subversion, committing a file overwrites the old copy of the file in the source control database with the new one from your local machine. You will see this option if your project is bound to Git or Subversion. Submit Opens the Submit dialog, which lets you submit files into source control. When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control. You will see this option if your project is bound to Perforce. Check Out Opens the Check Out dialog, which lets you check out files from source control. When you need to work on any of the Analyzer project files, you can check them out. Checking out files means to copy the latest source control files to your local Analyzer project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out. You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce. Get Latest Version Opens the Get Latest Version dialog, which lets you "get" files from source control. After you bind a Analyzer project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Analyzer project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out. See Updating or Getting the Latest Version of Source Control Files. You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce. Update Opens the Get Latest Version dialog, which lets you update files from source control. After you bind a Analyzer project to a Subversion, you can update any of the source control files. When you do this, you are copying the most current files stored in Subversion to your local Analyzer project. You will see this option if your project is bound to Subversion. See Updating or Getting the Latest Version of Source Control Files. Undo Check Out Opens the Undo Check Out dialog, which lets you reverse the check-out of the files. If you have files checked out from source control but do not want them checked out anymore, you can use the "Undo Check Out" option instead of checking in the files. You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe. See Reverting or Undoing a Checkout of Source Control Files. Revert Opens the Revert dialog, which lets you return files to their last known state. If you have modified files from source control but do not want to keep your modifications, you can use the "Revert" option instead of committing the files. While committing the file would save your changes to source control, reverting a file returns it to its previously committed state and does not commit any of your new changes to source control. When reverting changes made in Git, you only revert changes to the file on the branch you are currently editing. If you have a file that resides on multiple branches, copies of the file on other branches are preserved. You will see this option if your project is bound to Git, Perforce, or Subversion. Show Differences Opens a window pane that lets you view the content and code differences for files. If you select a single file and choose this option, the differences between the local version of the file and the source control version of the file are shown. If you select two files and choose this option, the differences between those two files are shown. You will see this option for all source control providers. See Viewing Differences in Source Control Files. View History Opens the History dialog, which lets you view the history of a particular source control file, including all of the occasions when the file has been checked in. You can then use the dialog to view the differences between older versions of the file or roll back to a particular version. You will see this option for all source control providers. See Viewing the History of Source Control Files and Rolling Back to an Earlier Version of a File. Undelete Undeletes a file, allowing you to add it to source control. See Undeleting Source Control Files. You will see this option if your project is bound to Microsoft Team Foundation Server and Microsoft Visual SourceSafe. Refresh Refreshes the window pane so that the latest information is shown. You will see this option for all source control providers.
	Closes the active file.
	Displays a list of recently opened projects. You can select one from the list to open it. You can also select Manage Recent Projects. This opens the Recent Projects dialog, which lets you remove projects from the list of recently opened projects. This allows you to keep the list shorter and more manageable. When you use this feature, the project is merely removed from the list, but the actual project is not deleted.
	Opens the Options dialog, which lets you set various options. For more details, see Options Dialog.
	Closes the application.

home ribbon

	Pastes the selection from the clipboard to the place where the cursor is inserted.
	Cuts the selection and sends it to the clipboard.
	Copies the selection and sends it to the clipboard.
	Deletes the selection.
	Lets you select a font type (e.g., Arial, Times New Roman), applying it to the content selected in the topic.
	Lets you select a font size, applying it to the content selected in the topic.
	Applies bold typeface to the content selected in the topic.
	Applies italic typeface to the content selected in the topic.
	Underlines the content selected in the topic.
	Raises the selected content in the topic above the normal line of text (e.g., X²).
	Lowers the selected content in the topic below the normal line of text (e.g., X₂).
	Removes local formatting in a selection or even an entire topic. See Removing Inline Formatting.
	Lets you choose and apply a color to the selected content.
	Lets you choose and apply a color to the background of the selected content.
	You can set redacted text on any kind of content (e.g., characters, paragraphs, images, tables). You can do this locally at the font level by highlighting each piece of content. Redaction occurs when content is permanently eliminated from a printed or electronic document. In place of that content, end users will see black rectangles that indicate where the original content was found. See About Redacted Text and Setting Redacted Text on Content.
(at bottom of Font section)	Opens the Font Properties dialog, which lets you edit the font properties for topic content directly. See Editing Font Properties.
	Lets you select one of several kinds of bullet or numbered lists, applying it to the selected content. Bullet List Applies a bulleted list to the selected content. Circle Bullet List Applies a bulleted list to the selected content. The bullets are circles. Square Bullet List Applies a bulleted list to the selected content. The bullets are squares. Numbered List Applies a numbered list to the selected content. Lower-alpha Numbered List Applies a numbered list to the selected content where lowercase alpha characters are used (a., b., c., d., etc.) Upper-alpha Numbered List Applies a numbered list to the selected content where uppercase alpha characters are used (A., B., C., D., etc.) Lower-Roman Numbered List Applies a numbered list to the selected content where lowercase Roman numerals are used (i., ii., iii., iv., etc.) Upper-Roman Numbered List Applies a numbered list to the selected content where uppercase Roman numerals are used (I., II., III., IV., etc.) Custom Format Opens a custom list format that lets you create a uniquely styled list up to 10 levels deep. You can also select an existing custom format from this submenu to apply it to the selected content in your topic or snippet. At this time, custom list formats are supported only in PDF, XHTML, and XPS outputs. After browsers begin to support the CSS3 marker element that makes custom list formats possible, this feature will automatically be supported in browser-based outputs as well. Until then, if you want to generate a browser-based output, you should use the standard method for creating lists instead.
	Removes the group tag from a paragraph, thus "outdenting" it.
	Lets you use a group tag such as <div> to indent content. Another method for indenting content is through the use of margin or padding settings on a style.
	Lets you apply miscellaneous actions to selected content in a list. These actions are as follows. Merge With Previous List Combines a list with another list immediately before it. Merge With Next List Combines a list with another list immediately following it. Sort List Reorders the items in the list alphabetically. Reverse List Reorders the items in the list so that they appear in reverse order (i.e., first item is last, last item is first). Unbind List Removes the list designation from the content so that it displays as regular text. Continue Sequence Ensures that the next list you create in the topic starts with the next number in the sequence of the list above (even if the two lists are separated by other content). example example Let's say you have a numbered list from 1 to 10 at the top of your topic and you add a few regular paragraphs (not in a list) after it. If you start another numbered list and select this option, the new list will start at 11. List Start Number Lets you specify a number to start a numbered list. Item Number Lets you specify a number to start a selected item in a numbered list. example example Let's say you have a numbered list from 1 to 10. If you were to click in the paragraph with the number 7 and then use this option to start numbering at 23, your list would change so that the numbering displayed as 1 to 6 and then 23 to 26. Move Up Moves the selected item in the list above the item before it. Move Down Moves the selected item in the list below the item after it. Make Simple Item(s) Lets you return a line in a list from a paragraph item to a simple item (an <li> tag without a <p> tag following it). Paragraph items can be used in numbered or bulleted lists, for example, to add comments without disrupting the flow of the list. Make Paragraph Item(s) Lets you add a <p> tag after the <li> tag in a numbered or bulleted list. You can then add more lines after a list item without adding numbers or bullets to those lines. Paragraph items can be used in numbered or bulleted lists, for example, to add comments without disrupting the flow of the list.
	Groups selected items. The Create Group dialog opens, which lets you create a group from selected content and apply one of the following tags to it: <blockquote>, <div>, <fieldset>, <form>.
	Aligns the selected content to the left.
	Aligns the selected content in the center.
	Aligns the selected content to the right.
	Spaces the selected content so that both the left and right sides are aligned.
	Resets the alignment of the selected text to the default (inherited) setting.
(at bottom of Paragraph section)	Opens the Paragraph Properties dialog, which lets you edit the paragraph properties for topic content directly. This includes the ability to apply page breaks, column breaks, and widow/orphan control to a paragraph directly. See About Paragraph Formatting.
	Opens the Create Style dialog, which lets you create a new style for the content selected in the content file. See Creating Selectors.
	Opens the Stylesheet Links dialog, which lets you apply one or more stylesheets to the active content file.
	Lets you apply a style to the content selected in the topic.
	Opens the Find Elements window pane, where you can search for specific elements, tags, styles, and markup in the open document or the entire project. See Using the Find Elements Feature.
	Opens the Quick Find widget in the upper-right corner of the open document. This lets you search for text in that document. See Using the Quick Find and Replace Widgets.
	Opens the Quick Replace widget in the upper-right corner of the open document. This is the same as the Quick Find widget, except that it opens with the replace fields already in view. It lets you search for and replace text in that document. See Using the Quick Find and Replace Widgets.
	Opens a submenu, which lets you choose from the following options: Find and Replace in Files Opens the Find and Replace in Files window pane, which lets you search for and replace text in multiple documents. .See Using the Find and Replace in Files Feature. Find Results 1 Opens the Find Results 1 window pane, which is used to display results from a search in the Find in and Replace in Files window pane. Find Results 2 Opens the Find Results 2 window pane, which is used to display results from a search in the Find in and Replace in Files window pane.
	Opens the Properties dialog for the selected item.

view ribbon

	Opens the Analyzer Summary window pane, which is the primary window pane in the interface. This window pane displays a list of current issues in the project being analyzed. See Analyzer Summary Window Pane and Viewing Current Issues.
	Opens a submenu, which lets you select window panes that show information about links in your project. Broken Links Opens the Broken Links window pane, which lets you view a list of files in your project where a broken link is located. You can see which file it is trying to find, the link text, the link tag, and other information. You can also open the file where the broken link is located. The broken link is highlighted so that you can easily fix it. See Viewing Broken Links. Broken Bookmarks Opens the Broken Bookmarks window pane.You can view a list of files with broken bookmarks. You can see the bookmark destination that the link is trying to find, the link text, the link tag, and other information. You can also open the file where the broken link is located so that you can fix it. See Viewing Broken Bookmarks. External Links Opens the External Links window pane, which lets you view a list of files in your Flare project containing links to external files. For example, if you have a text hyperlink to a website, the file name where the link exists is displayed. By clicking the "Check" button, you can verify that all external links point to valid destinations. In addition, you can double-click a row to open the file in the Analyzer interface. You can also select the row and click File > Send to Flare to open the file in the Flare project. This allows you to fix any problems with external links. See Viewing External Links. Absolute Links Opens the Absolute Links window pane, which lets you view a list of files in your Flare project containing absolute links to other files. An absolute link contains the full path to the target file. For example, let's say you have a text hyperlink that points to a file in your project like this: file://C:\MyProject\Content\MyFile.htm. (You can view this link format in the file's true code, which can be seen by using the Internal Text Editor in the source Flare project.) Because users do not have access to your local C: drive, they will not be able to use the link successfully in the output. Instead, the link should be relative to the file in your project, with dots and slashes that represent each folder level away from the current file (e.g., ..\..\MyFile.htm). You do not need to create this path manually; instead, it is automatically created when you properly insert a link by using the interface. The Absolute Links window pane allows you to find absolute links so that you turn them into relative links (by re-inserting the link). You can double-click a row to open the file in the Analyzer interface. You can also select the row and click File > Send to Flare to open the file in the Flare project. The link is highlighted so that you can easily fix it. See Viewing Absolute Links. Named Destinations Opens the Named Destinations window pane, which displays files in your project containing named destinations for PDF output. See Viewing Named Destinations. Index Keyword Links Opens the Index Keyword Links window pane, which lets you view a list of all index keywords used in index links throughout your project. You can also quickly rename index keywords associated with the links. See Viewing Index Keyword Links. Concept Links Opens the Concept Links window pane, which lets you view a list of all concepts that have been used in concept links throughout your project. You can also quickly rename concepts associated with the links. See Viewing Concepts in Links. Link Viewer Opens the Link Viewer window pane, which is used to view other files linked to and from the active file. See Viewing File Links.
	Opens a submenu, which lets you open window panes that display suggestions for improving your project. Index Keyword Suggestions Opens the Index Keyword suggestions pane, which lets you view a list of topics containing text that matches existing index keywords in your project. You can then quickly add the same index keywords to those topics. See Viewing Index Keyword Suggestions. Snippet Suggestions Opens the Snippet Suggestions window pane, which lets you view content that matches existing snippets in your project, and you can quickly convert these occurrences to snippets. You can also double-click a row to open the topic in question, with the potential snippet content highlighted. See Viewing Snippet Suggestions. Variable Suggestions Opens the Variable Suggestions window pane, which lets you view regular text that matches existing variables in your project, and then quickly convert these occurrences to variables. You can also double-click a row to open the topic in question, with the potential variable text highlighted. See Viewing Variable Suggestions. New Style Suggestions Opens the New Style Suggestions window pane, which lets you view the places in your project where you have used local formatting. MadCap Analyzer suggests that you convert these instances of formatting to new styles. You can use the Create New Style dialog to do just that. You can also double-click a row to open the file where the formatted content exists. See Viewing New Style Suggestions. Replace Local Style Suggestions Opens the Replace Local Style Suggestions window pane, which lets you view the places in your project where you have used local formatting. MadCap Analyzer suggests that you replace these instances of formatting with existing styles in your stylesheet that match the formatting that you have applied manually. This is different from a new style suggestion in the following way: With a new style suggestion, the properties in the tag do not match an existing style exactly; therefore, Analyzer suggests that you create a new style. On the other hand, if you make formatting changes that happen to result in an exact match to all of the properties in an existing style, Analyzer suggests that you replace the formatting with that style (rather than creating a new style). See Viewing Local Style Suggestions. Accessibility Suggestions Opens the Accessibility Suggestions window pane, where you can search for places in your project where you can make accessibility improvements for WebHelp and PDF outputs in Flare. That way, you can make sure your documentation can be accessed by people with disabilities (i.e., individuals who have visual, hearing, and mobility impairments). This includes the ability to identify tables that are missing certain elements and finding objects—such as images, equations, and QR codes—that are missing alternate text. You can click the "Search Properties" button to customize which types of issues to display in the window pane. You can double-click a row to open the topic or other file in the Analyzer interface. You can also select the row and click File > Send to Flare to open the file in the Flare project. See Viewing Accessibility Suggestions. Markup Suggestions Opens the Markup Suggestions window pane, where you can search for places in your project where the XHTML markup (code) can be improved (e.g., empty tags, CDATA tags, empty attributes, excessive spaces). You can click the "Apply" button to automatically apply the suggestions to the selected files. You can click the "Search Properties" button to customize which types of issues to display in the window pane. You can double-click a row to open the topic or other file in the Analyzer interface. You can also select the row and click File > Send to Flare to open the file in the Flare project. See Viewing and Applying Markup Suggestions. Writing Suggestions Opens the Writing Suggestions window pane, which lets you view places in your project where you can make writing improvements based on industry-wide standards. For example, Analyzer can locate files where an h1 or h2 heading has only one subheading (i.e., an h1 heading with only one h2 heading under it, or an h2 heading with only one h3 heading under it). It is recommended that you have more than one subheading under a parent heading. Therefore, occurrences such as these are raised as concerns. Analyzer can also locate files where a heading level has been skipped (e.g., an h1 heading is followed by an h3 heading, rather than h2), as well as any files where consecutive headings exist (e.g., an h1 heading is followed by an h2 heading, with no other content between them). You can use the Writing Suggestions Search Properties dialog to customize which types of suggestions to display in the window pane. See Viewing Writing Suggestions. Cross-Reference Suggestions Opens the Cross-Reference Suggestions window pane, where you can search for hyperlinks in your project that can be converted to cross-references. You can double-click a row to open the file and proceed to convert the hyperlink into a cross-reference. See Viewing Cross-Reference Suggestions. Frequent Segments Opens the Frequent Segments window pane, which lets you view a list of segments that occur frequently in your project. You can see the text, the number of occurrences of each segment, and the number of words and characters in each segment. If you notice that certain segments are repeated numerous times throughout your project, you can easily convert them to snippets or variables. For an example, see About Frequent Segments. Also see Viewing Frequent Segments. Similar Segments Opens the Similar Segments window pane, which lets you view a list of segments of text in your project that are similar, but not identical, to each other. You may want to modify similar segments so that they become identical to each other, or even convert them to snippets. You can also use the "Start Search" button to limit or expand the list of similar segments that are displayed. See Viewing Similar Segments.
	Opens a submenu, which lets you open window panes showing information related to used elements in your project. Undefined Glossary Term Links Opens the Undefined Glossary Term Links window pane, which lets you view a list of all files where you have glossary term links inserted into content, but those glossary terms do not appear in any of your glossary files. This might occur, for example, if you have created a new term in a glossary and then inserted that term into a topic as a glossary term link. Later, you remove that term from the glossary. You now have a glossary term link in a topic, but the term no longer exists in the glossary. Therefore, a problem exists. You need to either remove the glossary term link from the content, or you need to add the term to the glossary again. From the Undefined Glossary Term Links window pane, you can quickly unbind or rename multiple glossary term link occurrences in a single batch, add a new glossary term, or map the undefined term to an existing glossary term. See Viewing Undefined Glossary Term Links. Undefined Variables Opens the Undefined Variables window pane, which lets you view a list of all files where you have variables inserted in the content, but those variables have not been defined. This might occur, for example, if you have inserted a variable in a topic and then later change the name of the variable or variable set. The old variable or set name is still used at the location where it was previously inserted in the topic; therefore, a problem exists. From the Undefined Variables window pane, you can open the topic in question and fix the undefined variable. You can also quickly rename or remove multiple variables in a single batch, add the undefined variable to the project, or map the undefined variable to an existing variable. See Viewing Undefined Variables. Undefined Condition Tags Opens the Undefined Condition Tags window pane, which lets you view a list of all files where you have condition tags in the content, but those condition tags have not been defined. This might occur, for example, if you have applied a condition tag in a topic and then later change the name of the tag or condition tag set. The old tag or set name is still used at the location where it was previously applied in the topic. Therefore, a problem exists. From the Undefined Condition Tags window pane, you can open the file in question and fix the undefined condition tag. You can also quickly rename or remove multiple condition tag occurrences in a single batch, add the undefined tag to the project, or map the undefined tag to an existing condition tag. See Viewing Undefined Condition Tags. Undefined File Tags Opens the Undefined File Tags window pane, which lets you view a list of all files that are associated with file tags, but those file tags have not been defined. This might occur, for example, if you have associated a file tag with a topic and then later change the name of the tag or file tag set. The old tag or set name is still used for the topic. Therefore, a problem exists. From the Undefined File Tags window pane, you can open the file in question and fix the undefined tag. You can also quickly rename or remove multiple file tag occurrences in a single batch. See Viewing Undefined File Tags. Undefined Styles Opens the Undefined Styles window pane, which lets you view a list of all files where you have style classes applied to content, but those styles have not been defined. This might occur, for example, if you have created a new style class and applied it to a paragraph in a topic. Later, you remove that style class from the stylesheet. Therefore, you now have a style in a topic that is no longer defined in the stylesheet. You need to either apply a different, existing style class to that content, or you need to add the style class to the stylesheet again. You can also quickly rename or remove multiple style occurrences in a single batch, add the undefined style to the project, or map the undefined style to an existing style. See Viewing Undefined Styles.
	Opens a submenu, which lets you open window panes showing information related to used elements in your project. Used Condition Tags Opens the Used Condition Tags window pane, which lets you view a list of all condition tags that have been applied in files throughout your project. The list shows not only the condition tags, but each file where they have been used. You can also quickly rename or remove multiple condition tag occurrences in a single batch. See Viewing Used Condition Tags. Used File Tags Opens the Used File Tags window pane, which lets you view a list of all file tags used in your project. The list shows the tag type and the file that it is associated with. You can quickly rename or remove multiple file tag occurrences in a single batch. See Viewing Used File Tags. Used Language Tags Opens the Used Language Tags window pane, which lets you view a list showing each file where a language tag is found, the content tag to which it has been applied (e.g., html, span), and the language used. See Viewing Used Language Tags. Used Variables Opens the Used Variables window pane, which lets you view a list of variables that have been inserted in your project. The list shows not only the variables, but each topic where they have been used. You can also quickly rename or remove multiple variable occurrences in a single batch. See Viewing Used Variables. Used Index Keywords Opens the Used Index Keywords window pane, which lets you view a list of all index keywords used throughout your project. You can also quickly rename multiple keyword occurrences in a single batch. See Viewing Used Index Keywords. Used Concepts Opens the Used Concepts window pane, which lets you view a list of all concepts used in your project. You can also quickly rename multiple concept occurrences in a single batch. See Viewing Used Concepts. Used Bookmarks You can view a list showing each file where a link to a bookmark is found, including the name of the bookmark, the kind of link used, and the path of the link. You can also double-click a row to open the file where the bookmark link is inserted. See Viewing Used Bookmark Links.
	Opens a submenu, which lets you open additional window panes. Files With Annotations Opens the Project Annotations window pane. You can view a list of all files where annotations (internal comments) have been inserted. You can also double-click a row to open the topic in question. See Viewing Files with Annotations. Files With Changes Opens the Files with Changes window pane where you can view all topics in your project that contain tracked changes. Topics containing tracked changes cannot be opened in the Analyzer interface. You can double-click a row, and you will be prompted to open the topic in Flare. You can also select the row and click File > Send to Flare to open the file in the Flare project. See Viewing Files with Changes. Topics Not In Index Opens the Topics Not in Index window pane, which lets you view a list of all topics where you have not yet inserted index keywords. Therefore, no references to those topics will be found in the generated index. You can also double-click a row to open the topic in question. See Viewing Topics Not Indexed. Topics Not In Selected TOC Opens the Topics Not in Selected TOC window pane (if you are analyzing a Flare project), which lets you view a list of all topics that have been created in the project, but they have not yet been linked to any items in a TOC. A drop-down filter lets you select a specific TOC to analyze, or you can select "Any TOC" to analyze all TOCs in a project. See Viewing Topics Not in a TOC. Topics Not Linked by Map ID Opens the Topics Not Linked By Map ID window pane (if you are analyzing a Flare project), which lets you view a list of all topics that are not linked to context-sensitive Help (CSH) map IDs. You can also double-click a row to open the topic in question. See Viewing Topics Not Linked by a Map ID. Duplicate TOC Items Opens the Duplicate TOC Items window pane (if you are analyzing a Flare project), which lets you view a list of all files in your project that have been added more than once to a table of contents. See Viewing Duplicate Items in a TOC. Duplicate Styles Opens the Duplicate Styles window pane, which lets you view a list of all styles in your project where the same properties have been set. For example, let's say you have a style called "p.tip" and another style called "p.note." If you have specified the same settings for each of these styles (e.g., red font, 12 pt), with no other properties set, these styles will be included in the Duplicate Styles window pane. Groups or pairs of duplicate styles are displayed in alternating shaded rows (e.g., the rows for the first pair of duplicate styles are not shaded, the rows for the next group are shaded, the rows for the next group are not shaded, and so on). If you encounter duplicate styles, you may want to modify the settings for one or both styles, or you can remove one of the style classes from the stylesheet. See Viewing Duplicate Styles.: note Note: Duplicate styles are displayed only if they are based on the same tag. For example, if you have identical properties set for the styles "p.tip" and "p.note," they will be included in the window pane (because they are both based on the p style). However, if you have identical properties set for the styles "p.tip" and "h4.note," they will not be included in the window pane (because one is based on the p style, whereas the other is based on the h4 style). Unused Items Opens the Unused Items window pane, which lets you view lists of unused elements in your project. See Unused Items Window Pane, Viewing Unused Condition Tags, Viewing Unused Content Files, Viewing Unused CSH IDs, Viewing Unused File Tags, Viewing Unused Images, Viewing Topics Not Linked,Viewing Unused Styles, Viewing Empty Content Folders, Viewing Unused Variables, and Viewing Unused Bookmarks. Non-XML Topics Opens the Non-XML Topics window pane, which lets you view a list of non-XML files (e.g., HTML files) that have been added to your project. You can also convert those HTML files to XHTML files in a single batch. See Viewing Non-XML Topics. Topics With Snippet Conditions Opens the Topics with Snippet Conditions window pane. You can view a list of all files where snippet conditions have been applied. You can also double-click a row to open the topic in question. See Viewing Files with Snippet Conditions. Files Without File Tags Opens the Files Without File Tags window pane. You can view a list of all content files in the project that do not have file tags. Then you can open the properties for a file and associate one or more file tags with it. See Viewing Files Without File Tags. Topics Without Concepts Opens the Topics Without Concepts window pane. You can view a list of all topics in the project that do not have concepts inserted. You can then open a topic and insert concepts into it. See Viewing Topics without Concepts.
	Opens the Incoming Links window pane and Outgoing Links window pane. The Incoming Links window pane lets you view links pointing to the selected file from other files. The Outgoing Links window pane lets you view links pointing from the selected file to other locations. See Viewing Incoming Links and Viewing Outgoing Links. note Note: You can also double-click a file row, opening that file in the interface. This automatically populates the window pane.
	Opens the Topics for Selected window pane, which lets you view a list of topics associated with a segment (as selected in the Frequent Segments window pane or Similar Segments window pane). This is simply a quick way to open a file where a particular segment exists. See Viewing Topics for a Selected Item.
	Opens the Statistics window pane, which lets you view information about your project, such as the number of topics, words, segments, images, snippets, and broken links. The information is shown not only for the latest version of the project, but also for versions saved on previous days. You can use the Statistics Search Properties dialog to customize the number of days in the past to show statistics for the project. See Viewing Statistics.
	Opens the Reports window pane, which lets you generate custom reports based on the information contained in your project, for just about any type of information that MadCap Analyzer captures. In addition, you can design the look and feel of reports, save them for future access, and open them in a browser window (where you can print them). See About Reports.
	Opens the File List window pane, where you can quickly view all content files in the Flare project being analyzed and send selected files to the File Issues Viewer window pane. See File List Window Pane.
	Opens the File Issues Viewer, where you can send selected files to the in order to see any issues associated with them. You can use the File List window pane to quickly add many files to this Viewer, or you can add files one at a time from within the user interface. See Viewing Issues for Specific Files.
	Opens the Start Page, which provides links to high-level tasks and information. See Start Page.
	Opens the Messages window pane, which displays important information as you work. For example, if a necessary file is missing, this window pane lets you know.
	Opens the Backups window pane so that you can see the files for which you have created backups and restore (roll back) any of those files if necessary. See About Backups, Viewing Backup Files, and Restoring Backup Files.
	Hides or shows special information pertaining to the editor or window pane.
	Opens or closes the status bar at the bottom of the program window.

tools ribbon

	Opens the Spell Check window pane, which lets you perform spell checking manually.
	Activates a feature that lets you check your spelling as you type in your topics. Questionable words are underlined with a jagged red line. You can take action with the word by right-clicking on it. See Spell Checking While Typing.
	Opens the Ignored Words dialog, which lets you create a list of words to be ignored when using the spell checking feature in the application. See About Spell Check and Adding Words to the Ignore Spell Check List.
	Opens the Update Cross-References dialog, which lets you update the cross-references that you have added to topics. By updating the cross-references, you can ensure that they reflect any changes in your project that might affect them. Updating cross-references is not a mandatory step. When you generate output for a target, all of your cross-references will be updated automatically. However, you can use this feature to manually update cross-references in a single topic. This is a way of performing a "spot check" ahead of time, verifying that cross-references will be updated accurately before you generate the entire target.
	Opens the master stylesheet in the Stylesheet Editor.
	Opens the Chart window pane, which lets you view statistics in many different kinds of color charts, making it easier to see statistics at a glance. You can quickly change the type of chart that displays the information. This includes a variety of pie, donut, bar, cylinder, and line charts. See About Charts, Creating Charts, and Editing Chart Styles.
	Opens the Glossary Terms window pane, which you can use to see all of the glossary terms and definitions that you have added to the project. You can double-click the terms in this window pane to insert them as links.
	Opens the Index window pane, which is used to create index keywords and insert them into topics. See Inserting Index Keywords.
	Opens the Concept window pane, which is used to create concepts and insert them into topics.
	Opens the Link Viewer window pane, which is used to view other files linked to and from the active file. See Viewing File Links.
	Opens the Footnotes window pane, which lets you see all of the footnotes that have been added in the active topic.
	Opens the Frame Contents window pane, which lets you add content to the selected frame in a page layout.

source control ribbon

The source control ribbon uses a dynamic interface. The icons that display that change depending on which source control provider your project is bound to. Additionally, the ribbon will not display if you are not using source control.

	Opens the Pending Changes window pane, which displays files in the project that are pending check in (if the project is integrated with a source control application). In other words, you can use this window pane to see which files you have checked out, which files have been created but not yet added to source control, which files other users have checked out, and which files are out of date. For more information see the Flare online Help.
	Opens the Check In dialog, which lets you add the selected files to the integrated source control application. When working in a project that is connected to source control, there may be occasions when you have files in your local copy of the project that are not yet part of the source control copy. For example, when you add a new topic in your local copy of the project, that file will not be included in the source control copy of the project until you add it. You will see this option for all source control providers See Adding Files to Source Control.
	Opens the Check In dialog, which lets you check files into source control. When you are finished editing files, you can check them in to source control. Checking in a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically check in files so that you have a backup in source control. You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe.
	Opens the Commit dialog, which lets you commit files into source control. When you are finished editing files, you can commit them to source control. If your project is bound to Git, committing a file adds your changes to the local database. When you are ready to add your local commits to the remote repository, you can push these files to the remote. This icon is Git-specific.
	Opens the Commit dialog, which lets you commit files into source control. When you are finished editing files, you can commit them to source control. If your project is bound to Subversion, committing a file overwrites the old copy of the file in the source control database with the new one from your local machine. This icon is Subversion-specific.
	Opens the Submit dialog, which lets you submit files into source control. When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control. You will see this option if your project is bound to Perforce.
	Opens the Check Out dialog, which lets you check out files from source control. When you need to work on any of the Analyzer project files, you can check them out. Checking out files means to copy the latest source control files to your local Analyzer project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out. You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.
	Opens the Lock dialog, where you can select files you want to lock. If your project is bound to Subversion, you can steal locks from another user's locked files using this dialog. When you are working, you may want to lock the files you have modified. Locking a file does not prevent other users from modifying the file. However, no one else can commit a file that you have locked until you unlock the file. If your project is bound to Subversion, you can steal a lock from another user if you need to commit a locked file while they are working on it. Likewise, another user can steal a lock on a file you have locked. You will see this option if your project is bound to Perforce or Subversion. See Locking Files.
	Opens the Unlock dialog, where you can select files you want to unlock. If you have locked a file, you should unlock it when you are done modifying it. Other users can modify the file while you have it locked, but they cannot submit a locked file until you unlock it. To help prevent file conflicts and make sure that everyone on your team has the most current version of the file, you should unlock and submit the file when you are finished working on it. You will see this option if your project is bound to Perforce or Subversion. See Unlocking Files.
	Opens the Get Latest Version dialog, which lets you "get" files from source control. After you bind a Analyzer project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Analyzer project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out. You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.
	Opens the Get Latest Version dialog, which lets you update files from source control. After you bind a Analyzer project to a Subversion, you can update any of the source control files. When you do this, you are copying the most current files stored in Subversion to your local Analyzer project. You will see this option if your project is bound to Subversion. See Updating or Getting the Latest Version of Source Control Files.
	Opens the Undo Check Out dialog, which lets you reverse the check-out of the files. If you have files checked out from source control but do not want them checked out anymore, you can use the "Undo Check Out" option instead of checking in the files. You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe. See Reverting or Undoing a Checkout of Source Control Files.
	Opens the Revert dialog, which lets you return files to their last known state. If you have modified files from source control but do not want to keep your modifications, you can use the "Revert" option instead of committing the files. While committing the file would save your changes to source control, reverting a file returns it to its previously committed state and does not commit any of your new changes to source control.When reverting changes made in Git, you only revert changes to the file on the branch you are currently editing. If you have a file that resides on multiple branches, copies of the file on other branches are preserved. You will see this option if your project is bound to Git, Perforce, or Subversion. See Reverting or Undoing a Checkout of Source Control Files.
	Opens a window pane that lets you view the content and code differences for files. If you select a single file and choose this option, the differences between the local version of the file and the source control version of the file are shown. If you select two files and choose this option, the differences between those two files are shown. You will see this option for all source control providers. See Viewing Differences in Source Control Files.
	Opens the History dialog, which lets you view the history of a particular source control file, including all of the occasions when the file has been checked in. You can then use the dialog to view the differences between older versions of the file or roll back to a particular version. You will see this option for all source control providers. See Viewing the History of Source Control Files and Rolling Back to an Earlier Version of a File.
	Undeletes a file, allowing you to add it to source control. You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce. See Undeleting Source Control Files.
	Refreshes the window pane so that the latest information is shown. You will see this option for all source control providers.
	Opens the Check In dialog, which lets you check all the files in the project into source control. When you are finished editing files, you can check them in to source control. Checking in a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically check in files so that you have a backup in source control. You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe.
	Opens the Commit dialog, which lets you commit all the files in the project into source control. When you are finished editing files, you can commit them to source control. If your project is bound to Git, committing a file adds your changes to the local database. When you are ready to add your local commits to the remote repository, you can push these files to the remote. This icon is Git-specific.
	Opens the Commit dialog, which lets you commit all the files in the project into source control. When you are finished editing files, you can commit them to source control. If your project is bound to Subversion, committing a file overwrites the old copy of the file in the source control database with the new one from your local machine. This icon is Subversion-specific.
	Opens the Submit dialog, which lets you submit all files in the project into source control. When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control. You will see this option if your project is bound to Perforce.
	Opens the Check Out dialog, which lets you check out all of the files in the project from source control. When you need to work on any of the Analyzer project files, you can check them out. Checking out files means to copy the latest source control files to your local Analyzer project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out. You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.
	Opens the Get Latest Version dialog, which lets you "get" all of the files in the project from source control. After you bind a Analyzer project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Analyzer project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out. See Updating or Getting the Latest Version of Source Control Files. You will see this option if your project is bound to Microsoft Team Foundation Server, Microsoft Visual SourceSafe, or Perforce.
	Opens the Get Latest Version dialog, which lets you update all of the files in the project from source control. After you bind a Analyzer project to a Subversion, you can update any of the source control files. When you do this, you are copying the most current files stored in Subversion to your local Analyzer project. You will see this option if your project is bound to Subversion. See Updating or Getting the Latest Version of Source Control Files.
	Opens the Undo Check Out dialog, which lets you reverse the check-out of all of the files in the project. If you have files checked out from source control but do not want them checked out anymore, you can use the "Undo Check Out" option instead of checking in the files. You will see this option if your project is bound to Microsoft Team Foundation Server or Microsoft Visual SourceSafe. See Reverting or Undoing a Checkout of Source Control Files.
	Opens the Revert dialog, which lets you return all files in the project to their last known state. If you have modified files from source control but do not want to keep your modifications, you can use the "Revert" option instead of committing the files. While committing the file would save your changes to source control, reverting a file returns it to its previously committed state and does not commit any of your new changes to source control.When reverting changes made in Git, you only revert changes to the file on the branch you are currently editing. If you have a file that resides on multiple branches, copies of the file on other branches are preserved. You will see this option if your project is bound to Git, Perforce, or Subversion. See Reverting or Undoing a Checkout of Source Control Files.
	Opens the Select Remote for Pull dialog, which lets you select the remote repository from which you will download remote files. After you select the repository you want to pull from, the remote files are retrieved from the repository and downloaded to your local project. If necessary, Analyzer will perform a commit before pulling your files. You will see this option if your project is bound to Git.
	Opens the Select Remote for Push dialog, which lets you select the remote repository to which you will upload your local commits. After you select the repository you want to push to, your files are sent to the remote repository. If necessary, Analyzer will perform a commit before pushing your files. You will see this option if your project is bound to Git. See Pushing Files to a Remote Repository—Git.
	Opens the Select Remote for Synchronize dialog, which lets you select the remote you want to use for a pull and push of files. After you select the repository, Analyzer pulls the remote files from the Git repository and merges them with your local database. Then Analyzer pushes your local changes back to the remote Git repository. If necessary, Analyzer will perform a commit before synchronizing your files. You will see this option if your project is bound to Git. See Synchronizing Source Control Files—Git.
	Opens the Branch Management dialog, which lets you create branches, switch to (select) a different branch, and delete an existing branch. Branches create a new development area for a file that is separate from the original. You can use branches so multiple authors can work in individual authoring spaces, or you can use them as a space to make major changes in your document without affecting the original (e.g., when documenting a new feature, rewriting large sections of a topic, or making layout changes). Even if others will not be working on a file, you can still create branches if you want to edit your file and then refer back to its previous versions. You will see this option if your project is bound to Git.
	Opens the Instant Messages window pane, which displays instant messages from other users and lets you send and configure instant messages. For more information see the Flare online Help.
	Opens the Send Request Check-In Message Dialog, which lets you ask another user to check in the selected files so that you can edit them. If you attempt to check out a source control file and discover that another user already has that file checked out, you can automatically send a request to that user to check in the file. This is a completely automated process involving instant messaging or email. Not only are the messages sent to the appropriate individuals automatically, but the mechanisms for checking in and checking out the necessary files are built in to those messages. This means that you and the other authors on your team do not need to hunt down the correct files manually. See Requesting a User to Check In Files.
	Opens the View File Request dialog, which lets you ask another user to view the selected file. If you have finished working on a file and want another user to review it, you can use the "Request View File" option. You can send an instant message or email to the other user with a message. That individual can then quickly open the specified file and send you comments about it. See Requesting a User to View Files.

window ribbon

	Opens the Manage Windows dialog, which lists the files that are currently open and lets you activate (i.e., switch to), save, or close a particular file.
	Closes open files. You can select the following from the submenu: Close All Documents Closes all files that you have opened in the workspace. Close All Documents Except This One Closes all files that you have opened in the workspace, with the exception of the document that is currently active.
	If you select the Dock option when a window pane is active, the Drag Pane area is shown or hidden in the window pane accordingly. The Drag Pane area lets you move the window pane and dock it elsewhere in the program window.
	"Pins" the active window pane or editor to the side of the interface so that you have more room for your workspace. You can show the window pane by hovering over the thin bar on the side of the interface. If you select the pin button at the top-right of the window pane, the window pane returns to its previous state (no longer pinned to the side of the interface).
	Converts the active window pane or editor to a floating window, which means it is no longer attached to the interface. This is a good option to use if you want to work on two topics side-by-side. If you do not want a window pane or editor to be floating anymore, you can right-click in the title bar and select Dock.
	Opens a submenu that lists the layouts. Select a layout to display it in the interface.
	Saves the window layout. You can select the following from the submenu: Save Window Layout If you are working in a particular layout and have opened different interface elements or moved interface elements around, you can select this option to save the changes to the layout. Save Window Layout As Opens the Rename Window Layout dialog, which lets you save the current interface configuration as a layout.
	If you are working in a particular layout and have opened different interface elements or moved interface elements around, you can select this option to return to the saved configuration of the layout.
	Returns the current configuration of the interface to the factory layout settings (the original layout when you first installed and launched Analyzer).
	Automatically saves the layout of the workspace when you exit Analyzer. The next time you launch Analyzer, that same layout will be displayed.

help ribbon

	Opens the Help system in a browser. By default, Analyzer's online and dynamic Help system points to files hosted externally. This allows for live updates to the Help. Because the Help system is hosted online, you may not be able to access it if you are behind a firewall or if you have a slow connection. In that case, you can use a local version of the Help. Analyzer will even switch to the local Help automatically if it detects that you cannot connect to the external Help system. If you want to use the local Help manually, open the Options dialog (File > Options), and on the General tab select Prefer Local Help. Note: The local Help system is only updated when the application is updated. If you want to be sure that you have the most current version of the Help, disable the local Help.
	Opens the Dynamic Help window pane, which automatically displays the Help topic related to the active element in the interface.
	Opens a Help topic that lets you access one of the printed guides related to Analyzer. See PDFs.
	Opens the MadCap Forums website, where you can obtain additional information about Analyzer and communicate with other Analyzer users.
	Opens the Activate Product Wizard, allowing you to activate the product.
	Deactivates the currently used license for the machine running Analyzer.
	Lets you register your version of Analyzer if you have not done so already. This option is enabled only if you are using a trial version of the software.
	Opens the New Updates Available dialog, which lets you download Analyzer updates from MadCap Software.
	Displays a popup that shows information about the current version of Analyzer. Click the popup to make it disappear.
	Opens your default Internet browser to the MadCap Software bug submission web page, where you can report the bug.