Re: initdb problem

Some characters in Big5 encoding has a / on
second byte and I think poEdit will add another / for me.
Now I think I should use UTF-8 instead of Big5.
I will send new files in minutes. Sorry for causing problems.


On Sun, 1 Aug 2004 00:48:21 -0400 (EDT), Bruce Momjian
<pgman@candle.pha.pa.us> wrote:
> 
> Ah, just the person I was looking for.  I see in the initdb po file you
> sent that the use of backslashes in the message string is causing some
> of us problems.
> 
> What are the rules for backslashes in translation files?  I particularly
> had problems with lines 199, 260, and 461 in the initdb po file because
> you had things like:
> 
>         "XXX\\n"
> 
> where XXX were high-bit characters.  Was that correct?  It caused us
> problems because it interpreted \\ as a single backslash and then
> complained because the message id and string had a different number of
> newlines.
> 
> ---------------------------------------------------------------------------
> 
> Zhenbang Wei wrote:
> > Thanks for importing these translations :-)
> 
> [ Attachment, skipping... ]
> 
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> >                http://archives.postgresql.org
> 
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman@candle.pha.pa.us               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
>