The latest version is classified as beta mainly because its documentation is not finished yet, but also because some troubles were not resolved yet. As to the stability, let me assure you that the software has been intensively tested for months already. Four types of tests verified its stability so far:
In other words, there might be errors and bugs. But the application does not crashes while using tools and it can always undo all steps. If you spot a bug, mistake or an error, please, report it. And use undo to return back to your previous text.
There is a bug in the new version, which prevents this feature from working. Unfortunatelly, this seems to be a non-trivial issue that I did not fully anticipate beforehand (you see, I do not write any language with right-to-left orientation myself). It might take some time to fix this, since I'll have to study RTL more first.
I appologize for the inconvenience. Please, stick with version 5.4.2 to retain bi-directional features for now.
There is an IME-related bug in the new version, which causes drawing problems when using IME in TED Notepad on some systems. IME is used to insert complex characters, including Chinese and Korean. Although the IME works and characters are inserted correctly, the screen is not updated and the IME displays them at wrong positions. In result, it might seem as if characters were being lost.
I appologize for the inconvenience. Please, stick with version 5.4.2 to retain reliable IME features for now.
Auto-recognition of UNICODE files is troublesome because of 畂桳栠摩琠敨映捡獴 problem, and is not currently automatically supported in TED Notepad. Only UTF-8 files are auto-recognized without BOM.
Unfortunatelly, TED Notepad allows you to save UNICODE files easily without BOM, even though it does not recognize such files correctly later on, upon loading. In order to prevent this from happening, always save UNICODE files with BOM. Note: You can check the BOM option in the Settings dialog, if you use UNICODE as default for all your files.
If you need to open UNICODE file with no BOM, click menu File » Re-open » Unicode. The file will be re-opened as UNICODE even without BOM. Note: This way you can also fix many other encoding and codepage troubles you might encounter when working with broken, foreign or invalid files.
I appologize for the inconvenience. Please, stick with version 5.4.2 to retain reliable IME features for now.
Please, file a bug report. I will try to help you out as soon as possible.