- 2004.03.20 08:44 "Re: [Tiff] txt to tiff", by Andrey Kiselev
-
2004.03.20 14:53 "Re: [Tiff] txt to tiff", by Bob Friesenhahn
-
2004.03.20 15:18 "Re: [Tiff] txt to tiff", by Joris Van Damme
-
2004.03.20 15:32 "Re: [Tiff] txt to tiff", by Bob Friesenhahn
-
2004.03.20 15:44 "Re: [Tiff] txt to tiff", by Joris Van Damme
- 2004.03.20 15:53 "Re: [Tiff] txt to tiff", by Bob Friesenhahn
-
2004.03.20 15:44 "Re: [Tiff] txt to tiff", by Joris Van Damme
-
2004.03.20 15:32 "Re: [Tiff] txt to tiff", by Bob Friesenhahn
-
2004.03.20 15:18 "Re: [Tiff] txt to tiff", by Joris Van Damme
2004.03.20 21:50 "Re: [Tiff] txt to tiff", by Andrey Kiselev
The other side of this story is 'what is going on underneath'. You solution converts txt to postscript, and does a hell of a lot of work rendering postscript, next. There's more then just 'call overhead' involved, there's actual loading and initializing of two executables. My solution renders txt directly, without going through postscript. There's no loading of executables. Your solution deployed in a commercial distribution, adds two seperate whatevers (I'm not sure how to call them) to the nightmare. My solution doesn't envolve a single DLL.
And your solution includes writing yet another typesetting engine. Not a trivial task even for very skilled programmer, isn't it? ;-)
Andrey
Andrey V. Kiselev
Home phone: +7 812 5274898 ICQ# 26871517