Encoding handling when saving new file

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open crash_sample.txt using Notepad
2. Select all content and copy
3. Paste it on editra
4. Try to save in Editra (after select a name, Editra crash)

What is the expected output? What do you see instead?
File is saved

What version of the product are you using? On what operating system?
Editra 0.4.95 on Windows XP Professional SP2

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

Original issue reported on code.google.com by aedelato...@gmail.com on 1 Jul 2009 at 9:00

Attachments:

• crash_sample.txt

[GoogleCodeExporter]

Hello,

The issue seems to be its not able to guess the proper encoding for the text 
which
must be something different from your default encoding. Try setting your 
"Preffered
Encoding" in the Preferences dialog to the appropriate setting (utf-8 worked 
for me)
and then try your above steps and see if it functions any better.

By 'Crash' does the error reporter dialog show up with any information in it or 
does
the program just shutdown? If the former please paste the contents of the error
reporter dialog here for analysis.

Also if you have the Editra Log Window (View=>Shelf=>Editra Log) open when you 
try to
save are any error ([err]) messages shown in the window?

Thanks,

Cody

Original comment by CodyPrec...@gmail.com on 1 Jul 2009 at 8:48

• Changed state: Accepted

[GoogleCodeExporter]

Thank for your response.

You are right about bug cause but I tried changing "prefered encoding" and it 
didn't
work. Always the same error.

I wasn't able to copy logs from log window because of another bug, so I send 
you a
screenshot with all messages.

Original comment by aedelato...@gmail.com on 2 Jul 2009 at 8:00

Attachments:

• editra_bug_screenshot.JPG

[GoogleCodeExporter]

Thanks,

The other bug was caused by a missed test case after the latest clipboard
enhancements. This has been fixed already.

Will get the encoding handling fixed for save as actions before the next 
release.

To workaround in current release you can add an encoding comment to the the top 
of
the file.

basically in one of the top two lines have the following text

encoding: utf-8

utf-8 can be replaced by the desired encoding.

Thanks,

cody

p.s) fixing title to be more descriptive to the problem at hand

Original comment by CodyPrec...@gmail.com on 7 Jul 2009 at 3:31

• Changed title: Encoding handling when saving new file

[GoogleCodeExporter]

Thank you very much

Original comment by aedelato...@gmail.com on 7 Jul 2009 at 4:13

[GoogleCodeExporter]

Fixed for next release.

Original comment by CodyPrec...@gmail.com on 21 Jul 2009 at 4:42

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by CodyPrec...@gmail.com on 21 Jul 2009 at 11:18

• Changed state: Fixed