-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Thanks for your input, xcin do have pinyin input but pinyin and character > relation is not in there. For example I cut an paste a chinese char > sentance > into a program, it will generate pinyin output instead of input pinyin > output > GB or Big5. I need a directionary type database to complete this task. > Unihan.txt > in unicode.org help but I'm not sure I can use that to create an > application > with it.
erm, do you mean that sometimes the same char has different pronounciations? Or what? you can of course use the xcin input table as a database, because every chinese char has the pinyin writing in this table. if you want to differ between certain situations when you have to use which pronounciation, then of course you should look on the following chars and have a little dictionary included that decides which pronounciation to use. I think a simple perl script should fit your needs in this case. Cheers Arne - -- Arne Goetje <[EMAIL PROTECTED]> (Spam catcher. Address might change in future!) PGP/GnuPG key: 1024D/685D1E8C Fingerprint: 2056 F6B7 DEA8 B478 311F 1C34 6E9F D06E 685D 1E8C Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+pNNybp/QbmhdHowRAhP4AKDAGnh57nDurNnSf2lkPbR8mh6cDACgs3I5 lZT1DAsbJIHkjHDsFvibweM= =6W5l -----END PGP SIGNATURE-----
