PSPad unicode 5.0.7 (659) English

Hello PGomersall,

Unfortunatly, i use x86 version.
Script support doesn't work in x64 right ?

PGomersall:

Greg,
It works (copy\paste to Excel - I used what you had in your images) for me in this (659 x64) version.
My text type was set to ANSI and document type was txt. Not sure if these settings have effect.

Correct Greg.
Verified this is an issue on 32 bit with standard paste. If you use Paste Special > Text it works, at least for me.
I think this may be a known issue from previous build.

Greg:

Hello ! ^^

Good news is the back to previous backup works perfectly fine.
I had to use it when i saw it is impossible to Paste to MS Excel. I didn't test it to another program.

Confirmed. Editor component authors changed form of paste to clipboard and it broke Excel pasting of TAB delimited text. I must investigave what is going on.

I will use way how old editor component handled clipboard instead of the new OLE handling.
I tested it and it works fine with Excel.

pspad:

I will use way how old editor component handled clipboard instead of the new OLE handling.
I tested it and it works fine with Excel.

PGomersall, Jan, Thank you guys!

Jan, why does the x64 not handle script support please ? I'm sorry i didn't get it.

Greg:

Jan, why does the x64 not handle script support please ? I'm sorry i didn't get it.

MS doesn't supports Windows Scripting Host for 64b. You need to make workarrounds in 64b application. Some parts of scripting works, some not yet. It really time consuming, but I hope I will make it works at final

Edited 1 time(s). Last edit at 2021-07-02 16:24 by pspad.

pspad:

Greg:

Jan, why does the x64 not handle script support please ? I'm sorry i didn't get it.

MS doesn't supports Windows Scripting Host for 64b. You need to make workarrounds in 64b application. Some parts of scripting works, some not yet. It really time consuming, but I hope I will make it works at final

Thanks again.

I just a saw this : " File ... contains broken UTF-8 encoding. Do you want to open it ?
Problem is it is an OEM 850 file...

It makes me think about another question... If i'm correct i understa,d it's not possible to detect an open accordingly an OEM (850) file and it causes me a lot of troubles when i modifi them before seing characters with accent are messed up...

Does someone now a confortable solution for this ?

Edited 1 time(s). Last edit at 2021-07-02 16:37 by Greg.

Greg:

Thanks again.

I just a saw this : " File ... contains broken UTF-8 encoding. Do you want to open it ?
Problem is it is an OEM 850 file...

It makes me think about another question... If i'm correct i understa,d it's not possible to detect an open accordingly an OEM (850) file and it causes me a lot of troubles when i modifi them before seing characters with accent are messed up...

Does someone now a confortable solution for this ?

Possible cause:
you have active Remeber file state option, this will save information include last use encoding. You save your file as UTF-8 previously. Now file was created again in OEM encoding.

I don't think so, that OEM encoding was incorrectly detected from OEM file.

You can any file reopen in correct encoding if PSPad detects is wrong - switch encoding and use Reopen file (Ctrl+R)

pspad:

Greg:

Thanks again.

I just a saw this : " File ... contains broken UTF-8 encoding. Do you want to open it ?
Problem is it is an OEM 850 file...

It makes me think about another question... If i'm correct i understa,d it's not possible to detect an open accordingly an OEM (850) file and it causes me a lot of troubles when i modifi them before seing characters with accent are messed up...

Does someone now a confortable solution for this ?

Possible cause:
you have active Remeber file state option, this will save information include last use encoding. You save your file as UTF-8 previously. Now file was created again in OEM encoding.

I don't think so, that OEM encoding was incorrectly detected from OEM file.

You can any file reopen in correct encoding if PSPad detects is wrong - switch encoding and use Reopen file (Ctrl+R)

That's what i already do but if i had it wrong for a moment, i have to change manually because characters are corrupted.

Tonight i have a probleme i had long ago...
I'm working on scripts for Postgres and i see asian characters... So i clic "OEM" and CTRL+R.

I let you look at the result... and i didn't push tonight so it's lost. I go to bed :\

Edited 1 time(s). Last edit at 2021-07-02 22:02 by Greg.

I don't know how to reproduce it unfortunatemy but it's the second time when i confirme "UNDO with real tabs after autoindent" :(