Description of problem: $ GET http://habrahabr.ru/blogs/hardware/82866/ | html2 2>/dev/null | 2xml | xmllint --noout - -:1: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xD7 0x3C 0x2F 0x61 ="blog-about-text hidden" id="js-blog_info"> <a href="" class="close-blog-info"> ^ -:4: parser error : PCDATA invalid Char value 20 ьтат" href="#" onclick="return Voter.vote(event, this, 'post', 'results');"> ^ -:4: parser error : PCDATA invalid Char value 19 �ские Медиа</a> <div id="about"> <span style="margin-left:4px;">© 2006 ^ Version-Release number of selected component (if applicable): $ rpm -q xml2 xml2-0.4-2.fc11.i586 How reproducible: Always
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Have it error fixed in Fedora 13?
No. This has to be fixed upstream. It is an encoding problem. I've experimented a bit, maybe this special issue can be fixed using libxml2 instead of libxml, dunno. Otoh, there have not been new releases for about 2.5 years, not sure if it's still an active project.
Contacted upstream.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I think it may be closed now as UPSTREAM. Meantime, Thomas is thee any answer from upstream developer(s)?
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
(In reply to comment #6) > I think it may be closed now as UPSTREAM. > Meantime, Thomas is thee any answer from upstream developer(s)? Sorry, forgot to report back here. Here's Dan Egnor's response from Nov 2010: "Hi! As you've probably figured out by now, I'm not really maintaining this package any more. Unfortunately, as far as I know nobody else is, either. I'm actually a little surprised that people still use it -- I figured other solutions would be more popular by now. I'd be happy to hand over ownership to any interested reasonable party, or at least to set up a public source code repository somewhere (code.google.com?) people can submit patches..."
Interestingly, upstream released a new version just a month ago, should have checked that ;) It seems to actually fix this bug.
xml2-0.5-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/xml2-0.5-1.fc14
xml2-0.5-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/xml2-0.5-1.fc15
Package xml2-0.5-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xml2-0.5-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/xml2-0.5-1.fc15 then log in and leave karma (feedback).
Thomas, thank you!
xml2-0.5-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
xml2-0.5-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.