<html><body bgcolor="#FFFFFF"><div><br></div><blockquote type="cite"><div><div><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; ">> 128 limit<br><br>I haven't read the code enough yet to verify that but you are probably right<br></span></blockquote><div><br></div>I was not right :), that call is incremental.</div></div></blockquote><div><br></div>I looked for that aspect too but missed it. :(<br><div><br></div><br><blockquote type="cite"><div><div><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; "> > ignoring everything over 16_FF<br><br>Probably that is the responsibility/claim of the caller of GetChars.<br>If you want to be correct in the face of non-ASCII, you are probably obligated to call GetWideChars.<br>Perhaps raising an exception would be reasonable to signal the loss of data. Or something.<br>There is HasWideChars for you to check.<br></span></blockquote><div><br></div></div><div><br><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; "><br>There is no encoding implied remember.<br>This isn't UTF8 data.</span></blockquote></div><div><br></div><div>It is not, but probably only way to solve this without exception is to make UTF8 "official" 8bit encoding :)</div><div><br></div></div></blockquote><br><div>I'm torn on that. We'd have to consider ramifications like Text.Length vs buffer size requirements/expectations.</div><div><br></div><div><br></div><div>Is TEXT & its use abstracted enough to have been widened? Should we put it back and introduce WIDETEXT? That is essentially what C and C++ do. They are inconvenient for existing code but simple predictable make sense. Contrast with weird hybrid systems like Perl & Python for which I just can't get through the documentation and understand and predict how they work..</div><div><br></div><div><br></div><div>Java is in-between but also simple & predictable -- there being no narrow option other than array of byte, which is reasonable.</div><div><br></div><div><br></div><div> - Jay</div></body></html>