Hi everyone. I have created a large text file which is essentially a concatenated bunch of emails. I simply selected the emails in Evolution with shift-click, and went "Save As". I can open the file fine in nano, or I can cat it without problems. It has a lot of useless crap markup, but that's to be expected. However, I'm completely unable to open it in gedit; I just get the error that gedit couldn't determine the correct character encoding. I've tried manually selecting all the various UTF and Western encodings without luck; the only one that will open at all is UTF-16, which renders the file as a lot of Japanese-looking text. Any ideas? Regards, Bnonn
There are another editors in X such as nedit, xcoral, cooledit and code-browser which are worthwhile. 010| Open source: Diversity & transparency | Live free or die 001| Just about everything is a farce. | 111| Sources ? ... Who is this guy ? | http://www.unix.org/unix/ _______________________________________________________ Yahoo! Acesso Gr�tis - Internet r�pida e gr�tis. Instale o discador agora! http://br.acesso.yahoo.com
On Thu, Feb 23, 2006 at 12:05:33AM +1300, Bnonn wrote:
Hi everyone. I have created a large text file which is essentially a concatenated bunch of emails. I simply selected the emails in Evolution with shift-click, and went "Save As".
I can open the file fine in nano, or I can cat it without problems. It has a lot of useless crap markup, but that's to be expected. However, I'm completely unable to open it in gedit; I just get the error that gedit couldn't determine the correct character encoding. I've tried manually selecting all the various UTF and Western encodings without luck; the only one that will open at all is UTF-16, which renders the file as a lot of Japanese-looking text.
Any ideas?
Hi, I suspect what's happened is that you've got messages in different encodings, so there are different parts of the file that are invalid no matter which encoding you try to choose. And gedit doesn't seem to have an option to leave a file unconverted (often called "raw" or simply "no" encoding), which is pretty lame, so I suspect you'll have to use a different editor. Ignore all the people telling you to use anything based on vi - it's a horrible editor if you don't already know how to use it. (Ditto for emacs, although possibly not quite so bad). John
Ignore all the people telling you to use anything based on vi - it's a horrible editor if you don't already know how to use it. (Ditto for emacs, although possibly not quite so bad).
Sorry, its like a reflex... someone says "text editor", i say "use vim!" Although you'd have to imagine it more like "text edi...", "VIM!" (possibly with half eaten biscuit flying from my mouth) :-P -- Cameron
John R. McPherson said:
Ignore all the people telling you to use anything based on vi - it's a horrible editor if you don't already know how to use it. (Ditto for emacs, although possibly not quite so bad).
But if you know how to use vi, it's a brilliant editor. It's not hard to learn enough commands to use gvim, since it has menus and mouse support. Regards, Jon
Ignore all the people telling you to use anything based on vi - it's a horrible editor if you don't already know how to use it. (Ditto for emacs, although possibly not quite so bad).
Ed is the standard text editor. Ed is generous enough to flag errors, yet prudent enough not to overwhelm the novice with verbosity. The experienced user will often know whats wrong.
I suspect what's happened is that you've got messages in different encodings, so there are different parts of the file that are invalid no matter which encoding you try to choose.
And gedit doesn't seem to have an option to leave a file unconverted (often called "raw" or simply "no" encoding), which is pretty lame, so I suspect you'll have to use a different editor.
Ignore all the people telling you to use anything based on vi - it's a horrible editor if you don't already know how to use it. (Ditto for emacs, although possibly not quite so bad).
Aha, +1 informative. Thank you. I might file the lack of ability to use raw in gedit as a bug...it's silly. And yah, I stay away from vim and emacs; I just don't have the inclination to learn them, since I never have had any need. I'll try some alternative text editors. Regards, Bnonn
And yah, I stay away from vim and emacs; I just don't have the inclination to learn them, since I never have had any need. I'll try some alternative text editors.
Check out GNOME 2.14 (due soon), as I know gedit has gotten a lot of love. Remember everyone, "change editor" isn't the correct answer to "there is a bug in my editor". :) Craig
Check out GNOME 2.14 (due soon), as I know gedit has gotten a lot of love.
Remember everyone, "change editor" isn't the correct answer to "there is a bug in my editor". :)
Yeah, I saw that (: I can't wait aksherly. And I would never give up my beloved gedit just because it can't open funkily encoded files. I'd just need an alternative for those cases.
* Craig Box <craig(a)dubculture.co.nz> [2006-02-23 05:00]:
Remember everyone, "change editor" isn't the correct answer to "there is a bug in my editor". :)
That’s true. If the editor is Vim, then “change editor” is the wrong answer. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
participants (8)
-
A. Pagaltzis -
Bnonn -
Camster342 -
Craig Box -
Gilmar Mendes -
John R. McPherson -
Jonathan Purvis -
Perry Lorier