<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for ThierryC2K8</title><link>http://disqus.com/by/ThierryC2K8/</link><description></description><atom:link href="http://disqus.com/ThierryC2K8/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 19 Mar 2009 10:42:35 -0000</lastBuildDate><item><title>Re: PDF-to-Word Conversion: Why It’s So Hard to Do</title><link>http://blog.nitropdf.com/2009/02/how-pdf-to-word/#comment-7346317</link><description>&lt;p&gt;Dear Richard,&lt;/p&gt;&lt;p&gt;Trying to convert technical datasheets with complex layouts (text, arrays, drawings, charts...) in order to copy and paste excerpts of them in other documents for my work, and not understanding why they were so "badly" converted, I suddenly understood why, thanks to your very interesting article.&lt;br&gt;In brief, we could compare the transition from a word processor-based document to a .PDF one with the compilation of source code to executable code.&lt;br&gt;Another question : could it be possible for a PDF-to-Word converter to use user-supplied hints to improve the conversion result, as seen in an OCR program ? For example I could select an area where there is a schematic and tag it as a drawing so that it would be interpreted as vector graphics and floating text boxes rather than main text.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ThierryC2K8</dc:creator><pubDate>Thu, 19 Mar 2009 10:42:35 -0000</pubDate></item></channel></rss>