Re: [ jEdit-devel ] jEdit - file encodings

[Dale A. <da...@gr...>]

I agree with the "must open" group.  There are times I'll send a file to 
gedit or kedit because I know it'll open it regardless.  If jEdit can't 
figure it out, go with plain ascii and open it.  Odds are if jEdit can't 
figure it out, it's some sort of binary file that I just want to look 
for some plain text in anyway.

Dale


Alan Ezust wrote:
> On Mon, Apr 7, 2008 at 2:19 PM, Dalibor Petričević <dal...@is...> wrote:
>   
>>  My idea is simple, configurable list of fallback encodings is a good
>>  feature and will cover 90% of anybodys needs. But if file is encoded
>>  with something else jEdit don't recognize, DO NOT REFUSE to open file.
>>  That's it. Open it as plain 7bit ASCII displaying >127 characters as []
>>  if you ask me. But open it and DO NOT nag me with ERROR dialog?!. If I
>>  want to specify encoding prior to opening file - I will do it, but if I
>>  don't do it - pretty please open file using fallback encodings feature
>>  and if that goes to nothing open it in some (configurable?) encoding
>>  even if I end up looking squares and funy characters on screen.
>>     
>
>   
>>  Does that sounds ok?
>>     
>
> If that's an option one can switch on/off when list of fallback
> encodings fail, that would be a good thing. I think some people like
> the current scheme, and others will like yours.
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Register now and save $200. Hurry, offer ends at 11:59 p.m., 
> Monday, April 7! Use priority code J8TLD2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>