Hi Alan. Some misunderstandings (sorry).
--- In [email protected], "entropyreduction" <[EMAIL PROTECTED]> wrote: > See docs: First param of inputdialog must be ascii string, not unicode > string. Right. I only tried this, because unicode.inputdialog with ASCII strings crashes immediately on my machine (also the encodeUnicode.powerpro script). > Do you want to be able to have unicode var=title? Not really. See above. > But, there is an error in inputdialog that causes crash on second run. > Easy fix. As I said: I get the crash on first run when I use ASCII strings as parameters. > I only did handles for unicode-strings. Thought so. > I can add handles for files, > quite easy. Would be nice to have, I think. > If you want releaseall fixed, inputdialog corrected and file handles, > you can probably have them instantly-ish. > Or you can wait a bit while I mess around with UTF-8 files and > Mutlibyte ANSI. UTF-8 is actually the thing that interests me about unicode. It is ASCII-compatible. Here's a page that probably explains it better than I could: http://www.personal.uni-jena.de/~pfk/mpp/sv8/utf8.html There is also a windows API function shown which seems to do what I need: Convert a locale string to UTF-8. 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/
