-
> >
> > > Does Chiness letter in spg's post (#34543) look properly?
I am not sure what these posts are aiming at. Here is the situation
as I understand it.
1. PowerPro does not understand Unicode, in general. The Windows
system knows PowerPro is a non-Unicode text program.
2. For both notes and clips, PowerPro attempts to build a valid file
name from the text in the note/on the clipboard.
3. It first asks the system for the text on the clipboard or in the
note's edit box (a Windows-system control). The system will return a
set of bytes which PowerPro interprets as an ASCII string.
4. PowerPro replaces any character with hex value <0x20 as well as
any of the non-allowed file characters:
< > : " / \ | ? *
It assumes normal ASCII codes are used for these characters.
5. It allows any other character to be part of the file name. It
then tries to open a file with the resulting string of text as the
file name. This seems to cause an error with some characters, but not
all.
Now the official rules for filenames are (from the MS site):
--------start of rules
"Use almost any character in the current code page for a name,
including Unicode characters and characters in the extended character
set (128255), except for the following:
* The following reserved characters are not allowed:
< > : " / \ | ? *
* Characters whose integer representations are in the range from
zero through 31 are not allowed.
* Any other character that the target file system does not allow."
----- end of rules
So somehow the rules that PowerPro uses and the above rules, when
applied on the Unicode system being tested, are not compatible. But I
don't know exactly how they are not compatible.
