In Windows Commander type file managers, the viewers,
and most other viewers, these NUL strings are are
displayed as solid square blocks.
Now, I use Total Commander Ultima Prime 3.3, an
enhanced version of the Total Commander file
manager. With this I can view most any thing. When
I view a file that has these NUL strings you
indicate, I just select the Unicode view option
that it provides and I am able to read the file.
When so read, all the NUL's are blank space.
I have not tried it, but try 'Encode in UTF-8'
in the 'Format' pulldown menu.
I do not know if this helps, but it is
informative.
BillBo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I open a log file in Notepad, and I get just text, which is great.
I open the same file in Notepad++ and I get a NUL between every character NUL0NUL8NUL6NUL2
and so on.
I know I can convert these NULs to spaces with the TextFX extension, but I would really rather just read in the file right off the bat in Notepad++.
Bear in mind, if there is no way to do this, I might, Lord forfend, have to install VIM -- and that just seems like cruel and unusual punishment.
What you indicate is normal for a Unicode file.
In Windows Commander type file managers, the viewers,
and most other viewers, these NUL strings are are
displayed as solid square blocks.
Now, I use Total Commander Ultima Prime 3.3, an
enhanced version of the Total Commander file
manager. With this I can view most any thing. When
I view a file that has these NUL strings you
indicate, I just select the Unicode view option
that it provides and I am able to read the file.
When so read, all the NUL's are blank space.
I have not tried it, but try 'Encode in UTF-8'
in the 'Format' pulldown menu.
I do not know if this helps, but it is
informative.
BillBo
You really must have done something terribly wrong, causing this punishment.
This thread might help you:
https://sourceforge.net/forum/message.php?msg_id=3977394