Re: Traditional Chinese translations for backend, pgsql,
От | Peter Eisentraut |
---|---|
Тема | Re: Traditional Chinese translations for backend, pgsql, |
Дата | |
Msg-id | Pine.LNX.4.30.0110052328410.654-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: Traditional Chinese translations for backend, pgsql, pg_dump and (Bruce Momjian <pgman@candle.pha.pa.us>) |
Список | pgsql-patches |
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
В списке pgsql-patches по дате отправления: