Since not only \ but also other characters that have special meaning
to compiler are used by Big5 Chinese characters. Adding an extra \
can make non-Big5 aware environment happy. I think we can get rid of
this dirty work by using UTF-8 instead of the annoying Big5 problem.
On Sun, 1 Aug 2004 01:17
The big problem is that it didn't add an extra \ in the cases I
mentioned. There were other strings that looked like:
"XXX\XX"
where X is a high-bit character. Notice there is only one backslash.
---
Zhenbang Wei
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
<[EMAIL PROTECTED]> 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 b
