Amp is displayed as & in EPG (1 Viewer)

[grubi]

The title says it all.
The symbol & in EPG data and recordings is displayed as &
So Lenßen&Partner looks like Lenßen&Partner

grubi.

 

[Marcusb]

yep, it's been posted a few times.
Strange, as I think it affects everyone, but there is not much comment on this issue.

The & is just the HTML code for the & sign, just like > is > (unicode).
This is how they are stored in the EPG XML file, but MP should be translating them back.
I guerss maybe it doesn't effect people who use the DTV grab, just the webepg grab.

 

[grubi]

Yes possibly only users of WebEPG are affected (wich I use also) as & is the HTML entity for &.
So maybe has to be fixed inside the WebEPG plugin.

grubi.

 

[grubi]

Just took a quick look at the sources.
All the conversion is done by calling the method "ConvertHTMLToAnsi" so the problem is not inside the plugin itself. I think to track this further down it is necessary to debug that part to see what exactly happens. As there are so many HTML entities there is the chance that processing & is simply missing.

grubi.

 

[Marcusb]

the whole amp thing annoys me in HTML. The purpose of these characters is to enable the display of characters that a probram can't natively support (I know I worded this badly) but the & is actually in the code so why have a substitue for something that is needed for the substitute?

Thanks for taking the time to check it out Grubi

 

[grubi]

the whole amp thing annoys me in HTML. The purpose of these characters is to enable the display of characters that a probram can't natively support (I know I worded this badly) but the & is actually in the code so why have a substitue for something that is needed for the substitute?

Thanks for taking the time to check it out Grubi

The & character is the escape character for all html entities (every entity begins with it) so
to distinguish it, it also has to be an entity itself.

grubi.

 

[grubi]

I had a more detailed look at the sources and found the problem.

The method "ConvertHTMLToAnsi" is no longer called at all. The lines in question have been commented out, and this is the reason why & is not substituted. I don't know why the developer did this. Maybe previously the tvguide.xml file contained HTML entities and this has changed.

However the current code uses the "XmlReader.ReadInnerXml" method which does not convert entities and is only useful if called on nodes containing subnodes. Changing this call to "XmlReader.ReadString" instead would solve the problem.

Maybe a dev could change the following lines and substitute "ReadInnerXml" by "ReadString"

case "title": if (nodeTitle == null) nodeTitle = xmlProg.ReadInnerXml(); else xmlProg.Skip(); break;
case "category": if (nodeCategory == null) nodeCategory = xmlProg.ReadInnerXml(); else xmlProg.Skip(); break;
case "desc": if (nodeDescription == null) nodeDescription = xmlProg.ReadInnerXml(); else xmlProg.Skip(); break;
case "sub-title": if (nodeEpisode == null) nodeEpisode = xmlProg.ReadInnerXml(); else xmlProg.Skip(); break;

 

[grubi]

Marcusb

OK. I made the changes in question and tested it. Works as it should.
I have a rebuild of the plugin based on SVN 15673 attached for testing.
Would be nice if you post back your results.

If any dev could incorporate this into the official release it would be nice.
Source is also included in the zip archive.

grubi.

 

[Marcusb]

sorry grubi, I'm in Mexico at the moment and about to head off to Peru to hike through the Amazon. I won't be back home to Melbourne until early October.

I really appreciate you looking into it, but I can't help for a while, sorry. Surely this is effecting others too?

 

[grubi]

sorry grubi, I'm in Mexico at the moment and about to head off to Peru to hike through the Amazon. I won't be back home to Melbourne until early October.

I really appreciate you looking into it, but I can't help for a while, sorry. Surely this is effecting others too?

No problem.
Everyone is affected as XML entities are not converted to the representing chars. The question is how often you will have those characters like &<> in EPG data. In Germany you will find them quite often.

I will ask a dev if he could incorporate my changes. Should not take longer than 5 minutes.

grubi.