I accidentally found a little issue in pspad regarding the file encoding (I'm using build 2349 on Windows XP SP3):
* Create a new file of any type * Go to the Format menu and select "UTF-16 LE" to convert it to unicode * now open any ANSI file, e.g. the pspad.ini or create a new file using the "New" menu in order to use an existing template. PSPad will treat the lastly opened or newly created ANSI file as if it was a utf-16 encoded file and only show a pile of asian characters (funny, but a little bit difficult to read when you in fact want to work on a C++ source file... :-D). The only way to get it back to normal behaviour is to select "ANSI" in the Format menu and to reopen the second file. Now this is really not a big problem since pspad does not crash and can be easily reset to normal behaviour, but I would consider it more intuitive if PSPad always defaults to ANSI encoding when it can't figure out the real encoding of a file being opened or when creating a new one instead of using the last encoding selected in the Format menu, which seems to be the current behaviour. It would be fine if you could think of changing this with the next build. P.S.: Thanks for this great piece of software which I and my colleagues use daily, Jan, and keep up the good work! -- <http://forum.pspad.com/read.php?6,49621,49763> PSPad freeware editor http://www.pspad.com
