That sounds quite good to me :-) Will there be any possibility for the user to reload the file using another code page in case PSPad "guessed" the wrong encoding?
There is a typo in the code page menue of your linked preliminary version. If you choose "UTF16LE (1251)" you will save the file using Big Endian byte order (where CP 1251 actually belongs to). Same for the BE menu item. FWIW It seems that the issue with Surrogates in file names (that I reported in January) was automatically resolved with version 5 :-)) Thanks for your efforts to continuously improve PSPad! Steffen -- <http://forum.pspad.com/read.php?2,67953,68038> PSPad freeware editor http://www.pspad.com
