Diskussion:Diff

message: noch zu übersetztender Text für den Bereich Geschichte:
In the context of Unix, the use of the ed line editor provided diff with the natural ability to create machine-usable "edit scripts".  These edit scripts when saved to a file can, along with the original file, be reconsitituted by ed into the modified file in its entirety.  This greatly reduced the space necessary to maintain multiple versions of a file.  McIlroy considered writing a post-processor for diff where a variety of output formats could be designed and implemented, but he found it more frugal and simpler to have diff generate directly the syntax and reverse-order input accepted by the ed command.
Most all diff implementations remain outwardly unchanged since 1975 with but improvements to the core algorithm, the addition of useful features to the command, and the design of new output formats.  Postprocessors sdiff and diffmk rendered side-by-side diff listings and applied change marks to printed documents, respectively, and were developed elsewhere in Bell Labs in or before 1981.  The Berkeley distribution of Unix made a point of adding the context format (-C) and recursion on filesystem directory structures (-r).  The GNU Project's diff application includes the unified context format and is combined in a package with other diff and patch related utilities.
In diff's early years, common uses included comparing changes in computer language source code, the source to technical documents, verifying program debugging output, comparing filesystem listings and computer assembly code.  The output targeted for ed was purposely added to allow compression of a sequence of modifications to a file.  Emerging in the late 1970s, the Source Code Control System (SCCS) was a direct consequence of this development.  The context format of diff introduced at Berkeley helped in distributing patches that would be applied to code that possibly may have been modified.  Paul Jensen, faced with consolidating changes from two branches of a program's source code tree proposed diff3, which persists for most as a curiosity, but is still useful to those finding themselves in Jensen's situation.
A conceptual predecessor of diff includes Project Xanadu, a hypertext project established in 1960 that had envisioned a version tracking system necessary for its "transpointing windows" feature.  As part of this feature, file differences were subsumed in the expansive term "transclusion", when a document has included in it parts of other documents or revisions.
In the digital realm of the humanities, computer comparison systems were understood to have been created for working on literary works published in large volumes.
:Die erste SCCS Version stammt von 1972 von Rochkind. SCCS Basiert auf den Ergebnissen von diff. Wenn die Geschichte korrekt dargestellt wird, dann müßte das irgendwie zu dem Rest der Angaben im Artikel passen... Schily 20:08, 9. Mär. 2010 (CET)

message: Der Link im dritten Literaturnachweis ist tot.
:is raus greetz vanGore 01:22, 3. Mär 2006 (CET)
thread_title:  Toter Link im Literaturnachweis erl. 

message: Es gibt doch einen Diff-Algorithmus, der zunächst die zwei(?) Dateien vergleicht, dann die größten Übereinstimmungen sucht und schließlich darauf beasierend die Änderungen zeigt/vergleicht. Wenn ich das richtig im Kopf habe, ist das die Funktionsweise eines Dreiwege-Diff.
Infos zu diesem Ding fehlen völlig. (nicht signierter Beitrag von 88.130.85.134 (Diskussion) 01:18, 23. Mai 2010 (CEST)
thread_title:  Dreiwege-Diff 

message: --2001:16B8:E9E9:8400:2478:420B:9FD3:8F5 19:46, 3. Mär. 2022 (CET)
thread_title:  Wie bitte kann man PDF-Dateien vergleichen?