Re: [Po4a-devel]Encoding options

> - if it's not valid UTF8, refuse to process until being given what it is > For translations: > - if not specified, suppose it's the same than the one in translated part > of the po file There is a problem I did not think about before, few English man pages contain non-ASCII characters, like euro-test in Debian. PO files have then to be UTF-8 encoded, and generated man pages will also be UTF-8 encoded which is not the expected result, at least in Debian. The easy solution is to use escaped sequences (see groff_char(7)) instead of ISO-8859-1 characters, and hope that a similar solution is always available. Then documentation should clearly state which encoding can be used for original documents, depending on their format.