Re: Potential to_char localization bug - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Potential to_char localization bug
Date
Msg-id 200611272020.kARKKJ207264@momjian.us
Whole thread Raw
In response to Re: Potential to_char localization bug  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Dennis Bjorklund wrote:
> > > Peter Eisentraut skrev:
> > > >                 case 4:
> > > >                         m = _("May");
> > > >                         break;
> > > > 
> > > > 
> > > > Haven't thought of a fix yet.
> > > 
> > > A common way is to use something of the form
> > > 
> > >     m = _("S:May") + 2;
> > > 
> > > and a comment above (that is copied to the .po file) explaining that the 
> > > S: should be in the translated string as well.
> > 
> > OK, I am ready to admit I am lost.  What is the problem here?
> 
> The problem is that "May" is both a month name, and the shorthand for a
> month name.  So there is no way to determine which is which for the
> translation machinery.  (Incidentally I noticed that what I proposed
> doesn't fix the problem, in fact it doesn't work at all).

Thanks, I get it now.  ;-)

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: Potential to_char localization bug
Next
From: Neil Conway
Date:
Subject: Re: Storing a dynahash for an entire connection or