<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Fighting Lock-in &#8211; A Report From the Trenches</title>
	<atom:link href="http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/feed/" rel="self" type="application/rss+xml" />
	<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/</link>
	<description>One man. Closing, all the windows.</description>
	<lastBuildDate>Thu, 23 May 2013 20:47:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: oiaohm</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92537</link>
		<dc:creator>oiaohm</dc:creator>
		<pubDate>Sat, 28 Jul 2012 02:13:07 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92537</guid>
		<description><![CDATA[Phenom you are close.  If a file format has compatibility or will be trouble.   The devil is in the details.

Like a RTF document can have word and excel document binary format embedded as a OLE.  So that so call generic RTF now needs word and excel to be viewed.

No Microsoft created format for Office usage passes a details check.

People avoid the details so are not aware how many compatibility problems they really have.]]></description>
		<content:encoded><![CDATA[<p>Phenom you are close.  If a file format has compatibility or will be trouble.   The devil is in the details.</p>
<p>Like a RTF document can have word and excel document binary format embedded as a OLE.  So that so call generic RTF now needs word and excel to be viewed.</p>
<p>No Microsoft created format for Office usage passes a details check.</p>
<p>People avoid the details so are not aware how many compatibility problems they really have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phenom</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92440</link>
		<dc:creator>Phenom</dc:creator>
		<pubDate>Thu, 26 Jul 2012 07:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92440</guid>
		<description><![CDATA[RTF is eBil!  It is developed by the Devilest of Devils, M$!]]></description>
		<content:encoded><![CDATA[<p>RTF is eBil!  It is developed by the Devilest of Devils, M$!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iLia</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92419</link>
		<dc:creator>iLia</dc:creator>
		<pubDate>Wed, 25 Jul 2012 17:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92419</guid>
		<description><![CDATA[&lt;b&gt;Now I use RTF files only. They work everywhere, even Linux!&lt;/b&gt;

Don&#039;t be so happy, I have some problems with RTF in LibreOffice on Linux, the problem is that this file wasn&#039;t something very complex, but LibreOffice couldn&#039;t open it correctly.]]></description>
		<content:encoded><![CDATA[<p><b>Now I use RTF files only. They work everywhere, even Linux!</b></p>
<p>Don&#8217;t be so happy, I have some problems with RTF in LibreOffice on Linux, the problem is that this file wasn&#8217;t something very complex, but LibreOffice couldn&#8217;t open it correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oiaohm</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92321</link>
		<dc:creator>oiaohm</dc:creator>
		<pubDate>Mon, 23 Jul 2012 04:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92321</guid>
		<description><![CDATA[Clarence Moon  MS Works contained version of Word contians OLE parts not in any other.

Word used in MS Office enterprise can also include OLE links that someone using MS Office Standard cannot open.  Heck MS Office Starter contained less OLE parts than MS Office Standard.

Clarence Moon its the embed OLE data that is the problem.  It does not matter what link I use to document its presence.

I could point to MS documentation on RTF the section covering embedding of OLE object but that has to be downloaded to be viewed.

Just because a file ends in .doc or .docx does not mean the version of Word you have on your computer is able to open it.  You have MS Office Standard and someone made it with MS Office Enterprise using one of the Enterprise extras you may not be able to open the file even that the file is from the same version of Word.

OLE problems only get worse when you start crossing versions of MS Office. Clarence Moon.

All this is written up at national achieves documentation on selection of long term storage formats.

&quot;That’s what you get for using non-Microsoft software&quot;

The reality how would you know.  You just inserted a Image and the wrong OLE was used.  It will still display perfect on your machine Clarence Moon.  This is why .doc and .docx is such a bastard for sending documents around.

This is the reality of the problem.  Microsoft file format design is a land mine.  Just because you have walked across the mine field safely for now does not mean you always will Clarence Moon.

Yes the OLE objects ruin your day with all of the MS Office documents.

Most users of MS Office don&#039;t want to become aware that its broken.]]></description>
		<content:encoded><![CDATA[<p>Clarence Moon  MS Works contained version of Word contians OLE parts not in any other.</p>
<p>Word used in MS Office enterprise can also include OLE links that someone using MS Office Standard cannot open.  Heck MS Office Starter contained less OLE parts than MS Office Standard.</p>
<p>Clarence Moon its the embed OLE data that is the problem.  It does not matter what link I use to document its presence.</p>
<p>I could point to MS documentation on RTF the section covering embedding of OLE object but that has to be downloaded to be viewed.</p>
<p>Just because a file ends in .doc or .docx does not mean the version of Word you have on your computer is able to open it.  You have MS Office Standard and someone made it with MS Office Enterprise using one of the Enterprise extras you may not be able to open the file even that the file is from the same version of Word.</p>
<p>OLE problems only get worse when you start crossing versions of MS Office. Clarence Moon.</p>
<p>All this is written up at national achieves documentation on selection of long term storage formats.</p>
<p>&#8220;That’s what you get for using non-Microsoft software&#8221;</p>
<p>The reality how would you know.  You just inserted a Image and the wrong OLE was used.  It will still display perfect on your machine Clarence Moon.  This is why .doc and .docx is such a bastard for sending documents around.</p>
<p>This is the reality of the problem.  Microsoft file format design is a land mine.  Just because you have walked across the mine field safely for now does not mean you always will Clarence Moon.</p>
<p>Yes the OLE objects ruin your day with all of the MS Office documents.</p>
<p>Most users of MS Office don&#8217;t want to become aware that its broken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clarence Moon</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92305</link>
		<dc:creator>Clarence Moon</dc:creator>
		<pubDate>Sun, 22 Jul 2012 19:50:48 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92305</guid>
		<description><![CDATA[&lt;b&gt;that 1 document you really want is missing some odd ball OLE object &lt;/b&gt;

That&#039;s what you get for using non-Microsoft software, Mr. O.  You found some obscure program where some wannabe developer hacked into the MS Word formats using some unsupported interface and then you couldn&#039;t recover some data with a subsequent version.  I hope you understand how stupid that makes you look.  I doubt if you do, though.]]></description>
		<content:encoded><![CDATA[<p><b>that 1 document you really want is missing some odd ball OLE object </b></p>
<p>That&#8217;s what you get for using non-Microsoft software, Mr. O.  You found some obscure program where some wannabe developer hacked into the MS Word formats using some unsupported interface and then you couldn&#8217;t recover some data with a subsequent version.  I hope you understand how stupid that makes you look.  I doubt if you do, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oiaohm</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92297</link>
		<dc:creator>oiaohm</dc:creator>
		<pubDate>Sun, 22 Jul 2012 15:05:48 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92297</guid>
		<description><![CDATA[Tar
&quot;I tried to open an old Star office 5 file from 2002-2003 and guess what? Formatting is all wrong.&quot;
I have staroffice documents in my archive back to 1995 in fact Tar I have no problem handling them.

Clarence Moon
third party extension to OLE MS Office allows OLE objects to be embedded without a reference image or any exact size details.

The way MS Office interacts with &quot;non-Microsoft products&quot; causes problems.  .doc files from MS Works version of Word also fail in MS Office 2010 due to MS Works version of word having unique OLE addons.

So broad cross section of documents from every version of MS Word things start coming apart quite quickly just sticking to MS product.  Gets worse once you have third party extensions in OLE.

Basically a .doc file allows storage of a mix of data some made by Microsoft only for particular versions of Office or Works due to differences in OLE objects included.  Ie someone insert a visio object into a .doc file it don&#039;t display right unless you have visio installed.  Some data only for third part OLE objects.  Nice if you are the poor sod on the other end of the email who get that.  This is why a lot of businesses these days only send pdf.  So you don&#039;t send a document and not have it not open on the other end.

Sorry Tar RTF is not magic cure all. 
http://www.aspose.com/community/forums/permalink/302986/302986/showthread.aspx

Welcome to land mine.  MS has land mined all there word processing formats the same exact way.  Lets allow OLE objects to be embed without having a picture if computer does not have that OLE object.  Tar.

Never allow generic storage of what ever in a file-format and expect to be able to render it in future.

So a RTF file from 2002-2003 might not even open at all Tar due to the fact your computer does not contain the OLE object that lot of the data was contained in.

Tar Staroffice document from 2002-2003 you will get open might have to change a few formatting options to make it look right.

Basically I have old RTF documents with OLE objects in them one case I was forced to reinstall windows 3.11 so I could view some of them.  The OLE object would not install and work in 9x or anything NT based.

RTF with embed OLE are also not assured to work on Linux.  OLE embed in ODF there s a image of what should be at that page location if the OLE cannot be found.  Not true for old MS Office formats or new OOXML format or RTF.

ODF is design to work if items like OLE objects are missing by using a reference image instead.  It has something to swap it with.

Tar basically what level of broken do you want.  ODF style where formating could be bust but fixable yet your data readable.  Or MS style where formatting might be OK but your data is nowhere to be seen because you don&#039;t have anything to display it.

Tar you could have got lucky and picked a old StarOffice 5 document from 2002-2003 that renders perfectly not all of those documents render incorrectly.  In fact most render correctly.

Tar really if you want perfect formatting in future you should produce a pdf/A that works but basically not editable.  ODF means the information will be there to edit no matter what.  Yes the PDF/A the /A is archive and it a stable long term format.

Clarence Moon when I learnt about the OLE issue is with a drawing program called warbirds.  That program was never provided on the Internet the company that made it is no more.  Sorry the OLE bug is what drives anyone running document archives nuts.

Its like 10000 documents open no problem but that 1 document you really want is missing some odd ball OLE object and is missing the key bit of information you want and you hope someone made a pdf or images of it so you can find out what it had.

Also please visit your countries national archive sites and read the documentation on long term electronic documentation storage particular what are the allowed formats.  Clarence Moon yes there is formal certificate in most countries to say you know how to archive documents.  Claiming I know this by google shows you don&#039;t know the topic Clarence Moon.

I am a trained to maintain archives.  The approved formats are highly limited for documents.  png, pdf/a, odf, jpg(special cases) that is all.  rtf, doc, docx are not approved for long term storage due to known bugs in design.

Clarence Moon as normal claims my knowledge is a google search if it so simple why in hell did you not know that rtf .doc and .docx is not approved to be used by national achieves.  Basically you are trying to hide your incompetence by saying my information comes from google searches.

Google only helps you if you know exactly what you are searching for.  OLE error in MS Office produced files I know about.]]></description>
		<content:encoded><![CDATA[<p>Tar<br />
&#8220;I tried to open an old Star office 5 file from 2002-2003 and guess what? Formatting is all wrong.&#8221;<br />
I have staroffice documents in my archive back to 1995 in fact Tar I have no problem handling them.</p>
<p>Clarence Moon<br />
third party extension to OLE MS Office allows OLE objects to be embedded without a reference image or any exact size details.</p>
<p>The way MS Office interacts with &#8220;non-Microsoft products&#8221; causes problems.  .doc files from MS Works version of Word also fail in MS Office 2010 due to MS Works version of word having unique OLE addons.</p>
<p>So broad cross section of documents from every version of MS Word things start coming apart quite quickly just sticking to MS product.  Gets worse once you have third party extensions in OLE.</p>
<p>Basically a .doc file allows storage of a mix of data some made by Microsoft only for particular versions of Office or Works due to differences in OLE objects included.  Ie someone insert a visio object into a .doc file it don&#8217;t display right unless you have visio installed.  Some data only for third part OLE objects.  Nice if you are the poor sod on the other end of the email who get that.  This is why a lot of businesses these days only send pdf.  So you don&#8217;t send a document and not have it not open on the other end.</p>
<p>Sorry Tar RTF is not magic cure all.<br />
<a href="http://www.aspose.com/community/forums/permalink/302986/302986/showthread.aspx" rel="nofollow">http://www.aspose.com/community/forums/permalink/302986/302986/showthread.aspx</a></p>
<p>Welcome to land mine.  MS has land mined all there word processing formats the same exact way.  Lets allow OLE objects to be embed without having a picture if computer does not have that OLE object.  Tar.</p>
<p>Never allow generic storage of what ever in a file-format and expect to be able to render it in future.</p>
<p>So a RTF file from 2002-2003 might not even open at all Tar due to the fact your computer does not contain the OLE object that lot of the data was contained in.</p>
<p>Tar Staroffice document from 2002-2003 you will get open might have to change a few formatting options to make it look right.</p>
<p>Basically I have old RTF documents with OLE objects in them one case I was forced to reinstall windows 3.11 so I could view some of them.  The OLE object would not install and work in 9x or anything NT based.</p>
<p>RTF with embed OLE are also not assured to work on Linux.  OLE embed in ODF there s a image of what should be at that page location if the OLE cannot be found.  Not true for old MS Office formats or new OOXML format or RTF.</p>
<p>ODF is design to work if items like OLE objects are missing by using a reference image instead.  It has something to swap it with.</p>
<p>Tar basically what level of broken do you want.  ODF style where formating could be bust but fixable yet your data readable.  Or MS style where formatting might be OK but your data is nowhere to be seen because you don&#8217;t have anything to display it.</p>
<p>Tar you could have got lucky and picked a old StarOffice 5 document from 2002-2003 that renders perfectly not all of those documents render incorrectly.  In fact most render correctly.</p>
<p>Tar really if you want perfect formatting in future you should produce a pdf/A that works but basically not editable.  ODF means the information will be there to edit no matter what.  Yes the PDF/A the /A is archive and it a stable long term format.</p>
<p>Clarence Moon when I learnt about the OLE issue is with a drawing program called warbirds.  That program was never provided on the Internet the company that made it is no more.  Sorry the OLE bug is what drives anyone running document archives nuts.</p>
<p>Its like 10000 documents open no problem but that 1 document you really want is missing some odd ball OLE object and is missing the key bit of information you want and you hope someone made a pdf or images of it so you can find out what it had.</p>
<p>Also please visit your countries national archive sites and read the documentation on long term electronic documentation storage particular what are the allowed formats.  Clarence Moon yes there is formal certificate in most countries to say you know how to archive documents.  Claiming I know this by google shows you don&#8217;t know the topic Clarence Moon.</p>
<p>I am a trained to maintain archives.  The approved formats are highly limited for documents.  png, pdf/a, odf, jpg(special cases) that is all.  rtf, doc, docx are not approved for long term storage due to known bugs in design.</p>
<p>Clarence Moon as normal claims my knowledge is a google search if it so simple why in hell did you not know that rtf .doc and .docx is not approved to be used by national achieves.  Basically you are trying to hide your incompetence by saying my information comes from google searches.</p>
<p>Google only helps you if you know exactly what you are searching for.  OLE error in MS Office produced files I know about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tar</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92286</link>
		<dc:creator>Tar</dc:creator>
		<pubDate>Sun, 22 Jul 2012 13:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92286</guid>
		<description><![CDATA[I tried to open an old Star office 5 file from 2002-2003 and guess what? Formatting is all wrong.

Now I use RTF files only. They work everywhere, even Linux!]]></description>
		<content:encoded><![CDATA[<p>I tried to open an old Star office 5 file from 2002-2003 and guess what? Formatting is all wrong.</p>
<p>Now I use RTF files only. They work everywhere, even Linux!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clarence Moon</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92278</link>
		<dc:creator>Clarence Moon</dc:creator>
		<pubDate>Sun, 22 Jul 2012 12:31:11 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92278</guid>
		<description><![CDATA[&lt;b&gt;Newer version of MS Office does not always open older document correctly &lt;/b&gt;

I am sure that your Googling found some case where that is true, Mr. O, but your waffling on why and the oblique reference to &quot;third part&quot;  (is that your clumsy way of saying &quot;3rd party&quot;?) seems to mean that some non-Microsoft product actually has the problem that you claim to exist.  What are the details?  I am sure that the incidence of whatever it is is so slight as to make no difference to anyone.

Explain it if you can.]]></description>
		<content:encoded><![CDATA[<p><b>Newer version of MS Office does not always open older document correctly </b></p>
<p>I am sure that your Googling found some case where that is true, Mr. O, but your waffling on why and the oblique reference to &#8220;third part&#8221;  (is that your clumsy way of saying &#8220;3rd party&#8221;?) seems to mean that some non-Microsoft product actually has the problem that you claim to exist.  What are the details?  I am sure that the incidence of whatever it is is so slight as to make no difference to anyone.</p>
<p>Explain it if you can.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kozmcrae</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92253</link>
		<dc:creator>kozmcrae</dc:creator>
		<pubDate>Sun, 22 Jul 2012 01:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92253</guid>
		<description><![CDATA[Tar wrote:

&quot;So many Foss tools break compatibility all the time.&quot;

So Tar points to someone else and says &quot;They do it&quot; and by his twisted logic that makes it okay for Microsoft to break compatibility throughout the life of their Office suite.

You are no better than any other Microsoft attack dog.  For your information Tar, it&#039;s not okay if someone else does it.  What some one else does is their business.  Microsoft breaks compatibility throughout the life of their office suite to encourage their customers to keep up on the treadmill.  It&#039;s a fools game and you are here to defend it.  That makes you a fool.]]></description>
		<content:encoded><![CDATA[<p>Tar wrote:</p>
<p>&#8220;So many Foss tools break compatibility all the time.&#8221;</p>
<p>So Tar points to someone else and says &#8220;They do it&#8221; and by his twisted logic that makes it okay for Microsoft to break compatibility throughout the life of their Office suite.</p>
<p>You are no better than any other Microsoft attack dog.  For your information Tar, it&#8217;s not okay if someone else does it.  What some one else does is their business.  Microsoft breaks compatibility throughout the life of their office suite to encourage their customers to keep up on the treadmill.  It&#8217;s a fools game and you are here to defend it.  That makes you a fool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Pogson</title>
		<link>http://mrpogson.com/2012/07/21/fighting-lock-in-a-report-from-the-trenches/#comment-92252</link>
		<dc:creator>Robert Pogson</dc:creator>
		<pubDate>Sun, 22 Jul 2012 00:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://mrpogson.com/?p=13319#comment-92252</guid>
		<description><![CDATA[Tar wrote, &lt;em&gt;&lt;font color=&quot;green&quot;&gt;&quot;there’s no way even to run star office binaries on modern Linux&quot;&lt;/font&gt;&lt;/em&gt;.

Besides the obvious question of why one would want to run an ancient release there&#039;s the obvious solution of running an ancient release of GNU/Linux. Why would there be a need to run it on a modern release? That&#039;s a straw man, a very weak argument. LibreOffice can still open StarWriter 3-5 files and all versions of OpenOffice.org]]></description>
		<content:encoded><![CDATA[<p>Tar wrote, <em><font color="green">&#8220;there’s no way even to run star office binaries on modern Linux&#8221;</font></em>.</p>
<p>Besides the obvious question of why one would want to run an ancient release there&#8217;s the obvious solution of running an ancient release of GNU/Linux. Why would there be a need to run it on a modern release? That&#8217;s a straw man, a very weak argument. LibreOffice can still open StarWriter 3-5 files and all versions of OpenOffice.org</p>
]]></content:encoded>
	</item>
</channel>
</rss>
