Talk: Errors in Figlet fonts

On 16 May 1995, The Dark Dragon wrote:

> Nice fonts!
> however... they have errors...

	Yes, they did indeed, didn't they... But! I fixed them up. I've
already posted one of them... I think it was 4max.flf... But I'll check
before I post the other two. And they'll be coming up right after this post.
:)

  ___  _                      _a' /(   <.  Simon Bradley, Knight Protector!
 / __><_>._ _ _  ___ ._ _  ~~ _}\ \(  _  ) E-mail: syb...@aber.ac.uk
 \__ \| || ' ' |/ . \| ' |       \(,_(,)'  Finger: syb...@osfb.aber.ac.uk
 <___/|_||_|_|_|\___/|_|_|      ._>, _>,   WWW: http://www.aber.ac.uk/~syb3/

	Well, the fonts wouldn't work for most UNIX users because of the
presence of a carriage return at the end of each line. (I *think* these were
your fonts, but I may be mixing them up with some other fonts that had
errors...) Also, several letters had one too many or one not enough lines
making up that letter. And other lines in the font files had an extra
character in them before the #, which was used to mark the end of a line.
Um... What else? Some last lines of letters (`letters' means Figlet letters)
were missing the second #. 

	I think that's about all. The way to get around all of these problems
is to use chkfont to check the font before you post it. chkfont will tell you
on what line an error is, so you can easily find it and fix it with any text
editor that allows you to jump to a certain line in a file. It took me only a
couple of minutes to fix up your fonts. It's worth doing! :)

  ___  _                      _a' /(   <.  Simon Bradley, Knight Protector!
 / __><_>._ _ _  ___ ._ _  ~~ _}\ \(  _  ) E-mail: syb...@aber.ac.uk
 \__ \| || ' ' |/ . \| ' |       \(,_(,)'  Finger: syb...@osfb.aber.ac.uk
 <___/|_||_|_|_|\___/|_|_|      ._>, _>,   WWW: http://www.aber.ac.uk/~syb3/

On 17 May 1995, Philip Menke wrote:

> Thank you for doing so, but could you please tell me what was wrong with 
> them? I knew some things went wrong with fraktur.flf, due to the method 
> of creating that, but the other ones I hadn't discovered anything wrong 
> with as yet. However, again my thanks for fixing them up.