From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
Subject: | Re: to_char and i18n |
Date: | 2005-12-22 04:50:14 |
Message-ID: | 19091.1135227014@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> I thought to_char already had i18n behavior. What exactly are you
>> thinking of changing?
> The modifiers that are suitable to localize. Month and day names comes
> to mind and maybe others, I'm not sure what the state of the code is,
> but I can say that, at least, the 'month' and 'day' modifiers does not
> behave in a localized way.
Can we spell the names differently but keep to the same field widths?
I can see where it might cause problems to change the widths --- other
than that, no objection.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Manuel Sugawara | 2005-12-22 04:58:47 | Re: to_char and i18n |
Previous Message | Bruce Momjian | 2005-12-22 04:38:53 | Re: to_char and i18n |
From | Date | Subject | |
---|---|---|---|
Next Message | Manuel Sugawara | 2005-12-22 04:58:47 | Re: to_char and i18n |
Previous Message | Bruce Momjian | 2005-12-22 04:38:53 | Re: to_char and i18n |