<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Improved Algorithms for Approximate String Matching (Extended Abstract) · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/0807.4368/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/0807.4368/feed.xml" rel="self" type="application/rss+xml" /><item><title>Improved Algorithms for Approximate String Matching (Extended Abstract) — mentioned by jbapple</title><link>https://news.ycombinator.com/item?id=9703701</link><guid isPermaLink="false">urn:hackerpapers:mention:0807.4368:9703701</guid><pubDate>Fri, 12 Jun 2015 02:34:33 GMT</pubDate><description>&lt;p&gt;&amp;gt; two almost-equal files. In that case the average running time should be way lower, no? Yes, indeed! What you&amp;#x27;re thinking of is &amp;quot;output-sensitive&amp;quot; algorithms. There are some output-sensitive algorithms for edit distance. The fastest one I found is in &amp;quot;Improved Algorithms for Approximate String Matching&amp;quot; by Dimitris and Georgios Papamichail. They note: &amp;quot;We designed an output sensitive algorithm solving the edit distance problem between two strings of lengths n and m respectively in time O((s-|n-m|)min(m,n,s)+m+n) and linear space, where s is the edit distance between the two strings.&amp;quot;…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/0807.4368/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DS</category></item></channel></rss>
