On Sat, Apr 06, 2013 at 08:20:15PM +0900, Charles Plessy wrote: > Le Mon, Apr 01, 2013 at 10:39:19AM -0700, Don Armstrong a écrit : > > On Fri, 29 Mar 2013, Russ Allbery wrote: > > > I think we should require UTF-8 as the character encoding for file > > > names and fix the non-UTF-8 file names in the archive currently. > > > None of the other courses of action really make any sense to me. > > > > I think we should also forbid the use of non ASCII file names in PATH > > and recommend that ASCII file names be used where possible, but I also > > agree that where ASCII cannot serve, only UTF-8 should be used. > > Hello everybody, > > Here is a somewhat clumsy proposition. > > <sec id="filenames"> > <heading>File names</heading> > > <p> > The name of the files installed by binary packages in the system > PATH > (namely <tt>/bin</tt>, <tt>/sbin</tt>, <tt>/usr/bin</tt>, > <tt>/usr/sbin</tt> and <tt>/usr/games/</tt>) must be encoded in > ASCII. > </p> > > <p> > The name of the files and directories installed by binary packages > outside the system PATH must be encoded in UTF-8 and should be > restricted to ASCII when they can be represented in that character > set. > </p> > </sec> > > > What do you think ?
I think configuration files should also be included in the first list, because the user is supposed to be able to interact dirrectly with them. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130414095803.GB1942@yellowpig
