From: Dalibor P. <dal...@is...> - 2008-04-07 18:19:24
|
Original message from Matthieu Casanova, sent on 6.4.2008 12:27 > On Sun, Apr 6, 2008 at 9:10 AM, Kazutoshi Satoda <k_s...@f2...> wrote: >>> we could try all available encodings, but of course try the most >>> common encodings first ? >>> >> You can get such behavior if you put all available encodings in the >> list of fallback encodings. >> >> But I think it should not be default because of the risk of opening >> with a wrong encoding. (See my first post about the risk, saying >> "For example, if Windows-1252 is in the list, ...". After I wrote >> that, I found that ISO-8859-1 is more permissive one.) > > > That's right, but who will do that ? > Imagine a user that wants to search for a text in a folder that > contains a lot of files and subfolders, if some files cannot be opened > by jEdit because of encoding, will he want to add some encodings in > the fallback encoding list ? Probably not, he will think that jEdit > sucks. > In that case it should be automatic > > Matthieu I edit a lot of different type of files, and often have a need to peek into some files I don't know what they contain (might be a binary file and I wouldn't know until I open it), you know the situation "what is this file?" Drag it to notepad, gedit, something and see what it contains. Or the situation when you get a file from *nix with no extension, what is it? Or you simply want to quickly check, say same EXIF metadata from the .jpeg file header or .mp3 ID tag. Or you want to open some source file which has, God forbid, some UTF characters nailed in some hardcoded string but it is otherwise ISO-8859-2 plain text file with no BOM (UTF character will then look like some squares and funy chars when you open file with ISO-8859-2 encoding - I know, it is a bad programmnig but I got to edit such files) etc... I EXPECT textual editor to open whatever file I drag into it (open). And I love Jedit. But when my favourite editor refuses to open a file because IT does not know what the file is - that is just plain silly. I will decide what file encoding is but you (editor) OPEN it even if you don't know the right encoding. I don't care in what encoding, try your best and I know that you can't allways be right. It's like that. And no, I don't want to put ALL possible encodings in fallback encodings so just my TEXT EDITOR would OPEN some strange FILE! Not to mention it will NEVER open a binary file for me to peek into it and look for some strings. Cheers guys -- Dalibor Petricevic |