>On Saturday 14 May 2005 20:41, Gregory Pittman wrote: > > Craig Bradney wrote:
[snip] > >> What I think it comes down to is the issue of >> intentionally/unintentionally setting up barriers to the use of >> (and happiness with) Scribus. A backup plan can always be to at >> least have a parsable format so that some utility can help with >> problems, and maybe even yield unanticipated benefits. >> > >Oh, we certainly do recognize this. No intentional barriers are >intended. Just the going from 1.3+ backsaving to < 1.2.x is not a >high priority IMNSHO. > >Peter May I suggest we inherit these concerns from the proprietary software world? Since upgrading to the next version of Scribus doesn't imply any money (but a little time, yes!), it is reasonable to assume there is no real barrier to upgrading? Then why simply not upgrade? The real issue, imo, is having old files being able to be opened by a newer version. The way around seems to me a bit like a programming challenge, but not an issue for users. On the other hand, in the proprietary world, where all upgrades are costly, then someone might have an older version and no will to upgrade, and will eventually be given no other choice than upgrade if he/she wants to open a more recent file. Am I missing something? Louis
