home *** CD-ROM | disk | FTP | other *** search
- Short: Patch FW to show and print EPS graphics with text
- Type: text/print
- Uploader: UpperDesign@zeus.ci.ua.pt (Manuel Lemos)
- Author: UpperDesign@zeus.ci.ua.pt (Manuel Lemos)
-
- DESCRIPTION
-
- This archive contains a patch to FinalWriter init.ps that is used to
- initialize the EPS interpreter letting it render EPS graphics that use
- PostScript text fonts to screen and to non-PostScript printers.
-
- Apparently the support for text fonts was deliberatly disabled by Softwood.
- This patches re-enables that support.
-
-
- DISCLAIMER
-
- With this document I make no warranties or representations, either
- expressed or implied, with respect to the program described herein. The
- program and the information presented herein is being supplied on an `as
- is' basis and is expressly subject to change without notice. The entire
- risk as to the use of the program and the information presented is assumed
- by the user. In no event will I be liable for direct, indirect,
- incidental, or consequential damages resulting from any claim arising out
- of the use of the program or the information presented herein, even if I
- have been advised of the possibilities of such damages.
-
-
- INSTALLATION
-
- Use the Shell and change the current directory to wherever you have
- unpacked this archive and then execute the following statments:
-
- set FINALWRITER WhereEverYouHaveInstalledFinalWriterInDisk
- Copy FinalWriter-init.ps.pch $FINALWRITER/FWFiles
- CD $FINALWRITER/FWFiles
- Copy init.ps init.ps.old
- spatch -oinit.ps -pFinalWriter-init.ps.pch init.ps.old
-
-
- SO, WHAT WAS THE PROBLEM?
-
- I found two problems:
-
- 1) The PostScript interpreter needs to know where in disk are located the
- fonts it needs. The file that initializes the interpreter
- (FWFiles/init.ps) had the lines that define that path in comment.
-
- This patch uncomments those lines, setting the font search path to
- PSFONTS: directory. You can edit the init.ps file after applying this
- patch to change this path to another directory.
-
- You need to have PostScript fonts (Type 1 and Type 3) installed in that
- directory. If you don't have any PostScript fonts, you may find them in
- Fish Disk 828, 829 and 830. These fonts quality is not very good but
- they'll do for the purpose of rendering EPS graphics to screen and to
- non-PostScript printers.
-
- You may use as well Adobe's ATM fonts that are very good or use any of
- those hundreds that come in CDs for a bargain.
-
- Be careful to restore the original names of the fonts of those files.
- Some collections of fonts were meant to be used in MS-DOS machines, so
- their filenames are truncated. There is an utility in Aminet that does
- that for you to Type 1 fonts.
-
- 2) The PostScript code in the init.ps file that defines ISOLatin1Encoding
- array that is the table in which is defined the names of glyphs used by
- the character set that Amiga uses was not very well defined.
-
- This could lead to erroneous character mapping when an EPS file with
- text was being imported to FinalWriter.
-
- ISOLatin1Encoding table is only expected to be defined by Level 2
- PostScript interpreters. Although FinalWriter PostScript interpreter is
- not a full Level 2 interpreter, the init.ps file was defining
- ISOLatin1Encoding table.
-
- Some EPS/PS files assume when ISOLatin1Encoding is defined, it is well
- defined which is not the case. This patch fixes the definition of this
- table.
-
- Many EPS/PS files generated by for instance Amiga programs, correctly
- redefine ISOLatin1Encoding table regardless if it is already defined, so
- they don't suffer from this fault of the FinalWriter init.ps.
-
-
- Manuel Lemos
- 17.2.95
- UpperDesign@zeus.ci.ua.pt
- Apartado 391
- 3800 AVEIRO
- PORTUGAL
-