Some characters are not displayed in RSS

Bug #354468 reported by ldsonline
4
Affects Status Importance Assigned to Milestone
Xibo
Fix Released
Medium
Dan Garner
1.0
Fix Released
Low
Dan Garner

Bug Description

First, congratulations for creating the XIBO.
The RSS does not show some characters (~ and C, for example). In English I know that does not interfere, but in other languages is a problem.

Thanks,

            Lindomar

Related branches

Revision history for this message
ldsonline (ldsonline) wrote :

Sorry...
Ç, not C.

Revision history for this message
Alex Harrington (alexharrington) wrote :

Thanks for your bug report. What is shown in place of those characters?

Xibo 1.0 series is not internationalised yet. We don't specifically support non-english languages.

The new development 1.1 series has this specifically targeted, so expect this to work properly once 1.2.0 and onwards are released.

That said, I expect Dan will have a look and see if this is an easy fix that could be included in 1.0 series clients.

Cheers

Alex

Revision history for this message
ldsonline (ldsonline) wrote :

Hi Alex,

These characters are not displayed and no other character or symbol is inserted in its place. Examples: if the word is "Leão" is showing "Leo", if the word is "caça", it displays "caa".

Cheers

Lindomar

Revision history for this message
Alex Harrington (alexharrington) wrote :

I just mentioned this to Dan.

On the client, can you find the .xml file that contains one of these RSS feeds and attach it to this bug. It'll be something like 47fwsf0w0.xml and it'll be in your clients library directory.

Cheers

Alex

Revision history for this message
Alex Harrington (alexharrington) wrote :

... and the feed URL too please.

Alex

Revision history for this message
ldsonline (ldsonline) wrote :

Ok, Alex.

The feed URL is: http://rss.terra.com.br/0,,EI1,00.xml

Here attached the XML required. Some examples of words that were incorrect displayed:

ltimas notcias : (correct = últimas notícias)
reprter: (correct = repórter)
estdio: (correct = estádio)
sustentvel: (correct = sustentável)
Poltica: (correct = Política)
Sumio: (correct = Sumiço)

Greetings!

Lindomar

Revision history for this message
Alex Harrington (alexharrington) wrote :

Thanks. Dan is going to take a quick look tonight to assess how complicated fixing this will be.

1.0.0 is likely to appear tomorrow so it might just get in the release - if it's something simple.

Cheers

Alex

Revision history for this message
Dan Garner (dangarner) wrote :

Having difficulty working out what is going on here - I just seem to be loosing these characters - even though I am encoding to UTf8. Needs a more detailed look - so am therefore targeting as a bug fix 1.0.1.

Changed in xibo:
assignee: nobody → dangarner
importance: Undecided → Medium
milestone: none → 1.0.1
status: New → Confirmed
Changed in xibo:
milestone: 1.0.1 → none
Revision history for this message
ldsonline (ldsonline) wrote :

What's the meaning of "xibo milestone: 1.0.1 → none"? The problem still exists?

Revision history for this message
Alex Harrington (alexharrington) wrote :

Hi Lindomar,

It means that we won't fix this in the 1.0 series as significant changes would be required to the client to support it.

1.0 is a stable series, which we have already stated does not support special characters well. Making large changes to the client could compromise stability of the system for those running Xibo in production environments.

Given that 1.1 will have a completely different client, it is not anticipated that it will have the same flaw.

Cheers

Alex

Revision history for this message
Alex Harrington (alexharrington) wrote :

Hi Lindomar

My mistake. I was thinking of a different bug.

If you look at the top of the page, this is still assigned to 1.0.1 in the 1.0 series so we are still hopeful to fix it, subject to it not requiring a major rework as I previously described.

If I remember correctly, Dan already had a quick look and determined that it isn't his code removing those characters, rather a .net library function, so I'm not sure how straightforward this is going to be to resolve.

Cheers

Alex

Revision history for this message
ldsonline (ldsonline) wrote :

Thanks, Alex.

Can I help you? I don't know what is the file where is the code that makes the program to communicate with the RSS (not researched about it yet) but I can take a look and consider what can be done to correct the problem.

Revision history for this message
Alex Harrington (alexharrington) wrote :

Hi

I think Dan already has a fair idea what the problem is.

As I understand it, it's roughly here:
http://bazaar.launchpad.net/~xibo-maintainers/xibo/halley/annotate/head%3A/client/dotNET/RssReader.cs#L76

You can see we use the .net builtin RSS parser to download and parse the XML in the RSS feed, and when we get it back from that function, the characters are missing.

I would strongly advise leaving it to Dan to work out, but if the mood takes you then I'm sure any patches would be appreciated.

Cheers

Alex

Revision history for this message
Dan Garner (dangarner) wrote :

The problem is actually here: http://bazaar.launchpad.net/%7Exibo-maintainers/xibo/halley/annotate/head%3A/client/dotNET/Rss.cs#L127

The StreamReader doesn't return the characters.

I don't know if it is a problem with the System.Net.WebClient or the StreamReader itself... interrogation of either object reveals the UTF8 char set - so I am a little stumped until I get some more time on it.

By all means take a look ;-)

Cheers,
Dan

Revision history for this message
ldsonline (ldsonline) wrote :

Alex/Dan,

I solved test again, this time on another computer. Unlike what happened before, (the special character was not replaced by another character) now the special characters are replaced by certain symbols. See attached xml.

http://rss.terra.com.br/0,,EI1,00.xml

Revision history for this message
pedroqn (pedronoronha) wrote :

Hi, I attached the system XIBO an excellent tool for testing digital communication has come online really great. About the bug above reaction I doing test with various sources of RSS. RSS Some sources are correct. following examples.

Big hug,
Noronha

Revision history for this message
pedroqn (pedronoronha) wrote :

Complementing the above matter which of the RSS link is posted in the language
http://www.estadao.com.br/rss/ultimas.xml country Brazil Brazilian

A big hug,
Noronha

Revision history for this message
Dan Garner (dangarner) wrote :

Noronha,

Thank you for this information - I thought the problem might be due to the RSS feeds themselves - maybe your examples will help prove this.

Cheers,
Dan

Revision history for this message
ldsonline (ldsonline) wrote :

Noronha,

Thank you very much! It seems that the problem is with the RSS fedds of www.terra.com.br, just what I decided to use, for unhappiness ... lol. I should have tested others Portuguese feeds for confirmation, but as I used the RSS Terra feeds in another programs and had no problems, I thought the fault was in Xibo.

Dan,

Disregard this "bug", now you even have time to watch Chelsea x Barcelona ...:)

Greetings,

           Lindomar

Revision history for this message
pedroqn (pedronoronha) wrote :

Hi, I'm happy to help you here is one more that works correctly in RSS Portuguese following address:

http://g1.globo.com/Rss2/0,,AS0-5598,00.xmlAS0-5598, 00.xml

Big hug,
Noronha

Revision history for this message
Dan Garner (dangarner) wrote :

I have re-visited this again while trying to wrap up 1.0.2
The Terra feeds are definitely outputting the wrong encoding with their feeds - however I did find that there were some feeds with correct encoding that Xibo didn't display.

These are now fixed in 1.0.2 (to be released shortly)

Changed in xibo:
milestone: none → 1.0.2
status: Confirmed → Fix Committed
Changed in xibo:
milestone: 1.0.2 → none
Dan Garner (dangarner)
Changed in xibo:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.