summaryrefslogtreecommitdiff
path: root/fonts/psfonts/corelpak/readme.txt
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
committerNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
commite0c6872cf40896c7be36b11dcc744620f10adf1d (patch)
tree60335e10d2f4354b0674ec22d7b53f0f8abee672 /fonts/psfonts/corelpak/readme.txt
Initial commit
Diffstat (limited to 'fonts/psfonts/corelpak/readme.txt')
-rw-r--r--fonts/psfonts/corelpak/readme.txt137
1 files changed, 137 insertions, 0 deletions
diff --git a/fonts/psfonts/corelpak/readme.txt b/fonts/psfonts/corelpak/readme.txt
new file mode 100644
index 0000000000..f3bfd4de0e
--- /dev/null
+++ b/fonts/psfonts/corelpak/readme.txt
@@ -0,0 +1,137 @@
+Corelpak 0.50 (JW)
+=================
+
+This package provides an easy and cheap way for using standard postscript fonts
+with LaTex2e. Instead of using real Adobe fonts, which are rather expensive,
+it uses PS-Fonts delivered with the comercial software Corel. This software is
+often bundled with your computer and is shipped with LOTS of fonts (almost from
+Bitstream).
+Unfortunately, mostly they are differently named than their original pedants.
+Times for example is named Dutch 801. This means, Dutch 801 is NOT a poor
+replacement almost like Times, moreover: Dutch 801 IS Times.
+
+So there are following tasks to do:
+
+1.) Find common name for Corel font xy
+ (for example, use the books TYPECOSMIC or file bitstream.aka
+ (CTAN:info/fontname))
+2.) Rename its parts (*.pfb and *.afm) following the KARL BERRY scheme (*)
+3.) Create the *.tfm, *.sty, *.fd, *.vf and *.map files
+ (use the fontinst package)
+4.) Copy all this stuff to an appropriate place.
+
+That's it! If you want to preview and print the output via ghostscript, then
+
+5.) Tell Ghostscript how to find and name the fonts
+ (setup the fontmap)
+
+
+Fortunately, all these steps are already done!
+--- Attention ---
+(*) Except step 2. This has to be done by YOU! As a help, look at file fontmap,
+it contains the internal names, Berry names and Corel filenames (xxxxa___.pfb).
+A complete list can be found in CTAN: \tex-archive\info\fontnames.
+
+EXAMPLE: Times Roman (Dutch 801) can be found as file 0011a___.pfb on the
+ Corel-CD. Copy it to somewhere ghostscript and dvips can find
+ it and rename it to btmr.pfb
+
+There is an easy workaround for this.
+I've had to use the K. Berry scheme (fontinst told me) - You have another
+choice: Simply within fontmap (and - if necessary - dvips-maps *.nrs)
+replace the Berry-names by the "Corel" names
+
+EXAMPLE: ghostview fontmap: /Times-Roman (0011a___.pfb) ;
+ :
+
+ dvips btm.nrs: btmr0 Dutch801BT-Roman <0011a___.pfb
+ :
+
+
+This package obviously does NOT contain the Corel ps-fonts itself. If you
+do not have them, this package is useless.
+Furthermore, it provides the LaTex-files for only a few of them, because
+1.) An hour is an hour is an hour
+2.) Check the version number, there is room for hope
+3.) Much of the cd fonts are decorative and therefore less important for a
+ text system like LaTex
+4.) I considered mainly these fonts, which provide beside the standard also
+ the shape italic and weight bold
+5.) the '35' Adobe standard fonts, I thought, have to be seen as an first
+ approach and mostly important (but aren't complete, anyway!)
+
+Currently there are 50 fonts available:
+ Serif: 30
+ Sans Serif: 11
+ TypeWriter: 1
+ Decorative: 8
+
+See nametabl.txt for currently available fonts in this package.
+
+
+Installing Corelpak
+=====================
+
+Package contents:
+
+o folder TFM: Put it, where Latex can find it. It contains the
+ Tex-font metrics
+o folder VF: Put it, where your dvi-driver can find it. It contains
+ the virtual fonts.
+o folder PSNFSS: Put it, where Latex can find it. It contains the *.sty
+ and *.fd files.
+o folder DVIPS: Put it, where dvips can find it. It contains the
+ *.map-files for dvips
+o readme.txt This file
+o nametabl.txt Table of "official" names, Corel font names and names
+ of LaTex2e *.sty files
+o fontmap.crk Additional entries for Fontmap (Ghostscript). Use this
+ solely or merge it to the original fontmap
+o pak2me.bat copies a given psfont-installation for use with EmTeX
+ (due to the absence of recursive subdirectory search
+ strategies (!!-feature is not allowed in dvips),
+ a structure like fonts/ps/adobe/Times/tfm is not possible)
+o alpak2me.bat copies all fonts to the appropriate place for EmTeX.
+ Configure pak2me.bat before using alpak2me.bat!
+
+
+All you have to do is:
+
+1.) Put the (contents of the) folders TFM, VF, PSNFSS and DVIPS at their
+ appropriate places
+2.) merge the *.map files (DOS: copy /b *.map psfonts.map)
+3.) if you want to include the fonts in your dvips-output (for example, you
+ don't want to use the ghostscript fontmap-feature, or want to download
+ them to your printer), merge the *.nrs files (nrs: not resident)
+ (DOS: copy /b *.nrs psfonts.map)
+4.) See comment for step 2.) at the beginning of this document
+
+If you use ghostscript:
+
+5.) copy fontmap.crk to your ghostscript directory and rename it to fontmap.
+ Don't forget to backup the original!!
+ Optionally you can merge both together. Check for double entries.
+
+
+Have fun!!
+Suggestions, wishes, bug reports:
+woch@informatik.uni-koblenz.de
+
+
+
+Some details
+=============
+
+o I used the fontinst package v1.335 for generating the LaTex-related stuff
+o Even if there are more widths, shapes, weights etc. available for some
+ fonts, I always used solely roman/book, italic, bold, bolditalic.
+ The reason is to be found in my lack of understanding what the heck
+ fontinst really does.
+
+
+Legal Stuff
+============
+
+Do, whatever you want to do with this package, except modified distributing it
+under the same name.
+