Closed TomOne closed 8 years ago
Notepad2-mod is just a fork. These things should be asked upstream.
Thanks for your fast reply.
It seems that the development of Notepad2 isn’t really active at the moment: the latest version is a beta from October 2012 and there’s no possibility to open an issue, only an abandoned mailing list. But I’m going to try to contact the developer anyway.
My main problem is that Notepad2 does not have any public repository which makes things hard.
That's why I insist on taking the upstream issues to the Notepad2 developer first.
My main problem is that Notepad2 does not have any public repository which makes things hard.
Is that because he doesn’t use a VCS? Has anybody ever ever asked him to create a repository? If not, I could do that.
I had asked him like in 2009 about that, but he didn't want to use a VCS...
I had asked him like in 2009 about that, but he didn't want to use a VCS...
could be time to ping him again. in 2009, Github wasn't the de-facto public VCS it is today; a lot changes in 5 years.
Well I was already using Google Code back then when I asked him to use it.
Anyway, feel free to ping Florian about this. Atm the patches are randomly on top of the source and if a new version is out, I'm pretty sure things will get messy.
:thumbsup:
I noticed that some Scintilla-based text editors like Notepad2, Notepad++ and also notepad2-mod (but not SciTE) use the term ANSI incorrectly.
ANSI is a wrong term to describe either the Windows-1252 code page or the default Windows code page on the operating system, e.g. Windows-1253 for Greek.
ANSI for this meaning was a term introduced by Microsoft, but they accepted that it was incorrect and now it’s officially called “Windows code pages”, see https://en.wikipedia.org/wiki/Windows_code_page#ANSI_code_page. Therefore the term ANSI should no longer be used.
I highly suggest to rename ANSI in notepad2-mod with the correct term, e.g.: “Windows Code Pages”, “Windows Codepages”, “Windows CP” or something similar. SciTE calls it “Code Page Property”, which is not optimal in my opinion, but even better than the incorrect ANSI term.
I think term accuracy is very important, especially when it comes to character encodings.
Even better would be if the actual code page would be displayed in the statusbar and in the menu where currently is displayed ANSI: e.g. Windows-1252, Windows-1251 or Windows-1253. This would reduce the confusion about this topic once and for all times and it’s more accurate.
Geany – an editor which handles character encodings very well – does this too.