On 24 Jun 2005 at 13:10, Tyler Turner wrote: > --- "David W. Fenton" <[EMAIL PROTECTED]> wrote:
> > Longhorn is *not* going to make their lives simpler, > > because MS is > > implementing a competitor to PDF in Longhorn, and > > perhaps this new > > standard will go beyond that towards doing what EPS > > does. MM is going > > to have to decide if they will support that in > > Longhorn, as well as > > deciding if they're going to fix EPS, which probably > > won't be made > > any easier in Longhorn (it may very well be no > > harder, either). > > My point wasn't that it would make their lives simpler > but that it could be the type of change that forces > them to work with that area of the program. I didn't > mention it, but I also was thinking about the special > PDF competitor that Microsoft is including. If > MakeMusic chooses to support that, the work they do > there might very well spill over into EPS. Who knows > how related the technologies will be. I would actually > be somewhat surprised if working on one didn't help > with the other. Well, as a programmer, I'd be surprised if supporting the new proprietary MS technology did not make supporting PostScript and EPS more difficult. There certainly is unlikely to be any overlap in the codebase for handling the two. The whole reason WinFin does poorly with EPS is because Windows just doesn't provide any help for PostScript at all -- it's not a basic part of the OS as it is on the Mac. MS's new proprietary competitor for PDF/PostScript will not bring Windows any closer to the Mac in its support for PostScript formats. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
