Bug 159580 - non utf-8 changelog
non utf-8 changelog
Product: Fedora
Classification: Fedora
Component: libxml2 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Veillard
Depends On:
  Show dependency treegraph
Reported: 2005-06-05 02:14 EDT by Florian La Roche
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-21 12:42:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Florian La Roche 2005-06-05 02:14:27 EDT
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:
Actual results:

Expected results:

Additional info:
Comment 1 Daniel Veillard 2005-06-05 04:31:08 EDT
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.

Comment 2 Florian La Roche 2005-06-09 06:29:30 EDT
Why not convert it to utf-8, in vi you can do ":w ++enc=utf-8" to get it
changed over.
Comment 3 Daniel Veillard 2005-06-09 06:57:50 EDT
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
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.

Comment 4 Daniel Veillard 2005-10-21 12:42:09 EDT
I think we will stay with the status-quo upstream, sorry :-)


Note You need to log in before you can comment on or make changes to this bug.