Potential to_char localization bug - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Potential to_char localization bug
Date
Msg-id 200611271240.04239.peter_e@gmx.net
Whole thread Raw
Responses Re: Potential to_char localization bug  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Potential to_char localization bug  (Dennis Bjorklund <db@zigo.dhs.org>)
List pgsql-hackers
Here is a localization bug waiting to happen:

static char *
localize_month_full(int index)
{       char       *m = NULL;
       switch (index)       {               case 4:                       m = _("May");                       break;


static char *
localize_month(int index)
{       char       *m = NULL;
       switch (index)       {               case 4:                       m = _("May");                       break;


Haven't thought of a fix yet.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Configuring BLCKSZ and XLOGSEGSZ (in 8.3)
Next
From: "Heikki Linnakangas"
Date:
Subject: Re: [CORE] RC1 blocker issues