Bug 71993
| Summary: | Spurious "A" characters in release notes title in install | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Public Beta | Reporter: | Telsa Gwynne <hobbit> |
| Component: | redhat-release | Assignee: | Tim Powers <timp> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | null | CC: | katzj, notting, tammy.c.fox, twaugh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-08-22 05:36:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 67217 | ||
|
Description
Telsa Gwynne
2002-08-20 16:33:23 UTC
Yep, I've seen this as well. I'm copying Jeremy and Tammy, maybe they have some clue as to what's happening. Tim It doesn't look like the A character is in the HTML file. Maybe there is a bug in the way anaconda renders it? I'm changing the component to anaconda. I think that the problem is that the copyright symbol as included isn't a valid UTF-8 character and it really should be using the © entity instead. Ideas from the docbook gallery on how to actually get this to occur? :) For the weird symbols lower down, it looks like we're getting output with the bullet symbol + paragraphs as opposed to an unordered list. 0x00A9 (which is what it is) displays fine here. I think the problem is the conversion from HTML to text---if you ask for UTF-8, you get UTF-8. Our RELEASE-NOTES.txt displays fine on a UTF-8 terminal here, but looks awful as ASCII. Why aren't we using ASCII, at least for English versions? Okay, html appears to be viewing properly with current trees. We still need to decide what we want to do about the text versions. We should probably just do the text as some sort of native encoding. Fixed in next build |