Re: message string fixes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>, pgtranslation-translators(at)pgfoundry(dot)org
Subject: Re: message string fixes
Date: 2008-01-20 02:11:28
Message-ID: 2063.1200795088@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> For example, in regis.c there are several strings talking about "regis
> pattern". I had never heard of regis patterns. Turns out they are a
> fast regex subset, used AFAICT only by the ispell code. Searching the
> web I don't find any other reference to "regises" (regisen? reges?), so
> I think we should avoid using the term. How about just changing the
> messages to just say "regular expression" instead?

Then people would think that full regular expressions were meant.

It seems to me that a proper solution is to say something like "fast
regular expressions" and then document what that means in the ispell
dictionary documentation.

> Additionally, I would like to apply the attached patch. Are there
> objections?

Let's see, the first change is just so you can fool with the word
ordering, right? Seems OK to me, but are the other translators
going to complain about changing strings at this late date?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gilligan 2008-01-20 04:18:17 Re: [PATCH] Add size/acl information when listing databases
Previous Message Tom Lane 2008-01-20 02:06:59 Re: [PATCH] Add size/acl information when listing databases