From arosta@uclan.ac.uk Wed Aug 22 08:20:12 2001 Return-Path: X-Sender: arosta@uclan.ac.uk X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_3_1); 22 Aug 2001 15:20:11 -0000 Received: (qmail 79685 invoked from network); 22 Aug 2001 15:13:39 -0000 Received: from unknown (10.1.10.26) by l7.egroups.com with QMQP; 22 Aug 2001 15:13:39 -0000 Received: from unknown (HELO com1.uclan.ac.uk) (193.61.255.3) by mta1 with SMTP; 22 Aug 2001 15:13:38 -0000 Received: from gwise-gw1.uclan.ac.uk by com1.uclan.ac.uk with SMTP (Mailer); Wed, 22 Aug 2001 15:51:58 +0100 Received: from DI1-Message_Server by gwise-gw1.uclan.ac.uk with Novell_GroupWise; Wed, 22 Aug 2001 16:18:51 +0100 Message-Id: X-Mailer: Novell GroupWise 5.5.2 Date: Wed, 22 Aug 2001 16:18:25 +0100 To: lojban Subject: apostrophes and Google Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline From: And Rosta It seems that Google ignores apostrophes, which is a bit of a bummer if one= is looking for something in Lojban. In an ideal world the onus would be on= search engines to fix this problem, but in the world as it is, I'm perturb= ed, since I can't google for what I want to. It is a known problem that computers have problems with lojban apostrophes,= but hitherto the problems were such that they could be fixed by ad hoc rep= lacement by h. --And.