> sure, still valid UTF-8, but it's UTF-8 for what the UTF-8 is if
> interpreted according to Latin1. I thought dpkg didn't assume anything
> at all about the encoding in control files? That it expected us-ascii
> and damn everyone who didn't follow that. Can I fix this somehow, or are
> we doomed to having several encodings in the file because we can't do
> UTF-8?
I don't think it is a workable solution to have Description-xx fields encoding on
8-bit encoding.
Could we move that out of Description-xx: lines to
generate some kind of po file?
regards,
junichi
--
[EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
