Re: [PATCHES] Solve a problem of LC_TIME of windows. - Mailing list pgsql-hackers

From Hiroshi Saito
Subject Re: [PATCHES] Solve a problem of LC_TIME of windows.
Date
Msg-id 68B4047E859E4A4C97FAC4077F23DDFA@HIRO57887DE653
Whole thread Raw
In response to Re: [PATCHES] Solve a problem of LC_TIME of windows.  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [PATCHES] Solve a problem of LC_TIME of windows.
List pgsql-hackers
Hi ITAGAKI-san.

Um, It was not supported. 
http://winpg.jp/~saito/pg_work/LC_MESSAGE_CHECK/LC_TIME_PATCH/ITAGAKI_PATCH.txt

The test of my various past is reproduced. Then, I proposed the management 
regarded as best in them.  and, to Magnus-san.
Does the reason for persisting in wsftime exceed a safe reason? 

However, I may have missed something...

Regards,
Hiroshi Saito

----- Original Message ----- 
From: "ITAGAKI Takahiro" <itagaki.takahiro@oss.ntt.co.jp>


> 
> "Hiroshi Saito" <z-saito@guitar.ocn.ne.jp> wrote:
> 
>> Umm, format operand seems to be a wide character sequence.
> 
> Here is a patch to work around the wide character format string.
> The hack is the following line:
>    +#define strftime(a,b,c,d) strftime_win32(a,b,L##c,d)
> 
> We use only literals in the format strings, the macro adds
> wide character prefix (L"...") to them.
> 
> Regards,
> ---
> ITAGAKI Takahiro
> NTT Open Source Software Center
> 
>


--------------------------------------------------------------------------------


> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value.
Next
From: Tom Lane
Date:
Subject: Re: Erroring out on parser conflicts