<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: OpenOffice .doc format</title>
	<link>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/</link>
	<description>A Specialist Group of the British Computer Society</description>
	<pubDate>Thu, 28 Aug 2008 20:09:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: foreclosures</title>
		<link>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-2826</link>
		<dc:creator>foreclosures</dc:creator>
		<pubDate>Sun, 03 Aug 2008 15:35:44 +0000</pubDate>
		<guid>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-2826</guid>
		<description>&lt;strong&gt;foreclosures...&lt;/strong&gt;

Everybody\'s favorite middle class housing project turned luxury rental community had quite a few twists and turns this week. First, the Times exposed what some rent- stabilized tenants believe is a campaign of harassment by landlord Tishman Speyer. ...</description>
		<content:encoded><![CDATA[<p><strong>foreclosures&#8230;</strong></p>
<p>Everybody\&#8217;s favorite middle class housing project turned luxury rental community had quite a few twists and turns this week. First, the Times exposed what some rent- stabilized tenants believe is a campaign of harassment by landlord Tishman Speyer. &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mikendall</title>
		<link>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-70</link>
		<dc:creator>mikendall</dc:creator>
		<pubDate>Tue, 28 Jun 2005 10:16:00 +0000</pubDate>
		<guid>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-70</guid>
		<description>&lt;h5&gt;OpenOffice .doc format&lt;/h5&gt;
		  To second what has been said already this is my experience of posting the group's
minutes to the BCS HQ in ODT format. (Identities obscured to protect privacy.)

First email: 
        Send minutes in ODT format.

First reply: 
                Thanks Malcolm
        The attachment wouldn't open.  Was it done with some peculiar Open
        Source program?!

Second email:
                Hi XXXXXX,
        It was done with Open Office version 2.0 beta. What else would you expect?
        We are the Open Source Specialist Group after all.
        Do you want me to send you a  MS Office compatible version?
        Or pehaps you can download and instatll Open Office (much better option).
        Here is the URL:
               http://download.openoffice.org/2.0beta/index.html&lt;/a&gt; 

Second reply:
                Malcolm         
        I thought there was nothing on the reply until I have had another look
        and found it at the bottom.  We are not allowed to download programs
        without permission.  I will ask 'IT'.
        Thanks XXXXXX

FX waiting....
FX messages at BCS HQ
             "XXXXX,
              Please do not download open office. We have had issues with the
              software. Could I suggest that you use a neutral file format such as
              RTF., YYYYY"

Third reply:
        Malcolm
        I have had the response from our 'Technical Architect', IC Software.
        Please can you convert the minutes to RTF  and send again.
        I nearly downloaded Open Office at home but it said that a vulnerability
        had been discovered, so I didn't bother.
        Thanks. XXXXXX

FX converting document...
Third email.        
        Hi XXXXXX,
        Thanks for your efforts to get Open Office installed in the BCS. The reply
        from YYYYYYY is sadly typical. A measure of  OSSG success will be to  
        change this.
        Attached are the minutes in a neutral file format ; hopefully not a neutered
        format.Best Regards, Malcolm Kendall, Secretary BCS OSSG 
        
All this took 10 days and 8 emails to achieve.</description>
		<content:encoded><![CDATA[<h5>OpenOffice .doc format</h5>
<p>		  To second what has been said already this is my experience of posting the group&#8217;s<br />
minutes to the BCS HQ in ODT format. (Identities obscured to protect privacy.)</p>
<p>First email:<br />
        Send minutes in ODT format.</p>
<p>First reply:<br />
                Thanks Malcolm<br />
        The attachment wouldn&#8217;t open.  Was it done with some peculiar Open<br />
        Source program?!</p>
<p>Second email:<br />
                Hi XXXXXX,<br />
        It was done with Open Office version 2.0 beta. What else would you expect?<br />
        We are the Open Source Specialist Group after all.<br />
        Do you want me to send you a  MS Office compatible version?<br />
        Or pehaps you can download and instatll Open Office (much better option).<br />
        Here is the URL:<br />
               <a href="http://download.openoffice.org/2.0beta/index.html" rel="nofollow">http://download.openoffice.org/2.0beta/index.html</a> </p>
<p>Second reply:<br />
                Malcolm<br />
        I thought there was nothing on the reply until I have had another look<br />
        and found it at the bottom.  We are not allowed to download programs<br />
        without permission.  I will ask &#8216;IT&#8217;.<br />
        Thanks XXXXXX</p>
<p>FX waiting&#8230;.<br />
FX messages at BCS HQ<br />
             &#8220;XXXXX,<br />
              Please do not download open office. We have had issues with the<br />
              software. Could I suggest that you use a neutral file format such as<br />
              RTF., YYYYY&#8221;</p>
<p>Third reply:<br />
        Malcolm<br />
        I have had the response from our &#8216;Technical Architect&#8217;, IC Software.<br />
        Please can you convert the minutes to RTF  and send again.<br />
        I nearly downloaded Open Office at home but it said that a vulnerability<br />
        had been discovered, so I didn&#8217;t bother.<br />
        Thanks. XXXXXX</p>
<p>FX converting document&#8230;<br />
Third email.<br />
        Hi XXXXXX,<br />
        Thanks for your efforts to get Open Office installed in the BCS. The reply<br />
        from YYYYYYY is sadly typical. A measure of  OSSG success will be to<br />
        change this.<br />
        Attached are the minutes in a neutral file format ; hopefully not a neutered<br />
        format.Best Regards, Malcolm Kendall, Secretary BCS OSSG </p>
<p>All this took 10 days and 8 emails to achieve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mikendall</title>
		<link>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-71</link>
		<dc:creator>mikendall</dc:creator>
		<pubDate>Tue, 28 Jun 2005 10:16:00 +0000</pubDate>
		<guid>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-71</guid>
		<description>&lt;h5&gt;OpenOffice .doc format&lt;/h5&gt;
		  To second what has been said already this is my experience of posting the group's
minutes to the BCS HQ in ODT format. (Identities obscured to protect privacy.)

First email: 
        Send minutes in ODT format.

First reply: 
                Thanks Malcolm
        The attachment wouldn't open.  Was it done with some peculiar Open
        Source program?!

Second email:
                Hi XXXXXX,
        It was done with Open Office version 2.0 beta. What else would you expect?
        We are the Open Source Specialist Group after all.
        Do you want me to send you a  MS Office compatible version?
        Or pehaps you can download and instatll Open Office (much better option).
        Here is the URL:
               http://download.openoffice.org/2.0beta/index.html&lt;/a&gt; 

Second reply:
                Malcolm         
        I thought there was nothing on the reply until I have had another look
        and found it at the bottom.  We are not allowed to download programs
        without permission.  I will ask 'IT'.
        Thanks XXXXXX

FX waiting....
FX messages at BCS HQ
             "XXXXX,
              Please do not download open office. We have had issues with the
              software. Could I suggest that you use a neutral file format such as
              RTF., YYYYY"

Third reply:
        Malcolm
        I have had the response from our 'Technical Architect', IC Software.
        Please can you convert the minutes to RTF  and send again.
        I nearly downloaded Open Office at home but it said that a vulnerability
        had been discovered, so I didn't bother.
        Thanks. XXXXXX

FX converting document...
Third email.        
        Hi XXXXXX,
        Thanks for your efforts to get Open Office installed in the BCS. The reply
        from YYYYYYY is sadly typical. A measure of  OSSG success will be to  
        change this.
        Attached are the minutes in a neutral file format ; hopefully not a neutered
        format.Best Regards, Malcolm Kendall, Secretary BCS OSSG 
        
All this took 10 days and 8 emails to achieve.</description>
		<content:encoded><![CDATA[<h5>OpenOffice .doc format</h5>
<p>		  To second what has been said already this is my experience of posting the group&#8217;s<br />
minutes to the BCS HQ in ODT format. (Identities obscured to protect privacy.)</p>
<p>First email:<br />
        Send minutes in ODT format.</p>
<p>First reply:<br />
                Thanks Malcolm<br />
        The attachment wouldn&#8217;t open.  Was it done with some peculiar Open<br />
        Source program?!</p>
<p>Second email:<br />
                Hi XXXXXX,<br />
        It was done with Open Office version 2.0 beta. What else would you expect?<br />
        We are the Open Source Specialist Group after all.<br />
        Do you want me to send you a  MS Office compatible version?<br />
        Or pehaps you can download and instatll Open Office (much better option).<br />
        Here is the URL:<br />
               <a href="http://download.openoffice.org/2.0beta/index.html" rel="nofollow">http://download.openoffice.org/2.0beta/index.html</a> </p>
<p>Second reply:<br />
                Malcolm<br />
        I thought there was nothing on the reply until I have had another look<br />
        and found it at the bottom.  We are not allowed to download programs<br />
        without permission.  I will ask &#8216;IT&#8217;.<br />
        Thanks XXXXXX</p>
<p>FX waiting&#8230;.<br />
FX messages at BCS HQ<br />
             &#8220;XXXXX,<br />
              Please do not download open office. We have had issues with the<br />
              software. Could I suggest that you use a neutral file format such as<br />
              RTF., YYYYY&#8221;</p>
<p>Third reply:<br />
        Malcolm<br />
        I have had the response from our &#8216;Technical Architect&#8217;, IC Software.<br />
        Please can you convert the minutes to RTF  and send again.<br />
        I nearly downloaded Open Office at home but it said that a vulnerability<br />
        had been discovered, so I didn&#8217;t bother.<br />
        Thanks. XXXXXX</p>
<p>FX converting document&#8230;<br />
Third email.<br />
        Hi XXXXXX,<br />
        Thanks for your efforts to get Open Office installed in the BCS. The reply<br />
        from YYYYYYY is sadly typical. A measure of  OSSG success will be to<br />
        change this.<br />
        Attached are the minutes in a neutral file format ; hopefully not a neutered<br />
        format.Best Regards, Malcolm Kendall, Secretary BCS OSSG </p>
<p>All this took 10 days and 8 emails to achieve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ptansom</title>
		<link>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-69</link>
		<dc:creator>ptansom</dc:creator>
		<pubDate>Tue, 15 Mar 2005 02:17:00 +0000</pubDate>
		<guid>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-69</guid>
		<description>&lt;h5&gt;OpenOffice .doc format&lt;/h5&gt;
		  The problems with file formats are key to the lockin to proprietry systems. What you are using your application for can help in defining the best way of working for you.

For example, if you are using your Star/OpenOffice package on Windows then you can use a Word viewer (or Excel, etc.) to view the documents you are sent and print them.

If your primary reason for using the package is to produce printed or published information without the need to allow others to edit then using the native file formats is fine, along with the ability to save as PDF (which is a major bonus, and will become an even better proposition when Adobe Reader 7 is realeased - obviously not OSS software itelf unfortunately, but a big step forward in reading PDF documents on Linux).

The big problems come when you are exchanging documents with others for frequent editing. If you are in a closed environment for this (i.e. within a company) then you have the option to standardise on the new package. If you are exchanging with another company/organisation then things get difficult.

Exchanging regularly between Star/OpenOffice and MS Office for anything except fairly basic files is, unfortunately, not a good option (you are, after all, working with an import filter developed without access to Microsofts moving target of a file format specification).

You do, however, have the advantage that, if the organisation you are working with is flexible, that they may themselves be interested in using Star/OpenOffice given that the latter is available without cost. This doesn't always go down well though as in my experience many end users are very reluctant to use anything other than MS Office and would rather use 'borrowed' copies than change.

Hmm, started this post this morning. I've been to the meeting since then and it is now late, but it looks finished so I'll post and be damned! (Will that be content filtered?!)</description>
		<content:encoded><![CDATA[<h5>OpenOffice .doc format</h5>
<p>		  The problems with file formats are key to the lockin to proprietry systems. What you are using your application for can help in defining the best way of working for you.</p>
<p>For example, if you are using your Star/OpenOffice package on Windows then you can use a Word viewer (or Excel, etc.) to view the documents you are sent and print them.</p>
<p>If your primary reason for using the package is to produce printed or published information without the need to allow others to edit then using the native file formats is fine, along with the ability to save as PDF (which is a major bonus, and will become an even better proposition when Adobe Reader 7 is realeased - obviously not OSS software itelf unfortunately, but a big step forward in reading PDF documents on Linux).</p>
<p>The big problems come when you are exchanging documents with others for frequent editing. If you are in a closed environment for this (i.e. within a company) then you have the option to standardise on the new package. If you are exchanging with another company/organisation then things get difficult.</p>
<p>Exchanging regularly between Star/OpenOffice and MS Office for anything except fairly basic files is, unfortunately, not a good option (you are, after all, working with an import filter developed without access to Microsofts moving target of a file format specification).</p>
<p>You do, however, have the advantage that, if the organisation you are working with is flexible, that they may themselves be interested in using Star/OpenOffice given that the latter is available without cost. This doesn&#8217;t always go down well though as in my experience many end users are very reluctant to use anything other than MS Office and would rather use &#8216;borrowed&#8217; copies than change.</p>
<p>Hmm, started this post this morning. I&#8217;ve been to the meeting since then and it is now late, but it looks finished so I&#8217;ll post and be damned! (Will that be content filtered?!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous User</title>
		<link>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-68</link>
		<dc:creator>Anonymous User</dc:creator>
		<pubDate>Sun, 06 Mar 2005 09:50:00 +0000</pubDate>
		<guid>http://ossg.bcs.org/2005/02/28/openoffice-doc-format/#comment-68</guid>
		<description>&lt;h5&gt;OpenOffice .doc format&lt;/h5&gt;
		  </description>
		<content:encoded><![CDATA[<h5>OpenOffice .doc format</h5>
]]></content:encoded>
	</item>
</channel>
</rss>
