🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.ms-windows.programmer.misc
Article #2301

Re: Viewer for postscript doc files on NT sdk.

#2301
From: John Grant
Date: Sun, 24 Jan 1993 21:12
54 lines
2925 bytes
In article <727897437snz@chrism.demon.co.uk> chris@chrism.demon.co.uk writes:
>In article <1324@alsys1.aecom.yu.edu> manaster@yu1.yu.edu writes:
>
>>I  understand that there are some viewers that one can use to view
>> all the postscript documentation files on the NT sdk CD_ROM.
>>[ stuff deleted ]
>> Why on Earth did microsoft put this out in this fashion without a
>> viewer. It almost seems like this is part of some mad plan to
>> force people to BUY the docs.
>>
>
>Because the CD-ROM *also* contains the same information in Windows Write,
>and in "Help" format.  Lots of people have a PostScript printer, and for
>those people, supplying the documentation in PostScript format allows them
>to directly print the documentation without the bother of having to go via
>a word processor.
>
>> Thank you very much for the help.
>>
>> Henry Manaster
>>
	One of the things that annoys me about Windows 3.1 (but I
	do like almost all of it), is the idea of associating a
	file type with a utility to allow it to be accessed and/or
	printed.  So, if I associate *.c with notepad.exe, then
	I can just click on a .c file in File Manager and print it.
	Windows knows enough to fire up notepad to print it.
	*BUT*, what if I have all of these postscript files and I
	don't have an application that can read them in order to
	print them.  The only way to print them from File Manager
	is to have an application that can read PS files associated
	with them.  I am forced to jump out to DOS and do:
		c:\copy xxx.ps lpt1
	which seems kind of silly when Windows is supposed to be
	all-wonderful and all-powerful.

	Obviously, if I have a .WK1 file, I will need a Lotus
	(or clone) product that can read the file if I want to
	print it from File Manager.  But postscript files are
	already print-ready.  So to make a long story short,
	does Windows NT improve upon this Windows 3.1 'gotcha'?

	On a similar note, if *.BAT files are pre-associated as
	'executable' files, then how can I print a *.BAT file
	from File Manager by clicking in it.  Obviously I will
	have to manually fire up notepad on it.  File Manager
	needs a way to print a file just be selecting it (it would
	have to assume you know what you are doing and that the
	file is already in appropriate print-ready format for
	the printer).
-- 
John A. Grant						jagrant@emr1.emr.ca
Airborne Geophysics
Geological Survey of Canada, Ottawa
Technical Details
Message-ID: <1993Jan24.211233.23040@emr1.emr.ca>
Path: arc1-ca.pugleaf.net!sparky!uunet!europa.asd.contel.com!howland.reston.ans.net!usc!cs.utexas.edu!torn!nott!emr1!jagrant
References: <1324@alsys1.aecom.yu.edu> <727897437snz@chrism.demon.co.uk>

Show Full Headers
Complete Article Headers
Newsgroups: comp.os.ms-windows.programmer.misc
Path: arc1-ca.pugleaf.net!sparky!uunet!europa.asd.contel.com!howland.reston.ans.net!usc!cs.utexas.edu!torn!nott!emr1!jagrant
From: jagrant@emr1.emr.ca (John Grant)
Subject: Re: Viewer for postscript doc files on NT sdk. 
Message-ID: <1993Jan24.211233.23040@emr1.emr.ca>
Organization: Energy, Mines, and Resources, Ottawa
References: <1324@alsys1.aecom.yu.edu> <727897437snz@chrism.demon.co.uk>
Date: Sun, 24 Jan 1993 21:12:33 GMT
Lines: 54