X-Google-Language: ENGLISH,ASCII X-Google-Thread: f996b,e6bf8155ded630d1 X-Google-Attributes: gidf996b,public X-Google-ArrivalTime: 2001-12-30 11:04:02 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!newsswitch.lcs.mit.edu!feed2.onemain.com!feed1.onemain.com!newsfeeds.belnet.be!news.belnet.be!newsfeed00.sul.t-online.de!newsmm00.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail From: "Peter \"lastfuture\" Marquardt" Newsgroups: alt.ascii-art Subject: Re: Request : NFO TEXT GENERATOR Date: Sun, 30 Dec 2001 20:02:03 +0100 Organization: T-Online Lines: 26 Message-ID: References: <3c271ac8@news.swissonline.ch> <4aee0d8f3dJeremy@omba.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: news.t-online.com 1009738955 01 9499 +mhATDUTSbAIWP 011230 19:02:35 X-Complaints-To: abuse@t-online.com X-Sender: 520084321266-0001@t-dialin.net X-Newsreader: Forte Agent 1.6/32.525 Xref: archiver1.google.com alt.ascii-art:13109 On Mon, 24 Dec 2001 20:27:39 +0000 (GMT), Jeremy C B Nicoll wrote: > >> Why do special character's pose a problem for ascii art if for example >> everybody uses Courier New as the font of choice for viewing .txt files? > >> If this sounds stupid please forgive, quite new to ascii art. :) > >It might depend on what you mean by "special characters". If all people >viewing ascii art use machines which map characters onto standard >positions in ascii, then no problem, but it goes belly-up if brackets and >currency symbols and things like ^ are not at the same code points for >everyone. ^ is a valid ascii character and mapped the same everywhere. invalid are for example: � � � � � � � � � � � as they differ in most fonts -- ' + ` . ,-------------. + . ` . * ' \/ * . __ . ( alt.ascii-art ) . . ,-----------. ` (oO) -._'"- ( ,. _.' `-------------' ' ( you said it )_,' vv . `" `-` . ' * ` + `-----------' . JL