Content-Type: multipart/alternative; boundary="-1476983308-453696690-1346421249=:59465" ---1476983308-453696690-1346421249=:59465 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi all=0AI've just been trying to build plplot with unicode under windows. = I noticed quite a few warnings with wingcc.c that didn't appear in the non-= unicode build. A quick check showed that this was due to passing char* stri= ngs to unicode functions. Although these are only warnings I checked and th= ey cause corruption of the OS displayed strings (window title, menu items e= tc) so=A0I've just been through and changed all apropriate chars to TCHARs = and added _T() macros as needed, there was also a conversion of one string = from UTF-8 to unicode and a #undef to add before a #define.=0A=A0=0AI've te= sted compilation and build both with and without unicode selected and check= ed with example x00 and all now seems fine.=0A=A0=0APatch attached=0A=A0=0A= Phil ---1476983308-453696690-1346421249=:59465 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all
I've just = been trying to build plplot with unicode under windows. I noticed quite a f= ew warnings with wingcc.c that didn't appear in the non-unicode build. A qu= ick check showed that this was due to passing char* strings to unicode func= tions. Although these are only warnings I checked and they cause corruption= of the OS displayed strings (window title, menu items etc) so I've ju= st been through and changed all apropriate chars to TCHARs and added _T() m= acros as needed, there was also a conversion of one string from UTF-8 to un= icode and a #undef to add before a #define.
 
I've= tested compilation and build both with and without unicode selected and ch= ecked with example x00 and all now seems fine.
 
P= atch attached
 
Phil
---1476983308-453696690-1346421249=:59465--