Bug#701081: debian-policy: mandate an encoding for filenames in binary packages
Le Sat, Mar 16, 2013 at 01:11:37PM +0100, Julien Cristau a écrit :
> On Sat, Mar 9, 2013 at 10:51:45 +0900, Charles Plessy wrote:
> > I think that it emerges from the discussion that there are good uses of
> > Unicode, and that somebody would need to step up and ensure that a dozen of
> > packages are corrected if we were to restrict further the encoding of file
> > names. Moreover, there seems to be a good self-discipline, and Unicode is
> > not used in paths that are central on non-Unicode systems.
> > Given that currently the Policy does not mention anything about file names, I
> > think that it would be fair to fill the gap by documenting the use of Unicode
> > as current practice and recommend ASCII for most cases. This does not preculde
> > further restrictions if needed. I volunteer to contact the maintainer of
> > lletters-media and ooohg, the only packages with non-Unicode file names.
> > I attached a slightly updated patch. I have not added that the policy is for
> > 'the files that have been created after the binary package is "Installed"',
> > because I think that it is clear throughrough chapter 10 that "installed files"
> > means this. Nevertheless, it would be nice to have such a definition black on
> > white somewhere else, to be discussed in another thread.
> You say unicode everywhere but you seem to actually mean utf-8...
Indeed I meant UTF-8, sorry for being confusing.
The patch to the Policy already mentions UTF-8:
+ <sec id="filenames">
+ <heading>File names</heading>
+ The name of the files and directories installed by binary packages
+ must be encoded in UTF-8 and should be restricted to ASCII when they
+ can be represented in that character set.
I have just opened #703177 on ooohg, and figured out that there is already
#659345 for lletters-media.
Have a nice week-end,
Tsurumi, Kanagawa, Japan