Re: Traditional Chinese translations for backend, pgsql, pg_dump and

Patch applied. Thanks.

[ Charset big5 unsupported, skipping... ]

[ Attachment, skipping... ]

[ Attachment, skipping... ]

[ Attachment, skipping... ]

[ Attachment, skipping... ]

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

I'm getting a number of errors from these files such as:

src/backend/po/zh_TW.po:64: invalid control sequence
src/backend/po/zh_TW.po:67: invalid control sequence
src/backend/po/zh_TW.po:114: invalid control sequence
src/backend/po/zh_TW.po:207: invalid control sequence
src/backend/po/zh_TW.po:252: invalid control sequence
src/backend/po/zh_TW.po: warning: PO file header missing, fuzzy, or invalid
warning: charset conversion will not work
found 6 fatal errors

Apparently, in the particular character encoding you employ backslashes
occur on occasion, such as here

"�����\ \"root\" ���� PostgreSQL ���A���C\n"
"\n"
"���A�������H�D�S�v�ϥΪ̨����ҰʥH�קK\n"
"�i�઺�t�Φw�����D�A�аѾ\���H��o\n"
"�����p�󥿽T�Ұʦ��A������T�C\n"
"\n"

However, these strings are interpreted with C escapes, and this is an
invalid string.

I don't know of a good way to fix this, since in your editing tool you
probably don't see these backslashes, instead you see the multibyte
characters they are part of. If you have Emacs, try out the PO mode.
Otherwise you might want to ask around how other users of your language
handle this. (E.g., how do you enter strings in your language in C source
code without running into hidden backslashes?)

--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter