X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,bcba8c7403400943 X-Google-Attributes: gidf996b,public X-Google-ArrivalTime: 2001-10-31 11:49:33 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!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> <3bd9dd1e$0$757$edfadb0f@dspool01.news.tele.dk> <3BDE793C.2CE9EA56@rz.uni-karlsruhe.de> <3BDEF269.C233D5F@rz.uni-karlsruhe.de> Subject: JavE bug and algorithm for autoconverting to a figlet font Date: Wed, 31 Oct 2001 20:49:44 +0100 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: 52 Message-ID: <3be055cc$0$237$edfadb0f@dspool01.news.tele.dk> Organization: TDC Internet NNTP-Posting-Host: 62.243.165.90 X-Trace: 1004557773 dread02.news.tele.dk 237 62.243.165.90 X-Complaints-To: abuse@post.tele.dk Xref: archiver1.google.com alt.ascii-art:9334 > Hi there, > > Ok, I have written some documentation about the "FIGlet font export > assistant" in JavE. You will find it here: > http://www.jave.de/docs/figletexport/figletexport.html > > I hope it will clear things up rather than making it worse... > Any ideas for improvements are welcome. It certainly cleared up one big bug. If you open the Figlet Font Export Assistant (FFEA) .. change your mind , and open it later the blue adjustment boxes will not show - Thats why it failed so miserably for me the first time , and I had to edit the file by hand with a text editor without knowning the format. How about a F1 help function that open a help page for every window ? It's greatly needed .. In any case .. YES the short documentation you just wrote and linked was helpful. So was the official info you linked too. The FFEA still have faults .. fx it asumes that all letters are of equal width and that the spacing is the same. It should determine the width of each letter automaticly by searching for the first colum that only consisted of spaces. It could also try to determine the height and decent by looking for the common height and the max height .. max height would be height and decent would be max height - most common height , since most letters use a common height that is max height - decent. Using theese informations about width , height and decent it could also determine what was space between letters and waht was a letter. It could also try to autodetect what the letter was by looking at width, height and decent. An "a" would likely have no decent f.x. and would likely not be as tall as the max height , and the "a" would likely be followed by a "b" which would use max height but would not have a decent .. ect .. "g" "j" "y" would have decent .. "p" and "q" might have in some fonts and not in others All uppercase letter would likely not use decent but be of max height. "i" "l" "j" would likely not be of max width but be slim .. "m" and "w" would likely be very wide. I bet if you told me only the width, height, decent and the order of a number of letters that I could determine what they were without ever seeing them. JavE could be capable of this also.