I tried to edit a file that has 2-byte characters (Unicode), and for each character, the screen shows the character, then a highlighted "NULL". I tried all of the different formats from the "Format" menu, but nothing worked. Is there a configuration or plugin that addresses this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did this and was able to see the file correctly. However, these files are generally READ-ONLY on my system, and there are a lot of them, so I have to play with temporary files, etc. What I really need is to have NP++ recognize a file with NULL bytes between each text byte, as a Unicode file. Is there a way for me to get at the signature recognization logic?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The file I'm looking at is a log file created by a BREW application. Each character is actually 2 bytes (Unicode?).
Here's what the HexEditor sees:
30 00 38 00 2e 00 30 00 39 00 .... etc.
Hope that helps ... Andy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do following:
- open your log file
- create an empty file and select in menu 'Format' USC2-LE encoding
- switch here to HEX-Edit (now only 2 bytes are visible [fffe] (BOM))
- switch back to your log file and select the complete text
- copy into clipboard
- switch to HEX-Edit file back and paste here at the end of the two bytes your text
- disable HEX-Edit
Now your text should be readable.
Regards
Jens
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you. Now I understand. The file needs the FF FE bytes to indicate it's format. However, I was not successful following your detailed steps. When I got to the part where I selected all in my UNICODE file, then pasted into the Hex Edit window, nothing got pasted. I tried pasting into the generic Notepad supplied with XP, and nothing got pasted. It looks like I can't copy into the clipboard!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used Hex Edit to insert FFEE at the start of my file, but NP++ still read it in as an ASCII file as before. Is there a way to force UC-LE? Could I write a plug in that either inserts the FFEE or just forces UC-LE mode? What about auto-preview? Will I have to write something to make it work with my UNICODE files? I have lots of these files, so I don't want to do lots of manual operations just to see the data.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to edit a file that has 2-byte characters (Unicode), and for each character, the screen shows the character, then a highlighted "NULL". I tried all of the different formats from the "Format" menu, but nothing worked. Is there a configuration or plugin that addresses this?
I did this and was able to see the file correctly. However, these files are generally READ-ONLY on my system, and there are a lot of them, so I have to play with temporary files, etc. What I really need is to have NP++ recognize a file with NULL bytes between each text byte, as a Unicode file. Is there a way for me to get at the signature recognization logic?
What do you mean by:
> and for each character, the screen shows the character
something like an HEX Edit? There is a plugin available.
In addition: Be sure that the file has the correct BOM.
The file I'm looking at is a log file created by a BREW application. Each character is actually 2 bytes (Unicode?).
Here's what the HexEditor sees:
30 00 38 00 2e 00 30 00 39 00 .... etc.
Hope that helps ... Andy
Hello,
this is in USC2-LE encoding.
Do following:
- open your log file
- create an empty file and select in menu 'Format' USC2-LE encoding
- switch here to HEX-Edit (now only 2 bytes are visible [fffe] (BOM))
- switch back to your log file and select the complete text
- copy into clipboard
- switch to HEX-Edit file back and paste here at the end of the two bytes your text
- disable HEX-Edit
Now your text should be readable.
Regards
Jens
Thank you. Now I understand. The file needs the FF FE bytes to indicate it's format. However, I was not successful following your detailed steps. When I got to the part where I selected all in my UNICODE file, then pasted into the Hex Edit window, nothing got pasted. I tried pasting into the generic Notepad supplied with XP, and nothing got pasted. It looks like I can't copy into the clipboard!
I used Hex Edit to insert FFEE at the start of my file, but NP++ still read it in as an ASCII file as before. Is there a way to force UC-LE? Could I write a plug in that either inserts the FFEE or just forces UC-LE mode? What about auto-preview? Will I have to write something to make it work with my UNICODE files? I have lots of these files, so I don't want to do lots of manual operations just to see the data.
For USC encoding it should be FF FE or FF EF but not FF EE!