[GuidelinesChange] UTF8 filenames

[Simo Sorce]

On Fri, 2007-04-13 at 12:05 +0200, Matthias Saou wrote:
> Callum Lerwick wrote :
> 
> > On Wed, 2007-04-11 at 11:33 +0200, Matthias Saou wrote:
> > > Nicolas Mailhot wrote :
> > > 
> > > > Le mercredi 11 avril 2007 à 00:29 +0200, Matthias Clasen a écrit :
> > > > 
> > > > > US-ASCII is a meaningless term. There simply is no 8-bit ASCII 
> > > > 
> > > > Sure but ASCII is frequently abused nevertheless. And human lazyness
> > > > will "help" people choose the abusive interpretation.
> > > 
> > > How about referring to "plain ASCII" in the guideline?
> > 
> > Why has no one mentioned the most obvious solution. Refer to it as
> > "7-bit ASCII". It has the word "ASCII" in it for ease of understanding,
> > and further stresses that we mean 7 bits, not 8. It may technically be
> > redundant, but that's pretty much the point.
> 
> In the very first reply to the thread, Nicolas suggested just that, and
> it's what started the discussion :-)
> 
> Nicolas : "Shouldn't this be clarified as 7-bit ASCII ?"
> 
> Others : ASCII is necessarily 7-bit!!
> 
> ...
> 
> Which brought me to suggest "plain ASCII", as "plain" suggests "no
> extensions", but doesn't go into any technical details, and it's a
> terminology I'm quite sure I already came across a few times.

As said before, just tell people to do "man ascii".
There is all you need to understand which characters are in the ASCII
set.

Simo.