GNOME Bugzilla – Bug 497641
Files with a broken encoding crash bluefish (cvs) or confuse (stable) it
Last modified: 2008-01-12 08:25:29 UTC
Hi, I got this report: https://bugs.launchpad.net/ubuntu/+source/bluefish/+bug/163307 When I tested the attached file with the current bluefish-unstable version, bf crashed for me. The backtrace is attached. When I tested the attached files with the current stable tree, bf opened the file, but the user complains about the way and bf doesn't let the user specify a different encoding via Document > Character Encoding. Saving then of course complains too.
Created attachment 99252 [details] Backtrace Backtrace for the current bluefish-unstable.
in the file->open dialog you can specify the encoding when opening files. It opens fine on my machine with 8859-2 as encoding. How did it crash on your box? Can you reproduce it?
b.t.w. your explanation about the encoding in preferences was not entirely correct. The encoding is tried in several steps: 1) encoding set in a <meta> tag is searched and tried 2) the last encoding set in this session (or project) is tried. If you manually set the encoding of a document in file->open this sets the session encoding too. 3) the encoding for new files (as set in the preferences) is tried 4) UTF-8 is tried 5) any encoding available in the preferences is tried
(In reply to comment #2) > in the file->open dialog you can specify the encoding when opening files. It > opens fine on my machine with 8859-2 as encoding. How did it crash on your box? > Can you reproduce it? Yes. I normally use UTF-8 there as fallback. With this value, bf-unstable crashes and bf stable opens the file as ISO-8859-1 (not ISO-8859-2) for me.
Hm? Yesterday bf-unstable crashed reprodibly for me. Today it opens the file without a crash.
the bug is fixed, it is unrelated to encoding. it was a classical programming error that I should have seen earlier...