--- BUILD/ttf2pt1-3.4.3/ttf2pt1.1.manpages	2002-12-03 02:51:41.000000000 +0100
+++ BUILD/ttf2pt1-3.4.3/ttf2pt1.1	2003-10-26 14:24:48.000000000 +0100
@@ -228,11 +228,7 @@
 would be inaccessible anyway and would only consume the disk space. 
 But some applications are clever enough to change the encoding on
 the fly and thus use the other glyphs, in this case they could
-benefit from using this option. But there is a catch: the X11 library
-has rather low limit for the font size. Including more glyphs increases
-the file size and thus increases the chance of hitting this limit.
-See \f(CWapp/X11/README\fR for the description of a 
-patch to X11 which fixes this problem.
+benefit from using this option.
 .Ip "\(bu" 2
 \f(CW\fB-b\fR\fR \- Encode the resulting font to produce a ready \f(CW.pfb\fR file.
 .Ip "\(bu" 2
@@ -413,7 +409,7 @@
 The default value is 128, according to the limitation in X11. This seems to
 be the lowest (and thus the safest) widespread value. To display the
 hint stack depth required by each glyph in a \f(CW.t1a\fR file use the script
-\f(CWscripts/cntstems.pl\fR.
+\f(CWttf2pt1_cntstems\fR.
 .Ip "\(bu" 2
 \f(CW\fB-O \fIsuboptions\fR\fR\fR \- Outline processing options. The suboptions
 may be lowercase or uppercase, the lowercase ones disable the features,
@@ -443,8 +439,7 @@
 the chance of hitting this limit (that does not mean that you shall hit it
 but you may if your fonts are particularly big). This is especially 
 probable for Unicode fonts converted with option \*(L'\fB\-a\fR\*(R', so you may want to 
-use \*(L'\fB\-a\fR\*(R' together with \*(L'\fB\-Ou\fR\*(R'. See \f(CWapp/X11/README\fR for the description of 
-a patch to X11 which fixes this problem. Second, some rasterizers (again,
+use \*(L'\fB\-a\fR\*(R' together with \*(L'\fB\-Ou\fR\*(R'. Second, some rasterizers (again,
 X11 is the typical example) have a limitation for total number of hints
 used when drawing a glyph (also known as the hint stack depth). If that
 stack overflows the glyph is ignored. Starting from version 3.22 \f(CWttf2pt1\fR
@@ -455,11 +450,7 @@
 substituted hints look better than the fonts without them or at least the 
 same. Still if the original fonts are not well-designed the detailed 
 hinting may emphasize the defects of the design, such as non-even thickness 
-of lines. So provided that you are not afraid of the X11 bug the best idea 
-would be to generate a font with this feature and without it, then compare 
-the results using the program \f(CWother/cmpf\fR (see the description 
-in \f(CWother/README\fR) and decide which one looks better.
-\fBDefault: enabled\fR
+of lines. \fBDefault: enabled\fR
 .Sp
 \f(CW\fBo/O\fR\fR \- Space optimization of the outlines\*(R' code. This kind of optimization
 never hurts, and the only reason to disable this feature is for comparison 
@@ -634,21 +625,11 @@
 .Ip "\(bu" 2
 \s-1TTF2PT1_SHAREDIR\s0/*
 .Ip "\(bu" 2
-\s-1TTF2PT1_SHAREDIR/\s0scripts/*
-.Ip "\(bu" 2
-\s-1TTF2PT1_SHAREDIR/\s0other/*
-.Ip "\(bu" 2
-\s-1TTF2PT1_SHAREDIR/README\s0
+\s-1TTF2PT1_DOCDIR/README\s0
 .Ip "\(bu" 2
-\s-1TTF2PT1_SHAREDIR/FONTS\s0
+\s-1TTF2PT1_DOCDIR/FONTS\s0
 .SH "SEE ALSO"
 .Ip "\(bu" 4
-the \fIttf2pt1_convert(1)\fR manpage
-.Ip "\(bu" 4
-the \fIttf2pt1_x2gs(1)\fR manpage
-.Ip "\(bu" 4
-the \fIt1asm(1)\fR manpage
-.Ip "\(bu" 4
 ttf2pt1-announce@lists.sourceforge.net
 .Sp
 The mailing list with announcements about ttf2pt1. It is a moderated mailing
@@ -684,15 +665,15 @@
 this for now we recommend using the FreeType-based parser (option
 \&\*(R'\fB\-p ft\fR') with the \*(L"\f(CWplane\fR\*(R" language.
 .Sh "Troubleshooting and bug reports"
-Have problems with conversion of some font ? The converter dumps core ? Or your
-printer refuses to understand the converted fonts ? Or some characters are 
-missing ? Or some characters look strange ?
+Do you have problems with conversion of some font? Does the converter dump core? Or does your
+printer refuse to understand the converted fonts? Or are some characters 
+missing? Or do some characters look strange?
 .PP
 Send the bug reports to the ttf2pt1 development mailing list at
 ttf2pt1-devel@lists.sourceforge.net.
 .PP
 Try to collect more information about the problem and include it into
-the bug report. (Of course, even better if you would provide a ready
+the bug report. (Of course, even better if you could provide a ready
 fix, but just a detailed bug report is also good). Provide detailed
 information about your problem, this will speed up the response greatly.
 Don't just write \*(L"this font looks strange after conversion\*(R" but describe