<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I agree with this. This way we are compatible with Unices (majority of systems we use) but we also have straight way to W functions of Windows API, similar to method I used but with distinctive presumption of input encoding.<div><br><div><div>On Jun 25, 2012, at 10:29 PM, Rodney M. Bates wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">This is not necessarily a proposal, but FWIW:<br><br>hen working on my altered cm3 TEXT implementations, I put every relevant thing I could find into<br>a state that should allow M3 WIDECHAR to be 32-bit, with only one or two declarations<br>changed. I think Pickles might need some attention to cope with this, however. We would<br>want them to not only handle 32-bit WIDECHAR, but be able to read older pickle files that<br>used 16-bits.</span></blockquote></div><br></div></body></html>