NUL between every character

[GoogleCodeExporter]

What steps will reproduce the problem?
1. load attached file
2.
3.

What is the expected output? What do you see instead?
Not the text "NUL" between every character.

IMPORTANT!!! Please answer these questions for any and ALL bug reports

What version of the product are you using? On what operating system?
0.5.15

What method of install was your version installed with (Binary/Source)?
Binary

If from source: What version of python and wxPython are you using?

Please provide any additional information below.

Original issue reported on code.google.com by heino.lengfelder@gmail.com on 25 Nov 2009 at 1:29

Attachments:

• SQLDUMPER_ERRORLOG.log

[GoogleCodeExporter]

Hi,

I did a hex dump on that file and there actually are NULL characters between 
each
character in that file so Editra is displaying it accurately.

Here is the first part of the dump:

hexdump SQLDUMPER_ERRORLOG.log 
0000000 ff fe 31 00 30 00 2f 00 33 00 31 00 2f 00 30 00
0000010 38 00 20 00 31 00 38 00 3a 00 31 00 33 00 3a 00
0000020 30 00 34 00 2c 00 20 00 45 00 52 00 52 00 4f 00
0000030 52 00 20 00 2c 00 20 00 53 00 51 00 4c 00 44 00

As you can see there are NUL's between each character byte.

Not sure what to do about this as I can see how it makes it so you can't read 
the
file very well but I don't want to have Editra change it automatically either 
since
that could lead to data loss. So I think I will have to leave it as is unless 
there
are any other ideas out there.

Cody

Original comment by CodyPrec...@gmail.com on 25 Nov 2009 at 1:47

• Changed state: Pending
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Closing as invalid

Original comment by CodyPrec...@gmail.com on 10 Dec 2009 at 3:12

• Changed state: Invalid

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I too have run into this problem, but with all UTF-16 files created with either 
Editra or TextEdit (I'm on a Mac). I 
don't 
know much about the UTF-16 format, but when I did the hexdump as you did above 
I got a similar output with 
the nul blocks, but that's with any UTF-16 file I created, including with 
TextEdit. Is UTF-16 maybe supposed to 
have this?? TextEdit continues to display the files fine.
The thing is that Editra displays the UTF-16 encoded file fine until it is 
closed then reopened. It should be able 
to reopen and properly display a file that it itself saved, unless I'm not 
opening it properly? I've done File>Reload 
with encoding...>utf_16
Also, I'm on Mac OS X 5.8, Editra 0.5.51 binary install
I just started using Editra this evening to write up some xml files and love it 
so far, thank you for creating this 
wonderful piece of freeware Mr. Precord!

Original comment by aron.zah...@gmail.com on 5 Apr 2010 at 4:41

[GoogleCodeExporter]

Question:

Were the NULL characters in the file before you saved it with Editra or after?

UTF-16 does not use NULL's between bytes, the only way I could see them getting 
there
is if Editra had some trouble opening it and though it was raw binary bytes in 
the
file and tried to load them into the buffer. When this happens though the 
buffer is
set as Read Only so that it can't be written out.

If you have a sample file and some steps that can reproduce this issue I will 
reopen
it for further investigation.

Thanks

Original comment by CodyPrec...@gmail.com on 5 Apr 2010 at 5:10

[GoogleCodeExporter]

Ok so I made a file in TextEdit containing "test", then saved it as UTF-16. The 
hexdump gave
0000000 ff fe 74 00 65 00 73 00 74 00                  
000000a
In Editra I made a new file, saved it in format: All files. The I went 
File>Reload With Encoding...>utf_16. then I 
typed "test", saved it again (looked fine here), and closed it. hexdump gave
0000000 fe ff 00 74 00 65 00 73 00 74                  
000000a
I then reopened it in Editra, and it showed the Nul's between each character.
Both files display fine in TextEdit.
I did the same procedure except with UTF-8 and it worked fine, displaying fine 
after the reopen in Editra.

Original comment by aron.zah...@gmail.com on 5 Apr 2010 at 5:34

Attachments:

• texteditUTF-16
• editraUTF-16