On Tue, 2009-06-30 at 19:11 +1000, Matthew Palmer wrote: > > In section 3.3 of the documentation, the British Pound symbol is displayed > > with the U+FFFD REPLACEMENT CHARACTER rather than U+00A3 POUND SIGN. > > > > I think this is because the info file is encoded with latin1 rather than > > UTF-8. > > That certainly seems to be the case -- the pound sign is 0xA3 (with no > leading high-bit character) in the file I've just inspected here. > > I'm completely in the dark about file encodings, myself. Is it a policy > requirement that all info files be UTF-8 encoded? The only mentions of > UTF-8 I can find in the current policy are for control files and manpages. > Is there a way I can specify what encoding the info file is in? If so, is > explicitly specifying ISO-8859-1 an acceptable solution? If I do run the > info file through iconv to turn it into UTF-8, how do I respond to bug > reports from people viewing the file through ISO-8859-1 glasses?
Looking into the details, ledger.texi currently appears to correctly declare its encoding as latin1 on line 38. And that encoding does seem to be present at the end of the generated info file. So I think this is actually a bug in the info package--the info viewer needs to re-encode its output to the user's current encoding. As to how to find that encoding out: I believe you can call 'nl_langinfo (CODESET)' as is done if you run the shell command 'locale charmap'. But that's a matter for the texinfo maintainers. :) > - Matt -- Sam Morris <s...@robots.org.uk> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
