--- In [email protected], "brucexs" <bswit...@...> wrote:
>
> Right, I know. Unfortunatley, when I started work on PowerPro, I
did
> not know about internationalization, and now it is too late to
back
> fit it.
>
> The issue I think is that PowerPro is treating the unicode
contents
> of these files or clips as normal ascii text and trying to make
valid
> file names that way. I don't know of any easy way to fix this
issue.
>
> It might be interesting to know which binary bytes are causing
the
> error. I suspect it is because the valid file name characters are
> actually unicode, and so PowerPro cannot properly set them.
>
For Reproducing an error.
Does Chiness letter in spg's post (#34543) look properly?
; ---------------------------------------
Local invalid = "ÝÞßàáâ, ãäåæçèéêëì íîïðñò óôõö÷ø ùú ûüýþ ãäåæçèéê...
ëìíî ïðñòóôõö"
/*
; which is equivalent to
Local sString
= "Q37HVeGYLAAgALhbxoEQmIWWuoEgAPr5fXqeWCAAaV9FUUJXIACG"
sString
++= "bCAAOmpwiiAAuFvGgRCYhZYuAC4ALgC6gfr5IAB9ep5YaV9FUQAA"
Local invalid = Unicode.Decode(sString).To_Ascii()
*/
; clip error.
; Error message pops up when "All" is checked.
; If others(TEXT/RTF) checked, no error message, but, no captured
clip either.
Clip.Set(invalid)
; note error. Error message pops up.
Note.Open("", "clip")
; ---------------------------------------
