R
Richard Bond
Hi,
I have a vb ActiveX control in a frame by itself. It itself contains a third
party graphing control (Graphics Server). In short, a javascript function
passes an HTML table object to the activeX control, it loops through the
cells and charts it. There is also an option to export to powerpoint via
automation. This all miraculously works in English. It also works in
Taiwanese on a Taiwanese PC (running engish windows 98??!!!).
However on my english PCs (winXP/2000/98) although the HTML table renders
correctly in Taiwanese in "Frame A" (as I dynamically assigned the
response.codepage and response.character set to the html Page attributes.
The chart text (different frame) renders ????? instead of the correct
Chinese characters. However when I use the export to powerpoint method, all
the text is displayed as chinese. I have tried changing the locale to
chinese before browsing to the webpage/installing the activeX, but I get the
same problem.
what should I be setting in the activeX control to fix this?
regards,
Richard
I have a vb ActiveX control in a frame by itself. It itself contains a third
party graphing control (Graphics Server). In short, a javascript function
passes an HTML table object to the activeX control, it loops through the
cells and charts it. There is also an option to export to powerpoint via
automation. This all miraculously works in English. It also works in
Taiwanese on a Taiwanese PC (running engish windows 98??!!!).
However on my english PCs (winXP/2000/98) although the HTML table renders
correctly in Taiwanese in "Frame A" (as I dynamically assigned the
response.codepage and response.character set to the html Page attributes.
The chart text (different frame) renders ????? instead of the correct
Chinese characters. However when I use the export to powerpoint method, all
the text is displayed as chinese. I have tried changing the locale to
chinese before browsing to the webpage/installing the activeX, but I get the
same problem.
what should I be setting in the activeX control to fix this?
regards,
Richard