Notepad++ v7.9.5 released

Nazar Grynko 0

Update
I have reinstalled the app without saving my custom setting on uninstall and it worked.
Thanks!

xagaba

I have a weird problem with some Unicode files with Chinese chars not loaded or recognized properly.
If I load the file in windows notepad and save it, the Notepad++ shows and recognize perfectly…
I leave a little test file in my server for you to test…
Test file

Alan Kilborn

@xagaba said in Notepad++ v7.9.5 released:

I have a weird problem with some Unicode files with Chinese chars not loaded or recognized properly.

Suggest looking at THIS and seeing if that has any impact.

guy038

Hello, @xagaba, @alan-kilborn and All,

I downloaded your Test.txt file and, after numerous tests, I’ve got the solution ! I even think that I’m going to create a GitHub issue in order to improve the N++ auto-detection of the right encoding ;-))

But first, to correctly answer you, I need three additional pieces of information :

When you’ve just opened the Test.txt file, what encoding do you see, in the right part of the status bar ?
Could your provide the Debug Info... information of your Notepad++ configuration ( Menu option ? > Debug Info... )
Could you also specifiy what is your current N++ font ?
- In Settings > Style Configurator > Global styles > Global override > Font Style > Font Name ( IF the Enable global font option is tiched )
OR
- In Settings > Style Configurator > Global styles > Default Style > Font Style > Font Name ( IF the Enable global font option is NOT tiched )

TIA

Best Regards,

guy038

xagaba

@Alan-Kilborn

Sorry, I try it but no luck with that…
Seems to me that it’s not a rendering issue here…
Thanks anyway !

xagaba

@guy038 said in Notepad++ v7.9.5 released:

When you’ve just opened the Test.txt file, what encoding do you see, in the right part of the status bar ?

Unix (LF) ANSI

Could your provide the Debug Info… information of your Notepad++ configuration ( Menu option ? > Debug Info… )

Notepad++ v7.9.5 (64-bit)
Build time : Mar 21 2021 - 02:13:17
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS Name : Windows 10 Pro (64-bit)
OS Version : 2009
OS Build : 19042.928
Current ANSI codepage : 1252
Plugins : DSpellCheck.dll mimeTools.dll NppConverter.dll NppExport.dll

Could you also specifiy what is your current N++ font ?

Let me know if you need anything else…

Regards !

guy038

Hi, @xagaba, @alan-kilborn and All,

Thanks ! No, I don’t need anything else. I just wanted to know your current font and your default ANSI codepage :-)

After downloading your file, I realized that it contains some parts with 1 null byte, EVERY 2 bytes. So, I supposed that it was, initially, a Windows Unicode encoded file !

However, in that case, looking at its contents, with an hexadecimal editor, an invisible Byte Order Mark ( the two bytes FF and FE ) should had been at its very beginning ! As these two bytes are absent, just follow this quick method to get the things right :

Open your file Test.txt in Notepad++ ( 174 bytes )
Move to the very beginning of the file ( Ctrl + Home )
Hold down the ALT key and hit, successively, the 0, 2, 5 and 5 keys of the numeric keypad
Release the Alt key

=> The ÿ character, of ANSI code \xFF, should have been inserted at the very beginning

Again :

Hold down the ALT key and hit, successively, the 0, 2, 5 and 4 keys of the numeric keypad
Release the Alt key

=> The þ character, of ANSI code \xFE, should have been inserted, right after the ÿ character

Save the modifications of the Test.txt file ( Ctrl + S )

As specified above, the insertion of the ÿþ string at the very beginning of file, so the two bytes \xFF\xFE, represents the Byte Order Mark ( BOM ) of an UCS-2 LE BOM / UTF-16 LE encoded file, named Unicode in the Microsoft terminology !

Reload your Test.txt file ( Ctrl + R )

Et voilà, done ;-))

This time, the ÿþ string, added at the very beginning of your file is correctly detected as the invisible BOM.So, Notepad++ re-opens this file with the right encoding, displayed at the bottom of the status bar ( UCS-2 LE BOM )

Note that all the characters and, specifically, all the Chinese characters, are normally displayed, if you’re using, for instance, a current monospaced font, like Courier New, Consolas or Lucida Console !

Note also that your file has Unix line-endings ( LF = \x0a)

Best regards,

guy038

guy038

Hi, @xagaba, @alan-kilborn and All,

Below, a view of your file, with the correct appearance !

May be, it’s worth to add that I installed, on my old XP SP3 laptop, since a long time, some services to see Far Eastern languages !

Here is the English/American translation of this French windows, after using Start > Parameters > Regional and language options entry :

Title : Regional and language options

TABS : Regional options | Languages | Advanced Options

Text services and input languages

To view or change the languages and methods you can use to enter text, click on Details
                                                                                                  | Details |

Support for additional languages

Most languages are installed by default. To install additional languages select the corresponding options below.

  | |   Install files for languages with complex scripts and writing from right to left (this includes Thai)

  |x|   Install the files for the Far Eastern languages

So, may be you’ll correctly see the #./Localization/Description and #./Localization/Name headers but you won’t be able to get the correct displaying of all the Chinese characters : !?

BR

guy038

xagaba

Thanks for the explanation.
When the BOM it’s present I can see the Chinese chars correctly.

My problem was that windows notepad loads the file fine (also without the BOM) and notepad++ doesn’t.

Ayansh Vardhan

i install notepad and then something went wrong

Ayansh Vardhan

@xagaba please help me fix the notpad++ cause something went wrong

PeterJones

@Ayansh-Vardhan ,

Please start a new topic, since this topic is about problems specific to v7.9.5.

When you create the topic, please describe your problem in detail, giving us enough to understand what is wrong.