[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Recoding non-UTF-8 documentation?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason L Tibbitts III wrote:
> Is there ever a case where it's worth it to recode documentation to
> satisfy a "file-not-utf8" warning from rpmlint?  Some packages fix up
> line endings to quiet rpmlint but I'm not sure about altering the
> character encoding.
> 
> If not, then would it be reasonable to remove this warning from
> rpmlint?

I had this problem with xpilot-ng:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179818#c2

iconv fixed it up quite nice.  The less output that you get from
rpmlint, the smoother the review.  Since the fix is simple then I would
just go ahead and do the conversion.

- --Wart
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFEBG4MDeYlPfs40g8RAkOWAJ9uJhaPOei9sM1wx8t5iQF1dho8VQCdFJeM
i4iwTkKqceatxjWaKIQ8fWg=
=E+j2
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]