Bug 71993 - Spurious "A" characters in release notes title in install
Summary: Spurious "A" characters in release notes title in install
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-release
Version: null
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Powers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 67217
TreeView+ depends on / blocked
 
Reported: 2002-08-20 16:33 UTC by Telsa Gwynne
Modified: 2008-05-01 15:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-08-22 05:36:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Telsa Gwynne 2002-08-20 16:33:23 UTC
Description of Problem:

graphical install of 'null'. Hit the 'release notes' button.

The second line of the release notes box thrown up says copyrightA(c),
where the (c) is the © symbol and the A is a capital A with
a hat on it. 

This A-hat symbol recurs further down, seemingly in front of list items
in the RAID section of the notes, and in front of list items in the section
about Unicode, GNOME, gcc, java compiler... actually as I go down this
list it looks like all but that first one are list items within list
items.

Comment 1 Tim Powers 2002-08-20 16:35:31 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

Comment 2 Tammy Fox 2002-08-20 16:45:52 UTC
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.

Comment 3 Jeremy Katz 2002-08-21 05:47:36 UTC
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.

Comment 4 Tim Waugh 2002-08-21 07:06:49 UTC
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?

Comment 5 Jeremy Katz 2002-08-22 05:21:59 UTC
Okay, html appears to be viewing properly with current trees.  We still need to
decide what we want to do about the text versions.

Comment 6 Bill Nottingham 2002-08-22 05:36:38 UTC
We should probably just do the text as some sort of native encoding.

Comment 7 Matt Wilson 2002-08-23 22:51:08 UTC
Fixed in next build



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