300145 - RSS 2.0 UTF-8 feed titles and content not displayed correctly

Status: RESOLVED WORKSFORME

(MailNews Core :: Feed Reader, defect)

Description

[Manuel Lemos]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 SUSE/1.0.4-1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 SUSE/1.0.4-1

Thunderbird shows empty titles and oddly formatted content for this RSS 2.0
feed. Thunderbird says the content encoding is ISO-8859-1 despite the
content-type header of the feed says UTF-8. 

Reproducible: Always

Steps to Reproduce:
1. Add the feed http://www.pro-php.com/podcast.php making it show only the
article summary
2.
3.

Actual Results:  
The screenshot shows some odd headers and HTML instead of the item description
or content as requested.

Expected Results:  
The feed items with the actual titles and the item summaries

Comment 1

[Manuel Lemos]

Attachment: Screenshot of the problem

Comment 2

[Manuel Lemos]

Thunderbird version is 1.0.2 (20050322) from SuSE RPMs for SuSE Linux 9.0

Comment 3

[Magnus Melin [:mkmelin]]

Seeing the problem (with version 1.0+ (20050708)). However, the problem seems to
be with the feed. The xml is invalid (some char encoding issue). See
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.pro-php.com%2Fpodcast.php

Comment 4

[Mike Cowperthwaite]

The current version of the feed is still invalid per the feed validator, but not 
about "some char encoding issue".  Loading the feed as described, I am seeing 
the following with TB 1.5a1-0904:

The feed itself declares:
  <?xml version="1.0" encoding="ISO-8859-1"?>
(and that's how it's served, as well)

For the articles that have the MP3 attachments, the text/html part has:
  Content-Type: text/html; charset=NaN
You can see this by selecting the article and   View | Source
The "NaN" is definitely bogus; I've opened bug 307380 about this.

Thunderbird does not show *any* encoding selected in the Encoding menu -- which 
is a known bug for invalid charsets.

All the current articles seem to have only ASCII in the headers, so I can't 
check the original symptom.  Articles do not look anything like what's seen in 
attachment 188715 [details] -- instead, I see the expected text -- so I suspect the feed 
has been fixed.

Manuel Lemos, please state whether you are seeing this same behavior.  If so, 
please mark the bug   Resolved | WorksForMe.

If you're still getting new articles that look like the screenshot, save one of 
those articles as a .EML file and attach it to this bug.

Comment 5

[Robert Sayre]

This feed works for me on the trunk.

Comment 6

[Mike Cowperthwaite]

No response from reporter  =>  WFM