From ef5569d750c90d865b52eb8118275cab976cd401 Mon Sep 17 00:00:00 2001 From: Kimmo Varis Date: Tue, 15 Jul 2008 14:02:15 +0000 Subject: [PATCH] PATCH: [ 2017901 ] Copy edit help topic Fix typos, minor edit to two topics Submitted by Denis Bradford --- Docs/Users/Manual/Intro_diffs.xml | 44 ++++++++++++++++++--------------------- Docs/Users/Manual/Open_paths.xml | 2 +- 2 files changed, 21 insertions(+), 25 deletions(-) diff --git a/Docs/Users/Manual/Intro_diffs.xml b/Docs/Users/Manual/Intro_diffs.xml index 1a367234f..6177f99c1 100644 --- a/Docs/Users/Manual/Intro_diffs.xml +++ b/Docs/Users/Manual/Intro_diffs.xml @@ -7,18 +7,18 @@
Comparing files - If you compare two files, you can easily identify several types of differences: different characters and words, different lines, even entire blocks of text that are different. But trying understanding all the differences between two files by scanning them in your favorite editor can be tedious and error-prone. Specialized difference/merging tools like WinMerge can make this work much easier and more efficient. + 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 examine two such files you can usually see some similar areas, and also identify several types of differences: different characters and words, different lines, even entire blocks of text that are different. But trying to understanding all the differences between two files by scanning them in your favorite editor can be tedious and error-prone. Specialized difference/merging tools like WinMerge are designed make this work more systematic and efficient. - A spell checker is a useful difference utility: it can systematically step you through a document, highlight words that are different from those in its dictionary, and help you resolve each spelling problem. However, looking only at characters and words is not an effective way to do more complicated comparisons: many text utilities use lines as the basic unit of comparison instead. + For example, a spell checker is a difference utility that most people have used: it can systematically step you through a document, highlight words that are different from those in its dictionary, and help you resolve each spelling problem. However, looking only at characters and words is not an effective way to do more complicated comparisons: many text utilities use lines as the basic unit of comparison instead. - WinMerge also uses lines as its basic unit of difference. Words and spaces are not treated individually in comparing and merging operations. To illustrate: if two files have identical lines except that in one file, the last line has four different words and an extra space, then we say that the file has one difference, not five. + WinMerge also uses lines as its basic unit of difference. Words and spaces are not treated individually in comparing and merging operations. To illustrate, consider two files that are identical except for one line that is different. If the two versions of the line have four words that are different and one version has an extra space, then we say that the file has one difference, not five. - It's easy to identify individual lines that are different. But sometimes it is useful to treat an entire block of lines that are different as a single difference, instead of comparing one line at a time. As we will see later, detecting multiple-line differences makes merging more efficient too. + If it's quicker to compare lines than characters, sometimes it's also useful to treat an entire block of lines as a single difference, instead of comparing one line at a time. As we will see later, detecting multiple-line differences makes merging more efficient too.
Simple compare operation - This section offers a simple example that demonstrates how to compare line difference between two files in WinMerge: + This section offers a simple example that demonstrates how to compare line differences between two files in WinMerge: @@ -40,8 +40,6 @@ Believe it or else. WinMerge compares lines. Believe it or not. - - The files are similar enough that they might be later versions of the same file. @@ -76,7 +74,7 @@ Believe it or not. Number of differences - The message in the status bar (at the bottom) tells you that two differences were detected. Read on to learn how to identify them. + The message in the status bar (at the bottom) tells you that two differences were detected. @@ -84,7 +82,7 @@ Believe it or not. Difference colors - WinMerge marks detected differences with various background colors (which you can configure in WinMerge options). The basic difference color is gold, by default. Within each line difference, WinMerge marks words and characters that are different with a lighter background color. Identical lines (like the third line in the example) are unmarked: they have white backgrounds. + WinMerge marks differences with various background colors (which you can configure in WinMerge options). The basic difference color is gold, by default. Within each line difference, WinMerge marks words and characters that are different with a lighter background color. Identical lines (like the third line in the example) are unmarked: they have white backgrounds. @@ -119,7 +117,7 @@ Believe it or not. Alt Enter - ). If this button is not enabled (for example, if your cursor is in a different line of the file), click + ). If this button is not enabled (for example, if your cursor is in a different line), click @@ -133,7 +131,7 @@ Believe it or not. Home ) instead. - When you select a difference, the two versions are loaded in the Diff pane. The Diff pane is useful for confirming which lines are included, and for examining them in isolation from the rest of the file. In our example, Difference 1 clearly has two lines. + When you select a difference, the two versions are loaded in the Diff pane. The Diff pane confirms which lines are included in a difference, and lets you examine them in isolation from the rest of the file. In our example, Difference 1 clearly has two lines. @@ -161,7 +159,7 @@ Believe it or not. Enter ). This jumps over the identical line (which is not a difference) and selects the last line. - You have reached the end of the file and had a chance to examine every difference. This was a trivial example — there were only two differences, and there are other ways to compare differences in WinMerge — but it demonstrates the efficiency of using the WinMerge navigation controls. + You have reached the end of the file and had a chance to examine every difference. This was a trivial example — there were only two differences — and there are other ways to compare differences in WinMerge. But it demonstrates the efficiency of using the WinMerge navigation controls.
@@ -170,20 +168,18 @@ Believe it or not.
Merging files - The purpose of merging is to combine changes from two files into one file. Merging concepts and functions build on the comparing operation: please read the preceding section before beginning this section. In addition to detecting differences between two file versions, we resolve the differences and save the result in a single target version. - - An environment without merging is simple but constrained: you must always update files sequentially. Two people cannot work on the same file concurrently, and once you create two versions of a file, they must be maintained separately. + The purpose of merging is to combine changes from two files into one file. Merging extends the concepts and functions used in comparing operation: please read the preceding section before beginning this section. In addition to detecting differences between two file versions, we resolve the differences and save the result in a single target version. - Merging files makes concurrent development possible, and it is a common occurrence in team environments. For example, suppose you and another person want to add code to the same program file at the same time. You both begin with an identical copy of the file, but during development you create separate versions that are not identical. At some point, the two versions must be merged into one version that preserves the changes from each contributor. + Merging files makes concurrent development possible, and it is a common task in team environments. For example, suppose you and another person want to add code to the same program file at the same time. You both begin with an identical copy of the file, but during development you create separate versions that are not identical. At some point, the two versions must be merged into one version that preserves the changes from each contributor. - Merging can be prompted (or even initiated) by version control systems like Subversion and ClearCase. For example, your version control system might prevent you from submitting changes to its repository because of a conflict. A conflict can occur if someone else checked in a different version of the same file while you were working on your version, and the version control system was not able to automatically merge the differences. When that happens, you might need to merge the conflicting versions before trying again to contribute your version. Many systems have integrated difference and merge tools, but you might prefer to use WinMerge instead. + Merging can be prompted (or even initiated) by version control systems like Subversion and ClearCase. For example, your version control system might prevent you from submitting changes to its repository because of merge conflicts. A conflict can occur if someone else checked in a different version of the same file while you were working on your version, and the version control system was not able to automatically merge the differences. When that happens, you might need to merge the conflicting versions before trying again to contribute your version. Many systems have integrated difference and merge tools, but you might prefer to use WinMerge instead. - Just as with comparing, you use WinMerge's toolbar controls (or keyboard shortcuts) to systematically step through each difference. Resolve each difference by copying either its left or right candidate to the other side. When you have resolved all the differences, WinMerge lets you know that all differences are resolved (the versions are identical), and you are done merging. + Just as with comparing, you use WinMerge's toolbar controls (or keyboard shortcuts) to systematically step through the differences. Resolve each difference by copying either its left or right candidate to the other side. When you have resolved all the differences, WinMerge lets you know that all differences are resolved (the versions are identical), and you are done merging.
Simple merge operation - This short exercise demonstrates how use the controls in the File Compare window to merge the simple files shown earlier, in only a few steps: + This short exercise demonstrates how to use the controls in the File Compare window in a systematic way to merge the simple files shown earlier: @@ -203,7 +199,7 @@ Believe it or not. First Difference button - First Difference instead. + First Difference instead. @@ -215,7 +211,7 @@ Believe it or not. Copy Right button - Copy Right to merge difference 1 from File1 to File2. In File 2, notice that the single difference line is replaced by the two lines from File1, and the gray blank line is now gone. + Copy Right to merge difference 1 from File1 to File2. In File2, notice that the single difference line is replaced by the two lines from File1, and the gray blank line is now gone. @@ -227,7 +223,7 @@ Believe it or not. Next Difference button - Next Difference to select difference 2. This is easier than finding and selecting the difference yourself. It's especially useful if you want to step through all differences without accidentally missing any. + Next Difference to select Difference 2. This is easier than finding and selecting the difference yourself. It's especially useful if you want to step through all differences without accidentally missing any. @@ -239,7 +235,7 @@ Believe it or not. Copy Left button - Copy Left to merge difference 2 from File2 to File1. + Copy Left to merge Difference 2 from File2 to File1. The message that the the files are identical tells you that the merge is complete: @@ -251,7 +247,7 @@ Believe it or not. - Click OK to dismiss the message. The status Difference message changes from Difference of 1 to identical. + Click OK to dismiss the message. The status Difference message changes from Difference 1 of 1 to identical. diff --git a/Docs/Users/Manual/Open_paths.xml b/Docs/Users/Manual/Open_paths.xml index 05eb1ee69..cffbc3f63 100644 --- a/Docs/Users/Manual/Open_paths.xml +++ b/Docs/Users/Manual/Open_paths.xml @@ -83,7 +83,7 @@ - + Simple WinMerge context menu -- 2.11.0