Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 09/09/2011, mlevison <mark@mlevison.com> wrote:
...
Is this is a common problem. I'm at the point of just asking my client to
pay for MS office licenses because it will be cheaper than the time I'm
spending on this.

Classic cost benefit analysis. In this case the business opportunity
is to either receive payment from your customer for you to perform the
conversion (either automated batch process or manually) or to
recommend that m$o licence is used to access legacy documents, whilst
using LO to create odf documents in future.

Assuming m$ licences are valid in perpetuity, it is surprising that
business do not make a strategic decision to use m$ for legacy
documents and LO for future odf documents. As an hypothetical analogy,
it is legal to use a computer with m$windoze98 in perpetuity,
regardless of whether m$ support it; so such a computer could be used
to access a legacy m$ document, whilst using another computer with
gnu/linux distribution installed to create LO odf documents.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.