You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _includes/comparisonMethods.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Comparison Method
1
+
# [Comparison Method](#comparison_method)
2
2
3
3
It is possible to choose which method to use to compare two folders.
4
4
The method to use is strictly related to user needs, comparing source code (files large only few kilobytes) should use a content comparison but to find which movies (files larger than a gigabytes) are not present on right side is faster compare by file size or file timestamp.
@@ -44,4 +44,4 @@ The complete list of supported comparison methods
Copy file name to clipboardExpand all lines: _includes/finderMetadata.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Compare Finder Metadata
1
+
# [Compare Finder Metadata](#compare_finder_metadata)
2
2
3
3
It is possible to compare OSX Finder Metadata.
4
4
When the metadata comparison mismatches, for example left file's label is red and right file's label is blue, the other comparison methods (size, timestamp, content) are not evaluated.
@@ -24,4 +24,4 @@ The complete list of supported metadata
Before being compared two files they must be aligned, the alignment rule can be configured
12
12
13
-
# Align by Name Case Sensitivity
13
+
# [Align by Name Case Sensitivity](#align_by_name_case_sensitivity)
14
14
15
15
The default alignment method compares file name strings, if they are match case then they will be aligned.
16
16
Suppose you have the scenario shown below
@@ -65,7 +65,7 @@ This can be achieved selecting 'Ignore File Name Case' from popup menu.</p>
65
65
</table>
66
66
</div>
67
67
68
-
# Align by HFS+ Filesystem Case
68
+
# [Align by HFS+ Filesystem Case](#align_by_hfs_filesystem_case)
69
69
70
70
Normally the <acronymtitle="Hierarchical File System">HFS+</acronym> disks are formatted ignoring the file name case, so if we have winter.jpg and WINTER.JPG they cannot be created on same directory (because they have the same name).
71
71
@@ -79,7 +79,7 @@ It is possible to let VisualDiffer determine the file name alignment case algori
79
79
80
80
If the last scenario is true, the alignment will try to be smart, first it searches if a match case is available (winter.jpg with winter.jpg) then it tries to align with the most similar name.
81
81
82
-
# Align by User Defined Rules (required OSX Lion or above)
82
+
# [Align by User Defined Rules (required OSX Lion or above)](#align_by_user_defined_rules_required_osx_lion_or_above)
83
83
84
84
There are scenarios where it is necessary to align files having different names.
85
85
The most simple scenario has files with same name but different extension as shown below
@@ -138,15 +138,15 @@ Suppose you want to align ignoring the file extension to produce the result show
138
138
139
139
This can be achieved using VisualDiffer 'user defined alignment rules'.
The left regexp is used to match a filename on the left side of VisualDiffer Folder View, we want to find all jpg files so we create a group `(.*)` followed by `.jpg` extension.
Notice the right expression **isn't** a regular expression, it should contain some special patterns used to access to regular expression groups (if any).
169
169
@@ -201,6 +201,6 @@ But `002.jpg` and `002.RAW` files are not aligned because `002.RAW` extension is
It is possible to verify immediately if the expressions work as expected using the 'Test Rule', just type a file name and the 'Result' field will be filled accordingly.
206
+
It is possible to verify immediately if the expressions work as expected using the 'Test Rule', just type a file name and the 'Result' field will be filled accordingly.
0 commit comments