On Thu, Jul 13, 2006 at 11:12:47PM +0100, David Watson wrote:
> hpodder incorrectly displays the episode name from the following feed:
> 
> http://michaelandevo.com/podcast.xml
> 
> e.g.
> Winginâ It - Show #63
> 
> which should be 
> Wingin' It - Show #63

Hi David,

I will attach that feed to this message so that we can have a static
file in the BTS to talk about.

In that feed on line 53, I see that they are not in fact using the
apostrophe character (0x27).

Under a hex dump, we can see the following examples:

00000200  45 76 6f 27 73 20 57 69  6e 67 69 6e 27 20 49 74  |Evo's Wingin' It|
000008f0  45 76 6f 27 73 20 57 69  6e 67 69 6e 27 20 49 74  |Evo's Wingin' It|

Notice how both of these examples use the apostrophe character
correctly -- 0x27.

00001000  0a 09 09 3c 74 69 74 6c  65 3e 57 69 6e 67 69 6e  |...<title>Wingin|
00001010  e2 80 99 20 49 74 20 2d  20 53 68 6f 77 20 23 36  |... It - Show #6|

Notice how this one doesn't: it uses the sequence 0xe2 0x80 0x99.  I
suspect, but don't know for sure, that this is a Unicode sequence for
a particular character -- perhaps what Word inserts when it uses
slanted "single quotes".

> this is also reflected in the id3 tags written to the file.

You said that you see "Winginâ" when you look at the file.  If I open
the feed XML file in Emacs, on line 53, I see "Winginâ€™ It -
Show #68".

I tried adding the podcast to hpodder myself, then ran hpodder lseps.
On my terminal, I saw the same thing you did.  If I redirected the output
from hpodder lseps to a file, then opened that file with Emacs, I saw
the same three-character sequence that occured in the XML file
originally.

It seems to me, therefore, that hpodder is operating correctly and
passing on data as it is received.

What behavior would you seek in this situation?

Thanks,

-- 
John Goerzen
Author, Foundations of Python Network Programming
http://www.amazon.com/exec/obidos/tg/detail/-/1590593715

Reply via email to