You are here: PSPad forum > Bug report / Hlášení chyb > Old codepage autodetection behaviour

Old codepage autodetection behaviour

Goto Page: Previous1 2

#11 Re: Old codepage autodetection behaviour

Posted by: pspad | Date: 2022-01-23 15:02 | IP: IP Logged

jojo:
All of those suggestions just hinder my workflow I'm afraid. Maybe I should better explain what the most important things for me are here:

- I do not want to be warned everytime I open an ANSI file that it contains invalid UTF-8 codepoint. That just slows down my work.

In this case don't set UTF-8 as favourite

jojo:
- I do not want the codepage for those legacy ANSI files to be autodetected, as Chinese or Japanese characters don't have the same width as e.g. all characters in Windows-1252.
For me it's not a big matter if DOS ANSI characters are not decoded correctly (in my mind I can pretty much map the incorrect characters anyway), but if the formatting of tables breaks because some characters get turned into Chinese glyphs, it's rather annoying.

Open Settings in the Code page menu and uncheck all unnecessary code pages

jojo:
- All of that I want without having to manually reopen a file with a different encoding.

1) Set ANSI or 1252 as your favourite code page.
2) If you create mostly UTF-8 files, set UTF-8 as default CP for new files - in project settings, if you use project or in the program settings / Files
3) Use some accented chars in your UTF-8 no BOM files in comment to allow correct autodetection
4) If you want to improve autodetection (I aske you about it already), send me some files what are not autodetected correctly. I need to analyze what causes worng autodetection.

Options: Reply | Quote | Up ^


#12 Re: Old codepage autodetection behaviour

Posted by: jojo | Date: 2022-01-23 15:12 | IP: IP Logged

pspad:
1) Set ANSI or 1252 as your favourite code page.
2) If you create mostly UTF-8 files, set UTF-8 as default CP for new files - in project settings, if you use project or in the program settings / Files

I'm not sure what the difference between these two options is. I have set UTF-8 as the default for new files. But how can I set a favourite code page for existing files? Isn't that the exact same option?

pspad:
4) If you want to improve autodetection (I aske you about it already), send me some files what are not autodetected correctly. I need to analyze what causes worng autodetection.

I posted some links earlier: forum.pspad.com

Options: Reply | Quote | Up ^


#13 Re: Old codepage autodetection behaviour

Posted by: pspad | Date: 2022-01-23 15:19 | IP: IP Logged

Menu Code page - Ctrl+ Click or move CP1252 as the first in the Code page menu / Modify

Favourite Code page is used when UTF-8 detection failed
Code page in the project or program settings / Files is used for NEW files (I wrote it already)

Sorry for the examples, I missed it.

Related to ANSI art files, this isn't standard file. For such files I am afraid autodetection won't work.

Edited 1 time(s). Last edit at 2022-01-23 15:21 by pspad.

Options: Reply | Quote | Up ^


#14 Re: Old codepage autodetection behaviour

Posted by: jojo | Date: 2022-01-23 15:24 | IP: IP Logged

pspad:
Menu Code page - Ctrl+ Click or move CP1252 as the first in the Code page menu / Modify

Favourite Code page is used when UTF-8 detection failed

Okay, I Ctrl-Clicked on CP1252, then opened an ANSI file, and I no longer got a warning about invalid UTF-8. However, if I now create a new file it's not UTF-8, it's CP-1252! This is what I'm hinting at in my previous posts, the two settings seem to be overwriting each other, I don't know if that's intentional but I cannot get PSPad to use UTF-8 only for newly created files and silently fall back to CP-1252 if a file is not valid UTF-8. From your reply I can only deduce that this is not in fact how it's supposed to be. This is PSPad 5.0.7 (727) 32-bit, by the way.

Options: Reply | Quote | Up ^


Goto Page: Previous1 2





Editor PSPad - freeware editor, © 2001 - 2022 Jan Fiala, Hosted by Webhosting TOJEONO.CZ, design by WebDesign PAY & SOFT, code Petr Dvořák, Privacy policy and GDPR