On 3/31/07, Christian Perrier <bubulle@debian.org> wrote:
> > Apparently, you forgot the attachment, I'm afraid..?;-)
> >
> Oh, sorry, here comes the PO file. 8-)
OK, got it.
However, are you sure that this file is UTF-8 encoded as the PO file
header says?
Actually, the file I sent is encoded in GBK. It's the first time I translate PO file under MS Windows whose default keyboard-coding-system is Chinese GBK. But I did check it using `msgfmt -v -v -v' before submitting, and msgfmt complained nothing. Weird... My fault again. 8-(
It seems it probably uses one of the encodings used in the past for
Chinese, like BIG5 or GB....however, I'm not competent enough in these
things to really know which one is used.
There is some ways to guess the encoding of Chinese text files. The most reliable one is try to read it using differente candidate encodings in text editor. But, iconv does this work perfectly as well. I always try to convert the encoding of text file from one to another, like `$ iconf -f gbk -t utf8 <
README.gbk > README.utf8'.
If iconv failed to do the job. The most probably reason is that a wrong source encoding is specified. If the conversion completes without warning, we got it! Although it's also an e
xhaustive method, it may help in some occasions.
Thanks.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGDedH1OXtrMAUPS0RAi5SAKCESBERjrMQrrQe/7vhn/W+BbUQTwCfUwj0
MXNxrk6dtqHw65Mi1MB9VuI=
=AEou
-----END PGP SIGNATURE-----