--- In [email protected], "swzoh" <[EMAIL PROTECTED]> wrote:
> You may use 1 for OEMCP, and 2 for MACCP.
Good to know.
> In my case, ACP and OEMCP are the same, 949, and MACCP is 10003.
ACP and OEMCP differ for me (1252 and 850), haven't tried MACCP.
> ByteBlock's main purpose is to be used as LPWSTR or alike which can
> have embedded nulls, I suppose.
Yes. I'll keep that in mind.
> I think you mean code-points (range of 0 ~ 10FFFF currently).
10400 is
> outside the so-called BMP (range of 0 ~ FFFF), so it's represented
by
> 4 bytes in UTF-16, even so in UTF-8. The code-points in BMP are
> represented by 2 bytes in UTF-16, whereas 1/2/3 bytes in UTF-8.
Yes. As I said, rather unlikely to get chars higher than FFFF.
> The current default size of PP's variable is 272 bytes, including
> terminating null. Then increased by 16 bytes when needed. You can
> experiment it using undocumented function Win.DumpVar("var_name").
So,
> maybe in ByteBlock case:
> 263 = 272 - 6 - 4 + 1
> where 6 is the byteblock's overhead, and 4 may be terminating null
in
> unicode string case and among them 1 may be counted again as the
> (plain) terminating null character.
> It's purely my guess, BTW.
Could be. Will experiment with this.
Thanks again for the infos.
Mockey
Attention: PowerPro's Web site has moved: http://www.ppro.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/power-pro/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
