You are here: PSPad forum > English discussion forum > PSPad 5.0 future
Goto Page: Previous1 2 3 4 5 6 7 Next
Posted by: Freeman | Date: 2017-03-03 20:13 | IP: IP Logged
pspad:PSPad 5 (066)
Great work, Jan!
My wishes:
* CP866 in menu by default (probably 855 is not needed, but ask your Bulgarian/Serbian users).
* URL/Quoted prinatable/base64 to/from ANSI with UTF-8 autodetection. Encoding to UTF-8 also.
Posted by: pspad | Date: 2017-03-05 11:09 | IP: IP Logged
Freeman:* URL/Quoted prinatable/base64 to/from ANSI with UTF-8 autodetection. Encoding to UTF-8 also.
Hello. Can you be more specific? All those conversion are made in open file.
Mabe name of menu item "ANSI to anything" and "anything to ANSI" is wrong, cause all sources (text in file before you) is in unicode already.
Maybe correct name is "Text to Base64" e.t.c.
I will check this functionality if it works correctly.
Posted by: Ilya | Date: 2017-03-05 15:05 | IP: IP Logged
Highlighter Tcl/tk.
Shift+Ctrl+A toggles comments. The problem - a new line is added. Each Shift+Ctrl+A adds a line.
Sometimes (can't catch it) the last character of the commented line is going on the beginning of the added line.
Posted by: pspad | Date: 2017-03-05 16:07 | IP: IP Logged
Ilya:Highlighter Tcl/tk.
Shift+Ctrl+A toggles comments. The problem - a new line is added. Each Shift+Ctrl+A adds a line.Sometimes (can't catch it) the last character of the commented line is going on the beginning of the added line.
I know it and it's already fixed. Thank you for report
Posted by: pspad | Date: 2017-03-06 11:28 | IP: IP Logged
Which encoding choose to store PSPad files?
Localization files, scripts, clips, e.t.c.
I vote for UTF-8.
Localization files are now stored in UTF-8
Scripts can be in UTF-8 as well
In this case we need to store files in different folders from PSPad 4.x to prevent mix of ANSI and UNICODE encoding.
Do you have any idea how to choose name for new folders? Any prefix or suffix?
Good news is I have scripting in version 5
Posted by: Andreas | Date: 2017-03-06 11:42 | IP: IP Logged
Yes please UTF-8. This works around the world.
Why do we need to have old files from PSPad 4 in PSPad 5? We can easily save our own files to UTF-8 if necessary at all. Or am I wrong?
Nice, will try the scripting soon.
Posted by: Stefan | Date: 2017-03-06 11:53 | IP: IP Logged
pspad:...
In this case we need to store files in different folders from PSPad 4.x to prevent mix of ANSI and UNICODE encoding.Do you have any idea how to choose name for new folders? Any prefix or suffix?
Perhaps
\Lang
\Language
"Lang" as now for the current ANSI,
and "Language" for the new UNICODE?
Quote:Good news is I have scripting in version 5
Woo hoo!
--
Stefan (pleased user since 1722)
Do you know you can spend Jan a beer? (click here)
Inofficial FAQs + Infos + Special Settings
Posted by: Freeman | Date: 2017-03-06 12:24 | IP: IP Logged
pspad:I vote for UTF-8.
When possibility to pass encoding exists, I vote for any encoding, passing with data, as in HTTP. With UTF-8, Russian texts become ~1.5 times longer, in bytes. The same thing with other languages use Cyrillic.
Posted by: pspad | Date: 2017-03-06 12:26 | IP: IP Logged
Stefan:Perhaps\Lang
\Language"Lang" as now for the current ANSI,
and "Language" for the new UNICODE?
This is exactly how I did it now.
Why we need separate folders?
1. for testers
2. for users who will reinstall old version with new one.
We can rename folders
Quote:Context -> Clips
Convert -> Convertors
Lang -> Language
Script -> Scripting
or add prefix
Quote:U_Context
U_Convert
U_Lang
U_Script
or suffix
Quote:Context_U
Convert_U
Lang_U
Script_U
Posted by: Freeman | Date: 2017-03-06 12:40 | IP: IP Logged
pspad:Freeman:* URL/Quoted prinatable/base64 to/from ANSI with UTF-8 autodetection. Encoding to UTF-8 also.Hello. Can you be more specific?
For example, Russian word "файл" can be percent-encoded as:
* %F4%E0%E9%EB -- ANSI (1251), by PSPad
* %D1%84%D0%B0%D0%B9%D0%BB -- UTF-8, by most of browsers.
Both encodings are correct, but depend on server or site features/encoding. In real practice UTF-8 is used by most sites, ANSI is rarely needed, but needed sometimes.
Same thing with decoding.
* 9ODp6w== decoding as "файл" in ANSI.
* 0YTQsNC50Ls= is also "файл", but in UTF-8. PSPad decodes it as "файл"
Both base64 cases are correct, both should be decoded properly, second one with UTF-8 autodetection, as when opening files.
Editor PSPad - freeware editor, © 2001 - 2024 Jan Fiala, Hosted by Webhosting TOJEONO.CZ, design by WebDesign PAY & SOFT, code Petr Dvořák, Privacy policy and GDPR