How to debug vb6 richtextbox not displaying unicode (chinese) correctly

I have a simple vb6 editor type application that has rich text as the editor page. It allows users to enter data into a file and store it in a file which will save all text in RTF stored as CDATA in xml.

When you download a file, it will read it from xml and download rtf back. We allow Unicode editing, but my problem is that I have a user who is using Windows XP and they have some problems reading Chinese characters. They show up like gibberish on their computer.

It renders perfectly in both mine and a colleague. I have already verified that they have the appropriate regional language and settings on their system. The installation files for the East Asian language have already been verified. And they can see Chinese words on websites and even type them.

I feel like I am missing something, but I am at a loss on what to check next? Any ideas on what I could check or check next?

mine is bad for poor description of skills, if something is not clear, just ask me. Thank you. ~ Steve

0


source to share


3 answers


This is strange. Try to confirm your user has the same version of RICHTXT32.OCX?



0


source


Maybe there is a problem with the font?

Try using a font that supports Unicode characters (Arial Unicode). Or try going to a site with Chinese characters and pasting it into a richtextbox, saving it to a file, and trying to load it from a file.



It works?

0


source


Well, they should, because I packaged the app in an installer install package. and for the fonts, it is blue sun and I have already checked with users that they have blue sun fonts under windows / fonts.

Btw I already updated that the data is actually stored in xml under CDATA, although the rtf part is kept as is.

okie seems to be the solution, although I don't know why. in my msi setup file I have included the riched.dll file, so when I installed it, the DLL fires and spins my chinese character in the richtext control.

but when I repackage to exclude this dll file and reinstall it with this setting it seems to work now ...

0


source







All Articles