At 8:32 PM -0300 8/13/03, Joao S. O. Bueno wrote:
People have considered TIFF, PSD in this newer thread - before the
Camp, on the list, we were almost closed in an ar archive, with XML informatin and possibly PNG raster data inside.

Which is still a valid approach, but would DEFINITELY require a standard library since 'ar' isn't a standard outside the Linix world...

Why not settle for a Postscript subset?

Because Postscript is dead. It hasn't been updated in over 6 years, and Adobe themselves are slowly moving towards PDF-based solutions, including printing.

Also, Postscript is a programming language. You would need to implement a full parser and interpreter for it. NOT a fun thing.

You'd be better off heading down the PDF route...All the benefits of PS, but a LOT easier to implement and MUCH more extensible and supported.

The major one, of course, is that the file would be essentialy "auto renderable" - no need of GIMP, neither of any other program, to get it printed.

Assuming a PS printer...

But most users either have PCL or raster-based printers...

Since PSD and TIFF are used by ADOBE, ADOBE also has a program that makes use of postscript subsets.. I just do not remember which file type it is.

Versions of Adobe Illustrator <= 8 used a subset of EPS (Encapsulated Postscript) as its native file format. As of version 9, it now uses PDF as the file format.

It can have color profiling support - it is on the specifications. It has support for multiple compression standards... (ok, maybe you have to encode the decompressor algorithm inside the file as well if you want something too different)

PS doesn't support "plug-in" filters...

Text layers would have trivial, transformation independent, support.

Storing the text isn't the hard part of text layers...

Leonard -- --------------------------------------------------------------------------- Leonard Rosenthol <mailto:[EMAIL PROTECTED]> <> _______________________________________________ Gimp-developer mailing list [EMAIL PROTECTED]

Reply via email to