Patrice Dumas wrote:
Given that stabilized utf8 support is quite young in TeX, I
wouldn't say
the same. In any case latin1 is upstream choice, in that case. So it
is expected to have to do something for the encoding. My opinion is that
it is better to leave the document as-is and set the editor encoding,
but if the packager wants to convert the document and modify the commands
related with encoding such that the document is still valid, why not.
It's pretty easy to fix in the specfile: just recode the file and sed the
inputenc definition. I don't really see this as a valid excuse to ignore
our packaging guidelines there.
Kevin Kofler