435870 - Decide on the feed for Firefox 2.0.0.x, Persian (fa)

Status: RESOLVED FIXED

(Mozilla Localizations :: fa / Persian, defect)

Description

[(no longer active)]

spinoff from bug #390141 comment 43.

Please read that bug for a history of the feed selection for Persian Fx-2.0.

Comment 1

[Axel Hecht [:Pike]]

Adding a bit of context right here:

> > current list of RSS readers is default
> > LB: parseek
> 
> I need to check the rss url here too.

Ok, we can use http://news.parseek.com/rss/ .  I keep talking to site
maintainers to make better RSS support (html header alternate definitions,
etc).

Also we can use http://news.parseek.com/ as the livebookmark's original site.

The feed validator is grumpy,
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fnews.parseek.com%2Frss%2F.
Could we evangelize to get these fixed? It likely breaks the feed sniffing code
in Firefox 3.

Guess it's about time to fork the feed into a separate bug.

Comment 2

[Behnam Esfahbod [:zwnj]]

I sent an email to our contact, Alireza, to let him know about the feed problem.  I'll update here on responses.

Comment 3

[(no longer active)]

Based on communications with Mr. Alireza Shirazi from the Parseek project, their feed now validates.  There are three recommendations for them to implement in their feed, which should be done in a few days.

So, to sum up, the feed URL would be: <http://news.parseek.com/rss/>, the website URL would be <http://news.parseek.com/>, and we have permission from them to use their feed in Firefox.

Is this enough to close this bug?

Comment 4

[Mic Berman]

thanks, we'll need to still make the server side change. axel, can we do this in this bug?

Comment 5

[Axel Hecht [:Pike]]

We should only block the fx release bugs by this one.

I'm still puzzled why the feed doesn't trigger our feed view. And the pubTimes are off, right now, it's sending an entriy with
<pubDate>Fri, 30 May 2008 13:33:36 GMT</pubDate>, but it's 12:46 GMT.

I bet it's using localtime and just claims to be GMT.

I tried to figure out why the feedparser doesn't like this, but failed so far.

Comment 6

[(no longer active)]

I've not been able to figure that out as well.  The feed looks valid now, except for some glitches.  Could it be because of the content type the server is using to deliver the feed (text/xml IIRC)?

Comment 7

[Behnam Esfahbod [:zwnj]]

(In reply to comment #5)
> I bet it's using localtime and just claims to be GMT.

It's a common problem in some windows-hosts Iranian sites... We will ask them
to fix it too.  Probably the best way to fix is using +0330 or +0430. (hell,
windows xp has a lot of problem with IRDT/IRST too.)

(In reply to comment #6)
> I've not been able to figure that out as well.  The feed looks valid now,
> except for some glitches.  Could it be because of the content type the server
> is using to deliver the feed (text/xml IIRC)?

Have you got any reply from Alireza?  I got no email, and I don't see any change in Feed Validator results.

Comment 8

[(no longer active)]

(In reply to comment #7)
> Have you got any reply from Alireza?  I got no email, and I don't see any
> change in Feed Validator results.

Nope, nothing.  

I think I saw an improvement in feed validator results earlier, around the time I filed this bug, but I can't remember what it was.  Anyway, the feed is now valid, even though it doesn't comply with all recommendations.

Comment 9

[Mic Berman]

are we currently blocking on release due to this issue? just trying to get current status. thanks

Comment 10

[(no longer active)]

This bug is resolved.  It was filed to make a decision on the news headlines feed for Firefox, and this decision has been made.