From owner-freebsd-chat@FreeBSD.ORG  Sat Jan 31 22:00:42 2009
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
Delivered-To: chat@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 42C83106570C
	for <chat@freebsd.org>; Sat, 31 Jan 2009 22:00:42 +0000 (UTC)
	(envelope-from jcw@highperformance.net)
Received: from mx1.highperformance.net (s6.stradamotorsports.com
	[64.81.163.124])
	by mx1.freebsd.org (Postfix) with ESMTP id 179B28FC0A
	for <chat@freebsd.org>; Sat, 31 Jan 2009 22:00:41 +0000 (UTC)
	(envelope-from jcw@highperformance.net)
Received: from [192.168.1.17] ([192.168.1.17])
	by mx1.highperformance.net (8.14.3/8.14.3) with ESMTP id n0VLh1vI088219
	for <chat@freebsd.org>; Sat, 31 Jan 2009 13:43:01 -0800 (PST)
	(envelope-from jcw@highperformance.net)
Message-ID: <4984C5E5.1070505@highperformance.net>
Date: Sat, 31 Jan 2009 13:43:01 -0800
From: "Jason C. Wells" <jcw@highperformance.net>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: chat@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.4 required=2.5 tests=ALL_TRUSTED autolearn=failed
	version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
	s4.stradamotorsports.com
Cc: 
Subject: UTF as Filename Extension
X-BeenThere: freebsd-chat@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Non technical items related to the community
	<freebsd-chat.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chat>
List-Post: <mailto:freebsd-chat@freebsd.org>
List-Help: <mailto:freebsd-chat-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2009 22:00:43 -0000

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?

A wiki article states that such capability exists, but the tools aren't 
there yet.  I suppose the easiest question to answer is, should users 
like me worry about it much?

I use unformatted text more and more for documents, saving the 
formatting step for late in the writing process.  I like my text to be 
variable width and to reflow along paragraph demarcations.  New line 
compatibility issues are annoying.  Fixing them is not what I want to 
spend time doing.

Regards,
Jason