I'll check into all these. Thanks for finding.
--- In [email protected], "Sheri" <sheri...@...> wrote:
>
> Doc says, if type for default_get_set_type is numeric, it can use values in
> the range 0 to 65280. 0x2153 is 8531; but it gives the error:
> unicode.set_chars: Numeric value too big
>
> Also, error_dialog_on is documented, but the service doesn't exist.
>
> Also I couldn't seem to use ustring if created from using unicode.empty.
>
> Also, it appeared I should be able to specify the type in the brackets when
> setting only one character, but then I get position argument errors.
>
> Maybe I'm doing something wrong?
>
> Thanks,
> Sheri
>
> win.debug(unicode.version) ;;.71
> ;unicode.error_dialog_on ;;documented but doesn't exist?
> unicode.set_base(1)
> unicode.default_get_set_type("numeric")
> ;local ustring=unicode.empty(5) ;;ustring not unusable?
> local ustring=unicode.new(" ") ;;5 spaces
> ustring[1]=0x00BC
> ustring[2]=0x0020
> ustring[3]=0x2153 <--unicode.set_chars: Numeric value too big
> ustring[4]=0x00A0
> ustring[5]=0x2154
> quit
>
> ustring[1,"n"]=0x00BC
> ustring[2,"n"]=0x0020 <--unicode.set_char:position args out of range
> ustring[3,"n"]=0x2153
> ustring[4,"n"]=0x00A0
> ustring[5,"n"]=0x2154
>
