Re: PSPad unicode 5.5.1 (815) English

The last update of PSPad is appx. 8 months old. Yesterday I came across the "Chinese characters issue" again.

When can we expect an update and especially an improvement of the "Chinese characters issue"?

I am slowly work on editor engine replacement.
I hope new engine will be faster and better.

pspad:

I am slowly work on editor engine replacement.

Wow, great news!

Any screenshots from development?

One more question/request from me.

When first time opened file is 7-bit, and actual code page cannot be determined, PSPad sets it to ANSI encoding, regardless default code page setting in Options window. This behavior exists from the time I ever started to use PSPad. Is this a bug or a feature?

Now I often edit markdown files with metadata. Metadata keywords are English, so if I type or paste Russian text then, I suddenly get errors from markdown compiler because PSPad saved my page in 1251 code page while that compiler supports only UTF-8. Default code page in Options is to UTF-8 no BOM, but works only for new files created in PSPad, and keeps only when non-Latin characters entered.

When there is no possibility to detect UTF-8, e.g. file doesn't contains cyrilic encoded into UTF-8, there is no chance to recognize if file is in UTF-8

Click on the code page on the status bar (or select it in the encoding menu), switch to UTF-8 and reload (Ctrl+R).
Switch on remember file state in program settings / Files - part of information is file code page.

Put on the begin of file any comment with anything encoded in UTF-8 (e.g. few cyrilic letters) - it will ensure correct detection

pspad:

When there is no possibility to detect UTF-8, e.g. file doesn't contains cyrilic encoded into UTF-8, there is no chance to recognize if file is in UTF-8

I agree, but my thought is about different thing.

pspad:

Click on the code page on the status bar (or select it in the encoding menu)

I don't want to remember to do that every time I open new markdown files. Why just don't set default code page instead of hard-coded ANSI one, on PSPad side? I think, there is an exact line of legacy PSPad code that does that assignment.

pspad:

Put on the begin of file any comment with anything encoded in UTF-8 (e.g. few cyrilic letters) - it will ensure correct detection

This is just workaround, not bugfix. I just want to make PSPad follow its own setting in one more case – when 7-bit ASCII file loaded (in addition to new file creation). Please use code page value from the Options tab you mentioned above.

What algorithm is used for file autosave period calculation? Does PSPad start from zero when previous idle time was longer than autosave time set in Options? I think no, because sometimes PSPad overwrites files very quickly.

Ot should be reset from the last save, cause there is a timer what execute event when period is over.
If PSPad is busy, it can be little longer time. But it shouldn't be shorter than the period you set up.

Freeman:

In this version, when multiline tabs enabled and tab panel got multilined due to the number of files opened, it doesn't shrink back when files closed and just one line of tabs remained. It draws an empty line which takes space of screen height.

Still exists in build 825 (release version). Unfortunately.