I'm pleased to announce that the "change tracking text editor" finally reached a 1Finally, theI've managed to implement the ____capabilityget athehtx.gui.change_tracking_text_editor.working reliably enough for beta testing.e and prepared a downloadable package: <a href="http://publishinhypertext-systems.org/downloads.php">hypertext-systems.org/downloads.php</a>. A description of the tool/capability can be found in t<a href="https://www.bitchute.com/vicdeo/UQGtn2JYrIjY/">this video</a>.Java 1.6 or higher is required. From here, plenty of very interesting options to extend it present themsvelves, but I find more important to point out that in my opinion, tracking/recording the development of a text is fundamental for a hypertext system and serious writing on a computer. witWithout it, versioning an dd revision can only be done retrospectively with heuristical diffs, which can be wrong and are incomplete in terms of incorrectwronglack information like the order of changes or changes that later got overwritten again, as after-the-fact analysis as after-the-fact analysiss.-
<p style="text-align:justify;">
</p><p style="text-align:justify;"></p>With the the text's history recorded, the individual characters alss the most atomic element becomes addressable with a higher resolution everythan with indifferent diff blocks, . can be addressed , agnostic/patchFor a hypertext system, one has to ask where the texts <</p>
<p style="text-align:justify;">it's supposed to manage come from. If they're from old source s and have only survicved in specific versions without their , they're usually only available in history of their writing recorded, compiled, merged, consolidatedrecords of may be available, but new texts I write myself today should not follow the old constraints for , I don't want to immitate the old constraitnts of physical production.imposed by , but make full use of the potential of digital. and instead With writing covered for now, I can continue with tools for /capability for text/media/ management, publishing and reading, (although very primitive) initiallyiesresourceto eventually arrive at an integrated system for more convenience than using the capabilities individually.
<p style="text-align:justify;">This text was written with the change_trackSee the This text is licensed under the <a href="https://www.gnu.org/licenses/agpl-3.0.html">GNU Affero General Public License 3 + any later version</a> and/or under the <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">Creative Commons Attribution-ShareAlike 4.0 International</a>. See the <a href="https://skreutzer.de/htx/change_tracking_text_editor_1_announcement_20181104.xml">history </a> of how this text edeveloped.</p>
<p style="text-align:justify;"></p>During the development Theoretical works I've consulted while working on the editor are <a href="Books I've read:https://skreutzer.de/2018/06/23/track-changes-book-by-matthew-kirschenbaum/">"Track Changes" by Matthew Kirschenbaum and Related b<a href="https://lccn.loc.gov/2012042986">"The Work of Revision" by Hannah Sullivan</a>.</p>
<p style="text-align:justify;">TheBesides the <a href="http://hypertext-systems.org/journal/</a>">prototype for a hyperglossary capability</a> (y<a href="https://bitchute.com/video/Nu2Cv9fc8cvT/">video</a>)www.of and <a href="https://www.bitchute.com/video/agkvwxYtL6YD/">WordPress post retriever</Aa> (with subsequent <a href="https://biwww.bitchute.com/video/5hOPSTRLs7S4/">conversion to different target formats</a>), the "Change Tracking Text Editor" is the only other contribution I was able to prepare for the 50th anniversary of Douglas Engelbarts 's great demo while loosely participating in the <a href="https://doug-50.info">Doug@50</aA < > effort during the year 2018.</p>GD<a href="https://www.youtube.com/watch?v=M5PgQS3ZBWA&list=PLCGFadV4FqU3flMPLg36d8RFQW65bWsnP"></a>ade_skreutzer_20181104T160224Z_personal_hypertext_report_9