Use external editor to edit file filters (#2082774)
Improved command line handling (#2081779)
Change Manual url to http://winmerge.org/docs/manual/ (r5956)
+ Manual updates
Plugins: Show processing instructions in XML plugin (#1979321)
BugFix: ClearCase checkout/commit dialog translation error (#2051069)
BugFix: Table of Contents in manual (#2071625)
<?xml version="1.0" encoding="UTF-8"?>
<article id="AboutDoc">
- <title>About WinMerge online Help</title>
+ <title>About WinMerge Help</title>
- <para>This is online Help for WinMerge <xi:include href="replaceables.xml"
+ <para>This is Help for WinMerge <xi:include href="replaceables.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"
xpointer="element(version)" />.</para>
<section>
- <title>Audience</title>
+ <title>Audience and scope</title>
<para>WinMerge Help is intended for both new and experienced users. It
explains how to use WinMerge, and documents its capabilities and
</section>
<section>
- <title>Documentation conventions</title>
+ <title>Documentation conventions<indexterm>
+ <primary>conventions, documentation</primary>
+ </indexterm></title>
<informaltable>
<tgroup cols="2">
<article id="CommandLine">
<title>Command line<indexterm>
<primary>command line</primary>
-
- <secondary>syntax</secondary>
</indexterm><indexterm>
<primary>WinMerge command line</primary>
+
+ <see>command line</see>
</indexterm></title>
<para>The WinMerge command line accepts several parameters in addition to the
<indexterm>
<primary>filters</primary>
- <secondary>applying</secondary>
+ <secondary>applying in command line</secondary>
</indexterm>
<para><option>/f</option> applies a specified filter to restrict the
<listitem>
<indexterm>
<primary>conflict files</primary>
+
+ <secondary>specifying on command line</secondary>
</indexterm>
<para><option><replaceable>conflictfile</replaceable></option> Specifies a
<para>This topic describes how to compare and merge folders using the Folder
Compare window.</para>
- <xi:include href="Text_encoding.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="Text_encoding.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
<section id="Compare_dirs_starting">
<title>Starting a folder compare operation</title>
all files in the folders, and is nonrecursive (does not include
subfolders). To change any of these options and for more details about
the Select Files or Folder dialog, see <xref
- linkend="OpenPaths" />.<!--This topic focuses mainly on the WinMerge window method.--></para>
+ linkend="OpenPaths" />.</para>
</listitem>
</varlistentry>
<variablelist>
<varlistentry>
- <term>Recursive mode</term>
+ <term>Recursive mode<indexterm>
+ <primary>recursive folder compare</primary>
+ </indexterm></term>
<listitem>
<para>Recursive mode is useful for detecting and manipulating
<primary>Folder Compare window</primary>
<seealso>Compare windows</seealso>
+ </indexterm><indexterm>
+ <primary>Compare windows</primary>
+
+ <secondary>Folder</secondary>
+ </indexterm><indexterm>
+ <primary>subfolders</primary>
+
+ <secondary>in Folder Compare window</secondary>
</indexterm></title>
<para>The Folder Compare window shows the result of a folder compare in a
</section>
<section id="Compare_dirs_multiwin">
- <title>Working with multiple Folder Compare windows</title>
+ <title>Working with multiple Folder Compare windows<indexterm>
+ <primary>Folder Compare window</primary>
+
+ <secondary>using multiple</secondary>
+ </indexterm></title>
<para>By default, the WinMerge window displays a single Folder Compare
window. That is, if you start another file comparison while a Folder Compare
<primary>file operations</primary>
<secondary>in Folder Compare window</secondary>
+ </indexterm><indexterm>
+ <primary>Folder Compare window</primary>
+
+ <secondary>file operations</secondary>
</indexterm></title>
<para>The Folder Compare window supports common operations on files, like
<primary>Folder Compare window</primary>
<secondary>protecting files in</secondary>
+ </indexterm><indexterm>
+ <primary>protecting files</primary>
+ </indexterm><indexterm>
+ <primary>read-only files</primary>
+
+ <see>protecting files</see>
</indexterm></title>
<para>To protect the files and folders on either side of a compare from
<para>This topic describes how to use the WinMerge File Compare window to
compare and merge files. To understand the basic concepts about differences
- used here, we suggest you read read <xref linkend="IntroductDiffing" />
+ used here, we suggest you read <xref linkend="IntroductDiffing" />
first.</para>
- <xi:include href="Text_encoding.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="Text_encoding.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
<section id="Compare_files_starting">
<title>Starting a file compare operation</title>
<primary>File Compare window</primary>
<seealso>Compare windows</seealso>
+ </indexterm><indexterm>
+ <primary>Compare windows</primary>
+
+ <secondary>File</secondary>
</indexterm></title>
<para>The File Compare window displays compared files in two File panes,
</section>
<section id="Compare_files_merge">
- <title>Merging Differences<indexterm>
+ <title>Merging differences<indexterm>
<primary>merging differences</primary>
</indexterm></title>
</section>
<section id="ResolveConflictFiles">
- <title>Resolving Conflict Files<indexterm>
+ <title>Resolving conflict files<indexterm>
<primary>conflict files</primary>
</indexterm></title>
<section>
<title>Disable splash screen<indexterm>
- <primary>splash screen, disabling</primary>
+ <primary>splash screen, enabling and disabling</primary>
</indexterm></title>
<itemizedlist>
<title>Allow only one instance to run<indexterm>
<primary>WinMerge window</primary>
- <secondary>opening multiple</secondary>
+ <secondary>limiting instances</secondary>
</indexterm></title>
<itemizedlist>
</section>
<section>
- <title>Open-dialog Auto-Completion</title>
+ <title>Open-dialog Auto-Completion<indexterm>
+ <primary>MRU list</primary>
+ </indexterm></title>
<para>Choose one of these options:</para>
<section>
<title>Download 7-zip Plugin<indexterm>
- <primary>7-Zip archive support</primary>
+ <primary>7-Zip archives</primary>
- <secondary>options</secondary>
+ <secondary>configuring support after installation</secondary>
</indexterm></title>
<para>If WinZip is already installed on your system, WinMerge
</section>
<section>
- <title>Enable archive file support</title>
+ <title>Enable archive file support<indexterm>
+ <primary>7-Zip archives</primary>
+
+ <secondary>enabling and disabling integration</secondary>
+ </indexterm></title>
<para>This option controls how WinMerge handles archive files (based on
7-Zip integration).</para>
</section>
<section>
- <title>Detect archive type from file signature</title>
+ <title>Detect archive type from file signature<indexterm>
+ <primary>detecting archive types</primary>
+ </indexterm></title>
<itemizedlist>
<listitem>
<section>
<title>Add to explorer context menu<indexterm>
- <primary>shell integration</primary>
+ <primary>integration</primary>
- <secondary>enabling and disabling</secondary>
+ <secondary>with Windows shell</secondary>
</indexterm></title>
<itemizedlist>
<title>Version Control options<indexterm>
<primary>version control systems</primary>
- <secondary>integration configuration</secondary>
+ <secondary>configuring after installation</secondary>
+ </indexterm><indexterm>
+ <primary>integration</primary>
+
+ <secondary>with version control systems</secondary>
</indexterm></title>
<!--What does version control integration do for me? How do the Option page settings work with installed
<?xml version="1.0" encoding="UTF-8"?>
<article id="Filters">
<title>Using Filters<indexterm>
- <primary>filtering</primary>
+ <primary>filters</primary>
+
+ <seealso>file filters</seealso>
+
+ <seealso>file masks</seealso>
+
+ <seealso>line filters</seealso>
</indexterm></title>
<para>When you compare files or folders, you can use filters to narrow the
<secondary>file masks</secondary>
</indexterm><indexterm>
- <primary>filtering</primary>
+ <primary>filters</primary>
<secondary>in folder comparisons</secondary>
</indexterm></title>
omitted from your selection.</para>
<section id="Filters_MaskApply">
- <title>Defining and applying file masks</title>
+ <title>Defining and applying file masks<indexterm>
+ <primary>command line</primary>
+
+ <secondary>applying file masks</secondary>
+ </indexterm></title>
<para>Define and apply a file mask at the time you launch your folder
compare operation:</para>
</indexterm><indexterm>
<primary>filters</primary>
- <secondary>file mask syntax</secondary>
+ <secondary>file masks</secondary>
</indexterm><indexterm>
<primary>regular expressions</primary>
</section>
<section id="Filters_FileFilter">
- <title>Using File filters<indexterm>
+ <title>Using file filters<indexterm>
<primary>filters</primary>
<secondary>file filters</secondary>
</indexterm><indexterm>
- <primary>filtering</primary>
+ <primary>filters</primary>
<secondary>in folder comparisons</secondary>
</indexterm></title>
</section>
<section id="Filters_FileFilterApply">
- <title>Applying file filters</title>
+ <title>Applying file filters<indexterm>
+ <primary>file filters</primary>
+
+ <secondary>applying</secondary>
+ </indexterm></title>
<para>You can apply a file filter using any of these methods:</para>
</listitem>
<listitem>
- <para>When you launch a folder compare from the WinMerge command line,
- use the <option>-f</option> flag to specify a file filter.</para>
+ <para><indexterm>
+ <primary>command line</primary>
+
+ <secondary>applying file filters</secondary>
+ </indexterm>When you launch a folder compare from the WinMerge
+ command line, use the <option>-f</option> flag to specify a file
+ filter.</para>
</listitem>
</itemizedlist>
<secondary>file filter</secondary>
</indexterm><indexterm>
- <primary>filters</primary>
+ <primary>file filters</primary>
- <secondary>file filter syntax</secondary>
+ <secondary>syntax</secondary>
</indexterm></title>
<para>This section describes the syntax of WinMerge file filters and
</section>
<section id="Filters_LineFilter">
- <title>Using Line filters<indexterm>
+ <title>Using line filters<indexterm>
<primary>filters</primary>
- <secondary>line filters</secondary>
+ <secondary>line</secondary>
</indexterm><indexterm>
- <primary>filtering</primary>
+ <primary>filters</primary>
<secondary>in file comparisons</secondary>
</indexterm></title>
</indexterm><indexterm>
<primary>filters</primary>
- <secondary>line filter syntax</secondary>
+ <secondary>line</secondary>
</indexterm><indexterm>
<primary>regular expressions</primary>
<tip>
<para>It's usually good practice to use the beginning of line (
- <code>^</code> ) and end of line ( <code>&</code> ) of line markers
- to control your patterns precisely, because the rule is applied if any
- part of a line matches the expression.</para>
+ <code>^</code> ) and end of line ( <code>&</code> ) markers to
+ control your patterns precisely, because the rule is applied if any part
+ of a line matches the expression.</para>
</tip>
<example>
<example>
<title>Line filter rule matching CVS Id lines</title>
- <para>Id lines look like this:</para>
+ <para>CVS Id lines look like this:</para>
<screen>// $Id$</screen>
<?xml version="1.0" encoding="UTF-8"?>
<article id="Installing">
- <title>Getting and installing WinMerge</title>
+ <title>Getting and installing WinMerge<indexterm>
+ <primary>installing WinMerge</primary>
+ </indexterm></title>
<para>WinMerge can be installed using the installer or by unzipping files from
an archive. Using the installer is the recommended method.</para>
<variablelist>
<varlistentry>
- <term>WinMerge core files</term>
+ <term>WinMerge core files<indexterm>
+ <primary>WinMerge executables, Unicode and ANSI</primary>
+ </indexterm></term>
<listitem>
<para>WinMerge executable (<filename>WinMerge.exe</filename> on
<listitem>
<para>In the Select Additional Tasks page, specify any additional
- tasks:</para>
+ tasks:<indexterm>
+ <primary>integration</primary>
+
+ <secondary>with version control system</secondary>
+ </indexterm><indexterm>
+ <primary>VCS</primary>
+
+ <see>version control systems</see>
+ </indexterm></para>
<variablelist>
<varlistentry>
</varlistentry>
<varlistentry>
- <term>Integrate with TortoiseCVS</term>
+ <term>Integrate with TortoiseCVS<indexterm>
+ <primary>TortoiseCVS integration</primary>
+ </indexterm></term>
<listitem>
<para>Sets WinMerge to be the TortoiseCVS diff application.</para>
</varlistentry>
<varlistentry>
- <term>Integrate with TortoiseSVN</term>
+ <term>Integrate with TortoiseSVN<indexterm>
+ <primary>TortoiseSVN integration</primary>
+ </indexterm></term>
<listitem>
<para>Sets WinMerge to be the TortoiseSVN diff application</para>
</varlistentry>
<varlistentry>
- <term>Integrate with ClearCase</term>
+ <term>Integrate with ClearCase<indexterm>
+ <primary>ClearCase integration</primary>
+
+ <secondary>configuring during installation</secondary>
+ </indexterm></term>
<listitem>
<para>Sets WinMerge to be the ClearCase diff and merge
</section>
<section id="InstallFromArchive">
- <title>Installing from an archive</title>
+ <title>Installing from an archive<indexterm>
+ <primary>archive, installing Winmerge from</primary>
+ </indexterm><indexterm>
+ <primary>mfc71[u].dll runtime file</primary>
+ </indexterm><indexterm>
+ <primary>msvcr71.dll runtime file</primary>
+ </indexterm><indexterm>
+ <primary>msvcp71.dll runtime file</primary>
+ </indexterm></title>
<para>WinMerge is pretty much independent of other system components. It is
not tightly integrated with Windows, and does not use many DLLs.</para>
</section>
<section>
- <title>Shell integration</title>
+ <title>Shell integration<indexterm>
+ <primary>integration</primary>
+
+ <secondary>with Windows shell</secondary>
+ </indexterm><indexterm>
+ <primary>Windows shell integration</primary>
+ </indexterm></title>
<para>The installer enables shell integration when you choose the
<guilabel>Enable Explorer context menu integration</guilabel> option in the
Windows updates all its references.</para>
<section>
- <title>64-bit shell integration</title>
+ <title>64-bit shell integration<indexterm>
+ <primary>Windows 64-bit versions, WinMerge support</primary>
+ </indexterm></title>
<para>Starting with Version 2.6, WinMerge supports 64-bit Windows versions
by including 64-bit shell integration. The WinMerge installer recognizes
<section id="Installing_archive_support">
<title><indexterm>
<primary>installing archive support</primary>
+ </indexterm><indexterm>
+ <primary>7-Zip archives</primary>
+
+ <secondary>configuring support during installation</secondary>
</indexterm>7-Zip and archive support</title>
<para>WinMerge uses <ulink url="http://www.7-zip.org/">7-Zip</ulink> for
</menuchoice>.</para>
<section id="Install_merge7zinstaller">
- <title>Merge7zInstaller</title>
+ <title>Merge7z Installer<indexterm>
+ <primary>Merge7z installer</primary>
+ </indexterm></title>
<para><filename>Merge7zInstaller</filename> is a stand-alone installer for
7-Zip integration.</para>
operations.</para>
<section id="Intro_diffs_comparing">
- <title>Comparing files</title>
+ <title>Comparing files<indexterm>
+ <primary>comparing files</primary>
+
+ <secondary>overview</secondary>
+ </indexterm></title>
<para>We usually compare two files that are related in some way, such as two
versions that were edited at different times, or by different people. If you
breaks exactly:</para>
<formalpara>
- <title>Fle1:</title>
+ <title>File1:</title>
<para><screen>It's slow comparing words
and characters. Instead,
</section>
<section id="Intro_diffs_merging">
- <title>Merging files</title>
+ <title>Merging files<indexterm>
+ <primary>merging differences</primary>
+
+ <secondary>overview and example</secondary>
+ </indexterm></title>
<para>The purpose of merging is to combine changes from two files into one
file. Merging extends the concepts and functions used in comparing
</section>
<section>
- <title>Choosing a merge result file</title>
+ <title>Choosing a merge result file <indexterm>
+ <primary>merging differences</primary>
+
+ <secondary>result file</secondary>
+ </indexterm><indexterm>
+ <primary>result file, in merge</primary>
+ </indexterm></title>
<para>You control where your merge result is preserved. The WinMerge File
Compare window does not have a separate result pane, as some merge tools
the advantage of all WinMerge users.</para>
<section>
- <title>WinMerge versions</title>
+ <title>WinMerge versions<indexterm>
+ <primary>WinMerge versions</primary>
+ </indexterm></title>
<para>There are three kind of versions available in the <ulink
url="https://sourceforge.net/project/showfiles.php?group_id=13216">downloads</ulink>
<section>
<title><indexterm>
- <primary>Stable versions</primary>
+ <primary>stable WinMerge versions</primary>
</indexterm>Stable versions</title>
<para><ulink
<section>
<title><indexterm>
- <primary>Beta versions</primary>
+ <primary>beta WinMerge versions</primary>
</indexterm>Beta versions</title>
<para><ulink
<section>
<title><indexterm>
- <primary>Experimental versions</primary>
+ <primary>experimental WinMerge versions</primary>
</indexterm>Experimental versions</title>
<para><ulink
<section>
<title><indexterm>
- <primary>support</primary>
+ <primary>WinMerge support</primary>
<secondary>reporting bugs</secondary>
</indexterm>Getting support and reporting bugs</title>
<?xml version="1.0" encoding="UTF-8"?>
<article id="Locales">
- <title>Locale support</title>
+ <title>Locale support<indexterm>
+ <primary>localizing WinMerge </primary>
+ </indexterm></title>
<para>The WinMerge user interface is in English by default, but you can
- localize your installation to other languages for which translations have
- been contributed. Localizing WinMerge changes text strings that are
- displayed in the interface, including menus, dialogs, tooltips, and messages,
- to the language you choose.</para>
+ localize your installation to other languages for which translations have been
+ contributed. Localizing WinMerge changes text strings that are displayed in
+ the interface, including menus, dialogs, tooltips, and messages, to the
+ language you choose.</para>
<para>Note that localization does not extend beyond the translation of
strings. For example, it does not affect how numbers are divided or how words
</section>
<section>
- <title>Available WinMerge localizations</title>
+ <title>Available WinMerge localizations<indexterm>
+ <primary>localizations, available</primary>
+ </indexterm></title>
<para>WinMerge localizations contributed to date include the following
translations:</para>
</section>
<section>
- <title>Reporting errors in translation</title>
+ <title>Reporting errors in translation<indexterm>
+ <primary>translations, reporting errors</primary>
+ </indexterm></title>
<para>Please submit any errors you find in translations as bugs to our
<ulink
</section>
<section>
- <title>Submitting a new translation</title>
+ <title>Submitting a new translation<indexterm>
+ <primary>submitting translations</primary>
+ </indexterm></title>
<para>If you would like to add your language to the list, read the <ulink
url="http://winmerge.org/translations/">Translations</ulink> documentation
<?xml version="1.0" encoding="UTF-8"?>
<article id="OpenPaths">
- <title>Opening files and folders</title>
+ <title>Opening files and folders<indexterm>
+ <primary>opening files and folders</primary>
+ </indexterm></title>
<para>WinMerge provides several ways to specify paths and open files or
- folders:</para>
+ folders:<indexterm>
+ <primary>folders</primary>
+
+ <secondary>selecting in Select Files or Folders dialog</secondary>
+ </indexterm><indexterm>
+ <primary>files</primary>
+
+ <secondary>selecting in Select Files or Folders dialog</secondary>
+ </indexterm></para>
<itemizedlist>
<listitem>
</itemizedlist>
<section id="OpenPaths_opendialog">
- <title>Select Files or Folders dialog</title>
+ <title>Select Files or Folders dialog<indexterm>
+ <primary>Select Files or Folders dialog</primary>
+ </indexterm></title>
<para><xref linkend="QuickStart" /> describes the Select Files or Folders
dialog. This section provides more details, and some tips for using the
Select Files or Folders dialog more efficiently.</para>
<section>
- <title>Using environment variables</title>
+ <title>Using environment variables<indexterm>
+ <primary>environment variables, in compare target paths</primary>
+ </indexterm></title>
<para>You can use environment variables in your paths. Windows expands the
variable name between % (percent) delimiters. For example, if an
</section>
<section id="OpeningArchives">
- <title>Opening archive files</title>
+ <title>Opening archive files<indexterm>
+ <primary>7-Zip archives</primary>
+
+ <secondary>opening</secondary>
+ </indexterm></title>
<para>WinMerge archive support is provided in the 7-Zip plugin. See <xref
linkend="Installing" /> to install this plugin.</para>
</section>
<section id="Open_paths_filters">
- <title>Specifying filters</title>
+ <title>Applying filters<indexterm>
+ <primary>filters</primary>
+
+ <secondary>applying in Select Files or Folders dialog</secondary>
+ </indexterm></title>
<para>The <guilabel>Filter</guilabel> edit field enables you to restrict
the files to be included in your folder compare. You can specify one or
selecting, use filter files. Filter files are collections of regular
expressions that can either include or exclude files. WinMerge installs a
number of predefined filter files in its <filename>Filters</filename>
- folder, and you can create your own, too. </para>
+ folder, and you can create your own, too.</para>
<para>To specify a filter, click the <guibutton>Select</guibutton> button
next to the <guilabel>Filters</guilabel> field to choose from a list of
</section>
<section id="Open_paths_unpacker">
- <title>Selecting an unpacker for file comparisons</title>
+ <title>Selecting an unpacker for file comparisons<indexterm>
+ <primary>unpacker plugins</primary>
+ </indexterm></title>
<para>Unpackers are plugins that are installed with WinMerge to provide
functionality that is not used by default. Plugins that can be used to
<section id="OpenPaths_shell-integ">
<title><indexterm>
- <primary>shell integration</primary>
+ <primary>Windows shell integration</primary>
+ </indexterm><indexterm>
+ <primary>context menu, WinMerge shortcuts in Windows Explorer</primary>
</indexterm>Shell integration</title>
- <para>The WinMerge shell Integration is a convenient way to select paths and
+ <para>The Windows shell Integration is a convenient way to select paths and
open WinMerge directly from Windows Explorer. It adds a
<guimenuitem>WinMerge</guimenuitem> shortcut in the Explorer context menu
(available when you right-click one or two files or folders in Explorer).
</section>
<section>
- <title>Including Subfolders</title>
+ <title>Including Subfolders<indexterm>
+ <primary>recursive folder compare</primary>
+
+ <secondary>specifying in Select Files or Folders dialog</secondary>
+ </indexterm><indexterm>
+ <primary>subfolders</primary>
+
+ <seealso>recursive folder compare</seealso>
+ </indexterm></title>
<para>By default, WinMerge does not include subfolders in compare
operations. To change the default behavior, enable <guilabel>Include
<section id="OpenPaths_dragndrop">
<title><indexterm>
- <primary>drag and drop</primary>
+ <primary>drag and drop, in WinMerge window</primary>
</indexterm>Drag and drop</title>
<para>From any Windows source that allows you to drag objects, such as
<section id="OpenPaths_project">
<title><indexterm>
<primary>project files</primary>
+ </indexterm><indexterm>
+ <primary>command line</primary>
+
+ <secondary>specifying project files</secondary>
</indexterm>Project files</title>
<para>You can save the currently open paths and filters in a project file.
Project files are handy if you compare the same files repeatedly.</para>
<section>
- <title>Project files</title>
+ <title>Using project files</title>
- <para>You can specify a project file as a command line argument, just like
- a normal file. In the WinMerge window, click <menuchoice>
+ <para>To use a project file In the WinMerge window, click <menuchoice>
<guimenu>File</guimenu>
<guimenuitem>Open Project</guimenuitem>
</menuchoice>. WinMerge reads the paths from the project file. If the
project file has two paths, both paths are opened. If only one path is
given or one of paths is invalid, WinMerge opens the Select Files or
- Folders dialog, where you can add or correct the path information.</para>
-
- <para>A project file can also be opened in the Select Files or Folders
- dialog. Here are a few things to consider:</para>
+ Folders dialog, where you can add or correct the path information. Here
+ are a few things to consider:</para>
<itemizedlist>
<listitem>
file are compared.</simpara>
</listitem>
</itemizedlist>
+
+ <para>To specify a project file on the command line, simply enter it as a
+ single file path.</para>
</section>
<section>
<?xml version="1.0" encoding="UTF-8"?>
<article id="Plugins">
- <title>Plugins</title>
+ <title>Plugins<indexterm>
+ <primary>plugins</primary>
+ </indexterm></title>
<para>WinMerge plugins are custom dlls or scriptlets, written in the COM API,
that preprocess data before a comparison. For example, you can use a plugin to
provide are of interest to only a few users, or because they do not fit into
the WinMerge architecture.</para>
- <para>Each plugin is:</para>
+ <para>Each plugin is:<indexterm>
+ <primary>installing plugins</primary>
+ </indexterm></para>
<itemizedlist>
<listitem>
<variablelist>
<varlistentry>
- <term>Editor complement</term>
+ <term>Editor complement<indexterm>
+ <primary>editor complement plugins</primary>
+ </indexterm></term>
<listitem>
<para>This type of plugin performs custom operations on selected text
</varlistentry>
<varlistentry>
- <term>Unpacker: transform a file to a text format</term>
+ <term>Unpacker: transform a file to a text format<indexterm>
+ <primary>unpacker plugins</primary>
+ </indexterm></term>
<listitem>
<para>This type of plugin transforms a compressed file to a viewable
</varlistentry>
<varlistentry>
- <term>Prediffer: preprocess files to hide some differences</term>
+ <term>Prediffer: preprocess files to hide some differences<indexterm>
+ <primary>prediffer plugins</primary>
+ </indexterm></term>
<listitem>
<para>This type of plugin does not operate on the source files
<para>To apply plugins when automatic unpacking is set, simply launch a
compare operation on a file in the Folder Compare window. If the file's
type suggested unpacker plugin (if any) preprocesses the file before
- WinMerge opens it in the File Compare window. </para>
+ WinMerge opens it in the File Compare window.</para>
<para>For example, suppose you right-click an MS Word
<filename>doc</filename> file and choose
<guimenuitem>Compare</guimenuitem> (also assume that the <xref
linkend="Plugins_msword" /> plugin is available). WinMerge converts the
doc file (or rather, a copy of it ) to a plain text file and opens it in
- the File Compare window. </para>
+ the File Compare window.</para>
</section>
<section>
<orderedlist>
<listitem>
- <para>Select the file you want to compare. </para>
+ <para>Select the file you want to compare.</para>
</listitem>
<listitem>
<guimenu>Plugins</guimenu>
<guimenuitem>Edit with Unpacker</guimenuitem>
- </menuchoice>. </para>
+ </menuchoice>.</para>
<para>This menu item is enabled only if the selected file's type is
supported by an available unpacking plugin.</para>
</section>
<section id="Plugins_available">
- <title>Available plugins</title>
+ <title>Available plugins<indexterm>
+ <primary>Visual Basic dlls for plugins</primary>
+ </indexterm><indexterm>
+ <primary>plugins</primary>
+
+ <secondary>Visual Basic dlls</secondary>
+ </indexterm></title>
<section>
- <title><filename>CompareMSExcelFiles.dll</filename></title>
+ <title><filename>CompareMSExcelFiles.dll<indexterm>
+ <primary>CompareMSExcelFiles.dll plugin file</primary>
+ </indexterm></filename></title>
<para>Displays the text contents of a <trademark
class="registered">Microsoft</trademark> <application>Excel</application>
</section>
<section id="Plugins_msword">
- <title><filename>CompareMSWordFiles.dll</filename></title>
+ <title><filename>CompareMSWordFiles.dll<indexterm>
+ <primary>CompareMSWordFiles.dll plugin file</primary>
+ </indexterm></filename></title>
<para>Displays the text content of a <trademark
class="registered">Microsoft</trademark> <application>Word</application>
</section>
<section id="DisplayXMLFiles">
- <title><filename>DisplayXMLFiles.dll</filename></title>
+ <title><filename>DisplayXMLFiles.dll<indexterm>
+ <primary>DisplayXMLFiles.dll plugin file</primary>
+ </indexterm></filename></title>
<para>This plugin pretty-prints XML files nicely by inserting tabs and
line breaks. This is useful for XML files that do not have line returns in
</section>
<section id="EditorAddin">
- <title><filename>editor addin.sct</filename></title>
+ <title><filename>editor addin.sct<indexterm>
+ <primary>editor addin.sct plugin file</primary>
+ </indexterm></filename></title>
<para>Adds two functions to the <menuchoice>
<guimenu>Edit</guimenu>
</section>
<section id="IgnoreColumns">
- <title><filename>IgnoreColumns.dll</filename></title>
+ <title><filename>IgnoreColumns.dll<indexterm>
+ <primary>IgnoreColumns.dll plugin file</primary>
+ </indexterm></filename></title>
<para>This plugin ignores characters at specified columns. The first
column is number 1</para>
</section>
<section>
- <title><filename>IgnoreCommentsC.dll</filename></title>
+ <title><filename>IgnoreCommentsC.dll<indexterm>
+ <primary>IgnoreCommentsC.dll plugin file</primary>
+ </indexterm></filename></title>
<para>The plugin ignores comments within<constant> //</constant>... and
<constant>/*</constant> ... <constant>*/</constant> delimiters in C, C++,
</section>
<section>
- <title><filename>IgnoreFieldsComma.dll</filename></title>
+ <title><filename>IgnoreFieldsComma.dll<indexterm>
+ <primary>IgnoreFieldsComma.dll plugin file</primary>
+ </indexterm></filename></title>
<para>This plugin is for files with fields and commas as delimiters (CSV
files, for example). It ignores the delimiter characters. The first field
</section>
<section>
- <title><filename>IgnoreFieldsTab.dll</filename></title>
+ <title><filename>IgnoreFieldsTab.dll<indexterm>
+ <primary>IgnoreFieldsTab.dll plugin file</primary>
+ </indexterm></filename></title>
<para>This plugin is for files that use fields and tabs as delimiters
(<application>for examle, Excel</application> files saved in the <filename
</section>
<section>
- <title><filename>IgnoreLeadingLineNumbers.dll</filename></title>
+ <title><filename>IgnoreLeadingLineNumbers.dll<indexterm>
+ <primary>IgnoreLeadingLineNumbers.dll plugin file</primary>
+ </indexterm></filename></title>
<para>This plugin ignores the leading line numbers in text files (for
example, NC and BASIC files).</para>
</section>
<section id="Plugins_datetime">
- <title><filename>insert datetime.sct</filename></title>
+ <title><filename>insert datetime.sct<indexterm>
+ <primary>insert datetime.sct plugin file</primary>
+ </indexterm></filename></title>
<para>Adds two functions to the <menuchoice>
<guimenu>Edit</guimenu>
<section>
<title><filename>RCLocalizationHelper.dll</filename>,
- <filename>RCLocalizationHelperU.dll</filename></title>
+ <filename>RCLocalizationHelperU.dll<indexterm>
+ <primary>RCLocalizationHelper.dll, RCLocalizationHelperU.dll plugin
+ files</primary>
+ </indexterm></filename></title>
<para>This plugin preprocesses RC files by stripping out localized
strings, to enable comparing different language versions of the same RC
<section>
<title><filename>WatchBeginningOfLog.dll</filename>,
- <filename>WatchEndOfLog.dll</filename></title>
+ <filename>WatchEndOfLog.dll<indexterm>
+ <primary>WatchBeginningOfLog.dll, WatchEndOfLog.dll plugin
+ files</primary>
+ </indexterm></filename></title>
<para>For long LOG files, often only in the first lines or in the last
lines are significant.</para>
</section>
<section>
- <title>Requirements</title>
+ <title>Requirements<indexterm>
+ <primary>plugins</primary>
+
+ <secondary>Windows Script Host requirement</secondary>
+ </indexterm></title>
<section>
<title>Windows Script Host</title>
</section>
<section id="MSVBVM60">
- <title><application>Visual Basic</application> runtime library</title>
+ <title><application>Visual Basic</application> runtime library<indexterm>
+ <primary>Visual Basic dlls for plugins</primary>
+ </indexterm><indexterm>
+ <primary>plugins</primary>
+
+ <secondary>Visual Basic dlls</secondary>
+ </indexterm><indexterm>
+ <primary>msvbvm60.dll plugin file</primary>
+ </indexterm><indexterm>
+ <primary>Run-Time Redistribution Pack, for Visual Basic
+ library</primary>
+ </indexterm></title>
<para>Some plugins require <application>the Visual Basic</application>
runtime library to work.</para>
<title><indexterm>
<primary>getting started with WinMerge</primary>
</indexterm><indexterm>
- <primary>opening files and folders</primary>
+ <primary>choosing files and folders</primary>
<secondary>getting started</secondary>
- </indexterm>Opening files and folders</title>
+ </indexterm>Selecting files and folders to compare</title>
<para>After you have installed WinMerge, step through the procedure and
discussions in this topic to learn basic WinMerge operations and concepts.
<orderedlist>
<listitem>
<para>Open the WinMerge window. Here are some of the methods you can
- use:</para>
+ use:<indexterm>
+ <primary>WinMerge window</primary>
+ </indexterm></para>
<itemizedlist>
<listitem>
</orderedlist>
<section>
- <title>Other ways to open files and folders</title>
+ <title>Other ways to open files and folders<indexterm>
+ <primary>project files</primary>
+ </indexterm><indexterm>
+ <primary>command line</primary>
+
+ <secondary>opening files and folders</secondary>
+ </indexterm></title>
<para>The Select Files or Folders dialog is the main interface for opening
files and folders. But you can use many other ways, too:</para>
</authorgroup>
</bookinfo>
+ <!--Note to maintainers: Not all doc files are included in this file. There are also fragment files included at the topic
+level. For example, several files include elements from replaceables.xml. Other fragment files are select-unpacker.xml
+and Text_encoding.xml. Pleaes do not delete xml files in this directory unless you know for sure that they are not used.-->
+
&AboutDoc;
&QuickStart;
&ShortCuts;
- <index id="word_index"/>
+ <index id="word_index"></index>
</book>
OSDN Git Service
