Date: Sun, 01 Feb 2009 08:47:56 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: "Jason C. Wells" <jcw@highperformance.net> Cc: chat@freebsd.org Subject: Re: UTF as Filename Extension Message-ID: <873aeyd55v.fsf@kobe.laptop> In-Reply-To: <4984C5E5.1070505@highperformance.net> (Jason C. Wells's message of "Sat, 31 Jan 2009 13:43:01 -0800") References: <4984C5E5.1070505@highperformance.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 31 Jan 2009 13:43:01 -0800, "Jason C. Wells" <jcw@highperformance.net> wrote: > Here is a simple discussion that is probably more complex than I'd like > it to be. Is there any way to enforce a UTF-8 encoding of a file, > perhaps by filename extension? Could such an encoding solve cross > platform line break incompatibility? I find that Emacs makes a very good job of 'hiding' these annoying details from me. In both X11 and `no window' sessions of the editor, the coding-system auto-detection of new buffers works 99% of the time and I can specify it manually when it doesn't. Using the filename for automated guesses of what the content may be is probably not going to work so well. Windows has tried doing it, and see all the ATTACHMENT.JPG.EXE trojans they got as a result :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?873aeyd55v.fsf>