Description of problem: The changelog of this package (in the .spec file) has content not in utf-8 format. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The ChangeLog has 7 years of history. It was never assumed to be UTF-8 or even to be in a single encoding. What leads you to believe it would be that way ? I hardly see that as a bug, rather an historical fact. Daniel
Why not convert it to utf-8, in vi you can do ":w ++enc=utf-8" to get it changed over.
You're assuming a single encoding in the file. Suppose I do this, someone else commit with an accent -> 2 encoding in the files and then it's unrecoverable automatically. Sounds more dangerous than useful. If text files had metadata indicating their encoding like XML files this would work, but this is not the case, the tools used to edit them can't guess the encoding, so you have no garantee of maintainability of that property. I think you must drop your UTF-8 assumption when file format don't have metadata indicating their encoding. This just doesn't work. Daniel
I think we will stay with the status-quo upstream, sorry :-) Daniel