Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id DFD8E9FC4D4 for ; Thu, 25 Oct 2007 10:12:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 57625-09 for ; Thu, 25 Oct 2007 10:12:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 068BD9FC4C9 for ; Thu, 25 Oct 2007 10:12:34 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-215-196.bk12-dsl.surnet.cl [201.221.215.196]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l9PDCX5f001458; Thu, 25 Oct 2007 06:12:34 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id AED9D47C79; Thu, 25 Oct 2007 10:12:24 -0300 (CLST) Date: Thu, 25 Oct 2007 10:12:24 -0300 From: Alvaro Herrera To: Tom Lane Cc: pgsql-docs@postgreSQL.org Subject: Re: Example non-Latin words for text search parser docs? Message-ID: <20071025131224.GI5661@alvh.no-ip.org> References: <28960.1192998593@sss.pgh.pa.us> <20071021220857.GC12111@alvh.no-ip.org> <2965.1193174845@sss.pgh.pa.us> <20071023213649.GV18013@alvh.no-ip.org> <4678.1193178589@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4678.1193178589@sss.pgh.pa.us> User-Agent: Mutt/1.5.16 (2007-06-11) X-Virus-Scanned: ClamAV 0.91.1/4593/Thu Oct 25 00:03:02 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Thu, 25 Oct 2007 06:12:34 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/79 X-Sequence-Number: 4500 Tom Lane wrote: > Alvaro Herrera writes: > > Actually I was wondering if we should use actual words. So instead of > > "foo" we could use "elephant" for asciiword and "Éléphant" (french) for > > word. And for the hword, "sous-espèces" (which appears on the French > > Wikipedia) would do. > > Hmm ... I see a potential problem with that, which is that if someone > happened to be viewing the page on something that dropped the accents, > or even just made them too small to be easily readable, the examples > wouldn't make any sense at all. > > I have no problem with "elephant" as a sample asciiword, but for the > sample non-ascii word I'd suggest something that (a) is clearly not > English and (b) as much as possible, everybody knows has an accent. > At least in large parts of the US, something like "mañana" would > work nicely. OK I went with that. I also used real spanish hyphenated words in the hword examples. I also changed the domains foo.com to example.com, just because I'm anal enough to do it. The hword_asciipart I'm not 100% sure about. I used this: militar in the context político-militar, or postgresql in the context postgresql-beta1 What I wanted to emphasize here is that it's the "ascii-ness" of the part that matters, not that of the complete token. The reason I'm not sure about it is that it makes the table wider. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.