<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>emre şahin's digital garden 🍃 - document-analysis</title>
    <link>https://emresahin.net/tags/document-analysis/</link>
    <description>Posts in the document-analysis tag</description>
    <language>en</language>
    <managingEditor>contact@emresahin.net (Emre Şahin)</managingEditor>
    <lastBuildDate>Tue, 15 Sep 2026 19:46:32 +0000</lastBuildDate>
    <atom:link href="https://emresahin.net/tags/document-analysis/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>devlog</title>
      <published>2023-06-12T15:04:19+00:00</published>
      <updated>2023-06-12T15:04:19+00:00</updated>
      <author>Emre Şahin</author>
      <pubDate>Mon, 12 Jun 2023 15:04:19 +0000</pubDate>
      <link>https://emresahin.net/devlog/</link>
      <guid isPermaLink="true">https://emresahin.net/devlog/</guid>
      <description>I’ve read a few interesting ideas here . Identifying whether an uploaded document is a template could be a useful feature. This is a basic classification task. We can also find ways to extract named entities from the documents and remove them to create a template. Then, we can ask the user to pro...</description>
      <category>devlog</category>
      <category>Software Development</category>
      <category>legalops</category>
      <category>contract</category>
      <category>negotiation</category>
      <category>nlp</category>
      <category>document-analysis</category>
      <category>templates</category>
      <content:encoded><![CDATA[<ul>
<li>I’ve read a few interesting ideas <a href="http://sourcinginnovation.com/wordpress/2023/06/06/source-to-pay-is-extensive-p22-time-for-contract-management-but-its-a-nag-lets-start-with-negotiation/">here</a>.</li>
<li>Identifying whether an uploaded document is a template could be a useful feature.
<ul>
<li>This is a basic classification task. We can also find ways to extract named entities from the documents and remove them to create a template. Then, we can ask the user to provide values for these entities to generate a complete document.</li>
</ul>
</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Paper Review: Text Line Segmentation of Historical Documents: A Survey</title>
      <published>2012-07-27T14:00:00+00:00</published>
      <updated>2012-07-27T14:00:00+00:00</updated>
      <author>Emre Şahin</author>
      <pubDate>Fri, 27 Jul 2012 14:00:00 +0000</pubDate>
      <link>https://emresahin.net/text-line-segmentation-of-historical-documents/</link>
      <guid isPermaLink="true">https://emresahin.net/text-line-segmentation-of-historical-documents/</guid>
      <description>Authors: Laurance Likforman-Sulem, Abderrezak Sahour, Bruno Taconet URL: http://arxiv.org/pdf/0704.1267.pdf Keywords: page segmentation overlapping components image quality document complexity preprocessing projection based smearing based grouping based hough transform based repulsive attractive ...</description>
      <category>Paper Review</category>
      <category>text line segmentation</category>
      <category>historical documents</category>
      <category>Hough transform</category>
      <category>document analysis</category>
      <category>image processing</category>
      <content:encoded><![CDATA[<h1 id="authors-laurance-likforman-sulem-abderrezak-sahour-bruno-taconet">Authors: Laurance Likforman-Sulem, Abderrezak Sahour, Bruno Taconet</h1>
<h1 id="url-httparxivorgpdf07041267pdf">URL: <a href="http://arxiv.org/pdf/0704.1267.pdf">http://arxiv.org/pdf/0704.1267.pdf</a></h1>
<h1 id="keywords">Keywords:</h1>
<ul>
<li>page segmentation</li>
<li>overlapping components</li>
<li>image quality</li>
<li>document complexity</li>
<li>preprocessing</li>
<li>projection based</li>
<li>smearing based</li>
<li>grouping based</li>
<li>hough transform based</li>
<li>repulsive attractive</li>
<li>stochastic</li>
<li>touching components</li>
</ul>
<h1 id="q1-what-are-the-most-usable-techniques-for-ottoman-divans">Q1: What are the most usable techniques for Ottoman divans?</h1>
<p>Likforman-Sulem and Faure’s technique, which uses Gestalt criteria to associate text elements, might be of use. Feldbach and Tennies’ work, which was tested on Church Registers, may also be helpful. The Hough transform can be used. The Repulsive-Attractive method of Öztop et al. is also applicable. Stochastic methods by Tseng and Lee, which use a probabilistic Viterbi algorithm, can also be utilized.</p>
<h1 id="q2-how-are-touching-components-successfully-delimited">Q2: How are touching components successfully delimited?</h1>
<p>A touching component can be detected by its size. Subsequently, it should either be assigned to a lower or upper line, or be separated. Successful separation requires letter images or skeletons (which we lack).</p>
<h1 id="q3-how-is-the-hough-transform-used">Q3: How is the Hough transform used?</h1>
<p>Centroids of the connected components (CCs) are used as units of the Hough transform. Line hypotheses are developed in the Hough domain and verified in the image domain.</p>
<h1 id="q4-what-are-the-problems-specific-to-non-latin-texts">Q4: What are the problems specific to non-Latin texts?</h1>
<p>The baseline of Hebrew is at the upper part of the letters because of their box shape. Devanagari and similar scripts also have a headline on top of them. Diacritics and inter-letter shapes pose problems for Arabic.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
