X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,e6bf8155ded630d1 X-Google-Attributes: gidf996b,public X-Google-ArrivalTime: 2001-12-24 12:40:14 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!dispose.news.demon.net!news.demon.co.uk!demon!omba.demon.co.uk!Jeremy From: Jeremy C B Nicoll Newsgroups: alt.ascii-art Subject: Re: Request : NFO TEXT GENERATOR Date: Mon, 24 Dec 2001 20:27:39 +0000 (GMT) Organization: None - home Message-ID: <4aee0d8f3dJeremy@omba.demon.co.uk> References: <3c271ac8@news.swissonline.ch> NNTP-Posting-Host: omba.demon.co.uk X-NNTP-Posting-Host: omba.demon.co.uk:158.152.58.5 X-Trace: news.demon.co.uk 1009226388 nnrp-10:29858 NO-IDENT omba.demon.co.uk:158.152.58.5 X-Complaints-To: abuse@demon.net User-Agent: Pluto/2.03a (RISC-OS/3.70) Lines: 14 Xref: archiver1.google.com alt.ascii-art:12743 > 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. -- Jeremy C B Nicoll - my opinions are my own.