From owner-freebsd-chat Wed Apr 3 15:59:14 2002 Delivered-To: freebsd-chat@freebsd.org Received: from pilchuck.reedmedia.net (pilchuck.reedmedia.net [209.166.74.74]) by hub.freebsd.org (Postfix) with ESMTP id B1B4737B419 for ; Wed, 3 Apr 2002 15:59:10 -0800 (PST) Received: from reed by pilchuck.reedmedia.net with local-esmtp (Exim 3.12 #1 (Debian)) id 16suei-0004SO-00; Wed, 03 Apr 2002 15:59:08 -0800 Date: Wed, 3 Apr 2002 15:59:08 -0800 (PST) From: "Jeremy C. Reed" To: chat@freebsd.org Subject: Re: Anti-Unix Site Runs Unix In-Reply-To: <00b201c1db61$825e66e0$0a00000a@atkielski.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 4 Apr 2002, Anthony Atkielski wrote: > I have to be able to read the proprietary data formats; that is not an > option. "Almost" isn't enough. This is a good example of getting trapped. (Do software companies create new proprietary formats for new versions to make them incompatible with competitors?) I don't know what data you are referring to, but for generic tasks like word processing or spreadsheets, there are open alternatives. (Even Microsoft authored a widely-used, open specification for "encoding formatted text and graphics for easy transfer between applications.") Often, you can ask for alternative formats. (It may be an inconvenience at first, but in the long run it will all work out.) And depending on your standing, you could insist on not using the proprietary formats. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message