Received: with ECARTIS (v1.0.0; list gopher); Tue, 04 Apr 2006 10:12:52 -0500 (CDT) Received: from smtp2.atlavia.it ([213.199.4.210] helo=smtp.atlavia.it) by glockenspiel.complete.org with esmtp (Exim 4.50) id 1FQnD6-0000uB-GM for gopher@complete.org; Tue, 04 Apr 2006 10:12:51 -0500 Received: from kanthaka.localdomain (ppp-62-123-13-160.dial.atlanet.it [62.123.13.160] (may be forged)) by smtp.atlavia.it (8.10.1/8.10.1) with ESMTP id k34Fm8D17970 for ; Tue, 4 Apr 2006 17:48:08 +0200 (MET DST) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by kanthaka.localdomain (8.13.6/8.13.4) with ESMTP id k3484FZZ003049 for ; Tue, 4 Apr 2006 10:04:16 +0200 Message-ID: <4432287F.90505@route-add.net> Date: Tue, 04 Apr 2006 10:04:15 +0200 From: Alessandro Selli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060201 SeaMonkey/1.0 MIME-Version: 1.0 To: gopher@complete.org Subject: [gopher] Re: Handling of ISO-8859-* character sets References: <200604031527.k33FRWm4012410@floodgap.com> In-Reply-To: <200604031527.k33FRWm4012410@floodgap.com> Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.atlavia.it id k34Fm8D17970 X-Spam-Status: No (score 0.1): FORGED_RCVD_HELO=0.05 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Tue, 04 Apr 2006 10:12:51 -0500 X-archive-position: 1279 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: dhatarattha@route-add.net Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher Cameron Kaiser wrote: >> Hello, >> Before I run the risk of making a fool of myself and open a bug repor= t=20 >> that should not be opened, I need to know if someone of you can and is= =20 >> willing to give me an idea on how are ISO-8859 character sets handled = in=20 >> gopher menus. >> I think their correct display is left to the client, the server and th= e=20 >> protocol do not take in account any particular character set, right? > > As far as I know, no, they do not. The client is responsible for the > rendering. What's the selector/URL? It's gopher://gopher.route-add.net/. The menu should read: ______________________________________________________________________ | Benvenuti sul server sperimentale Gopher di "route-add.net"! | | | | Il contenuto del server non =E8 ancora definito, sar=E0 per=F2 = | | probabilmente destinato alla distribuzione di script vari e di | | documenti tecnici sull'amministrazione di sistemi Unix. | | | | La macchina sulla quale gira il server =E8 una SparcStation5-85 | | della Sun Microsystems con Debian GNU/Linux quale sistema operativo | | mentre il server gopher =E8 il Bucktooth 0.2 | ______________________________________________________________________ while instead on Seamonkey 1.0 I get this: ______________________________________________________________________ | Benvenuti sul server sperimentale Gopher di "route-add.net"! |=20 |=20 | | | | | | probabilmente destinato alla distribuzione di script vari e di | | documenti tecnici sull'amministrazione di sistemi Unix. | | | | | | della Sun Microsystems con Debian GNU/Linux quale sistema operativo |=09 _______________________________________________________________________ --=20 Alessandro Selli Tel: 340.839.73.05 http://alessandro.route-add.net