I think this problem to be complex....

FormatMessage of windows cannot consider the encoding of the database. However, I should try the solution now. It is necessary to clear the problem. Multi character-code exists together in message and log. It doesn't consider the data base encoding that the user intended....

The user in multi-byte country can try this.

That is, it is likely to become it in this manner.(Japanese)

Therefore, I hope for treatment that replaces these messages with English that is neutrality.

Hiroshi Saito

Attachment: FormatMessage_patch
Description: Binary data

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to