Re: PSPad UNICODE 4.5.0 (2133) beta English

Test build - PSPad freezes problem 3rd version

Download from:
pspad.cincura.net

Please report me the last message dialog that you see before PSPad freezes (enough is the number of step you see in the dialog)

--
Jan

No, this option doesn't exist.
You can set the "Esc exit" option and "Minimize to tray" option.

I see dialog 1 and 2 and PSPad doesn't freeze any more....
Seems like you fixed it!

It works for me too
I also see dialog 1 and 2 and PSPad doesn't freeze any more....

Great job

PSPad wrote:
> PSPad search file by file. If file contains a BOM, PSPad opens it correctly and
> handle it as UNICODE. If CP can't be detected, search string is converted into CP
> you specify in the dialog.

Hi again.

Yes, I understand the situation. What I am asking for is an additional option, Codepade "ALL" which will convert the search string into every CP when searching for documents that do not have a BOM.

Let me give you an example. I have the search string, "Foo" and I try to search for it in files. None of the files have a BOM. Some use UTF-8 encoding, some ANSI (Windows) and some ISO-8859-2. In the past, PSPad magically found "Foo" in any of the documents regardless of the code page. Now I have to specify the code page manually -- and because I have different types of files, I have to either guess or try them all. IMO, This is not clear because I don't care about the encoding -- I just want to find "Foo" in all files!

boots wrote:

> Let me give you an example. I have the search string, "Foo" and
> I try to search for it in files. None of the files have a BOM.

If you search text without accent marks, you can use any non unicode Code Page.
The code page settings has influence to higher part of ASCII chart, not for you "foo"

I'm happy too
2 dialogs and no more freezes, thanks.

Download the last build 2134 if you want to have PSPad without the debug dialogs

PSPad Wrote:

> If you search text without accent marks, you can use any non unicode Code
> Page. The code page settings has influence to higher part of ASCII chart, not for
> you "foo"

Okay, maybe I can better explain it this way:

In previous versions of PSPad, if I searched for "FOO" with either ANSI (Windows) *or* ISO-8859-2 selected, it would find all instances of "FOO" in all files for both cases. With new unicode version, if I try the same test, it finds "FOO" in all files ONLY IF ISO-8859-2 is selected. If ANSI (Windows) is selected, it finds no matches. Maybe this is the desired behavior but it feels like a regression to me.

Best regards and many thanks for responding!

ops, I just see new version 2134 and I noticed that you changed to behaviour! I tested and it now works as I expected.

Thank-you!! You ROCK!!