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 .info file contains characters not
part of the POSIX :ascii: class.

> 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.

Yup, 'fink validate' on those files gives:

  Warning: "maintainer" contains non-standard characters. (gtktalog.info)
  Warning: "maintainer" contains non-standard characters. (recode.info)

> Thus they show correctly in FinkCommander but not 
> anywhere else. If I change those files to UTF-8, "fink info" gives the 
> correct result. Of course, then FinkCommander is wrong. :) I came 
> across this issue because I'm working on a Cocoa program that reads 
> package info from fink, and since Cocoa assumes text is in Unicode, Bad 
> Things were happening with those two files. As in crashing. I had to 
> explicitly convert the text from MacRoman first, like FinkCommander 
> does.

...and that kind of "how do I encode this portably?" weirdness is one
of the reasons we want everything in plain-text ASCII. So the proper
solution is to not use non-ASCII chars:) I just patched those two
.info files in 10.3/unstable.

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to