X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,bcba8c7403400943 X-Google-Attributes: gidf996b,public X-Google-ArrivalTime: 2001-10-26 15:01:03 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!news.tele.dk!small.news.tele.dk!193.162.153.118!news.tele.dk!not-for-mail Reply-To: "CeeJay" From: "CeeJay" Newsgroups: alt.ascii-art References: <4tTZOz0OYRROH1yaCZAdAAQYhCOh@4ax.com> Subject: Re: Bored beyond belief Date: Sat, 27 Oct 2001 00:01:07 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Lines: 19 Message-ID: <3bd9dd1e$0$757$edfadb0f@dspool01.news.tele.dk> Organization: TDC Internet NNTP-Posting-Host: 62.243.165.90 X-Trace: 1004133662 dread04.news.tele.dk 757 62.243.165.90 X-Complaints-To: abuse@post.tele.dk Xref: archiver1.google.com alt.ascii-art:9002 > Turn it into a figlet font. I already did. - I posted it in alt.binaries.pictures.ascii (because this is not a binaries group) However it has a few bugs *g* , mainly because I had to guess how the figlet font format works. If anyone could supply me with info about the format it would be much apreciated. Oh .. btw .. Markus , if you're reading this : The JavE Figlet font creation stinks .. it needs to be documented and easier to use. I suggest letting the user input each char one by one - this reduces the risk of JavE guesswork fouling things up.