On Feb 25, 2005, at 10:15 AM, Daniel Macks wrote:
On Fri, Feb 25, 2005 at 08:33:04AM -0500, Daniel Johnson wrote:
Is there a policy about what encoding to use for .info files?
They are supposed to be "plain text files" in the traditional Unix
sense. As such, I don't think there's is any issue about
On Fri, Feb 25, 2005 at 08:33:04AM -0500, Daniel Johnson wrote:
> Is there a policy about what encoding to use for .info files?
They are supposed to be "plain text files" in the traditional Unix
sense. As such, I don't think there's is any issue about encoding.
The validator emits a warning if a .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Johnson wrote:
|
| I couldn't find anything in the Packaging Manual about this. Perhaps a
| good policy would be to require all .info files to use UTF-8 and
| document this?
|
As far as I am aware, any package not using plain old ascii is in viol
Daniel Johnson wrote:
I couldn't find anything in the Packaging Manual about this. Perhaps a
good policy would be to require all .info files to use UTF-8 and
document this?
I would vote for 7-bit ASCII, if possible. Everything else gives
trouble. Just look at the package database and try to find
Is there a policy about what encoding to use for .info files? The fink
tool (or specifically perl 5.8.x) and online package database seem to
expect Unicode while FinkCommander assumes MacRoman. There are two
files, gtktalog.info and recode.info, that use MacRoman in the
Maintainer field. Thus t
