From owner-freebsd-isp Mon Sep 16 10:28:31 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA19737 for isp-outgoing; Mon, 16 Sep 1996 10:28:31 -0700 (PDT) Received: from i-gw.dalsys.com (i-gw.dalsys.com [207.42.153.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA19729 for ; Mon, 16 Sep 1996 10:28:26 -0700 (PDT) Received: (from smap@localhost) by i-gw.dalsys.com (8.6.9/8.6.9) id MAA06765; Mon, 16 Sep 1996 12:28:13 -0500 Received: from future.dsc.dalsys.com(199.170.161.3) by i-gw.dalsys.com via smap (V1.3) id sma006763; Mon Sep 16 12:28:05 1996 Received: from richards.dsc.dalsys.com by future.dsc.dalsys.com (AIX 3.2/UCB 5.64/8.6.12) id AA31559; Mon, 16 Sep 1996 12:32:53 -0500 Message-Id: <323DAB73.3BF2@herald.net> Date: Mon, 16 Sep 1996 12:33:07 -0700 From: Richard Stanford Reply-To: richards@herald.net Organization: Herald Communications X-Mailer: Mozilla 3.0 (Win16; I) Mime-Version: 1.0 To: Rick Gray Cc: isp@freebsd.org Subject: Re: Internet Explorer bug? References: <1.5.4.32.19960916152842.0068ad1c@nwpros.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rick Gray wrote: > I created a customer's home page. On it is a Swedish word with which I had > to use Å to denote an accent. Now the customer and a few others when > viewing the page see only the first part of the word up to the symbol. The > remainder of the word is missing. I use both Netscape and Explorer and I > have no problem seeing the whole word. Internet Explorer and Netscape Navigator will do their best to "fix" broken HTML. This can lead to certain errors being masked, until the page is viewed by lynx or another more literal browser. The problem here is that any key-sequence beginning with & ( < & © ... ) should end with a semicolon ( ; ). I would suggest testing all pages with lynx as a matter of course (and every other browser you can get your hands on). This "feature" of Netscape and Microsoft browsers can cause some horrendous mistakes to appear correct. For instance, on a couple of occasions I've accidentally written: ... word word emphasized-word word word ... Netscape 2.0+ will interpret the as a for me. Gee, thanks. I can see why they do this, but it means that you should always double-check everything you do (MSIE1.x for WIN16 shows the error as an error, other browsers may too). Caveat Emptor, indeed. -Richard