2004.03.19 17:50 "[Tiff] txt to tiff", by Soledad Alborno

2004.03.20 16:18 "Re: [Tiff] txt to tiff", by Joris Van Damme

they have no sales/marketing department to tell them they are wrong.

That's probably the cause of their productivity...

I keep seeing the other side of this story, though, being native Windows closed source culture myself. I keep wondering how you earn food for your kids, and how you ensure that you don't make life impossible for other people earning food for their kids. But please regard this as just a loos remark, since a discussion about open/closed source and freeware/economy is off-topic and cannot lead to a conclusion. I for one am willing to admit I see advantages and disadvantages in both sides, anyways.

The user still has the minor challenge of obtaining the two programs for his operating systems. If he is using Linux, then these two programs are likely already present. If he is using Windows, then they will need to be downloaded from somewhere, or compiled from source code.

If Windows is used, then the command 'gswin32c' should be used rather than 'gs'.

I see. The 'threshold' for using 3rd party stuff is much higher, where I come from. We dislike using other executables in ours, this way, probably because it reminds us too much of DOS days. And I personally dislike all alternatives like COM and such, too, probably for the same reason. Is probably the reason why I cannot seem to meet any deadline, ever, and am slowly growing seriously fed up with my job. OTOH, it's also the reason that I still know what's going on, underneath, and why my software *does* gain speed as hardware becomes faster, instead of gaining weight only. You wizards are in danger of ending up more like power-users and scripters then programmers, in the end... Don't be offended by the remark, though, I do acknowledge that your way is probably most productive.

Joris Van Damme
Download your free TIFF tag viewer for windows here: