402032 - Firefox 3 productization, Esperanto (eo)

Status: RESOLVED INCOMPLETE

(Mozilla Localizations :: eo / Esperanto, defect)

Description

[Axel Hecht [:Pike]]

We're going to have a Esperanto localization for Firefox 2.

Eduardo, do you have any suggestions on changes to the list of search engines,
or the Feed readers? What would be a good news feed for Latvia?

Mic, any ideas on your side?

Comment 1

[Eduardo Trápani]

This would be a good news feed:

http://www.liberafolio.org/search_rss?SearchableText=&Title=&Description=&portal_type%3Alist=News+Item&portal_type%3Alist=Link&portal_type%3Alist=Document&Creator=redakcio&submit=Search&sort_on=created&sort_order=reverse&review_state=published&sort_limit:int=20

There are a couple of search engines that should be erased/changed.  Should I attach a zip with the whole l10n/eo/browser/searchplugins?

Comment 2

[Mic Berman]

Eduardo, can you help me get a contact name/email for liberafolio so that I can email them for permission to include them in Firefox3 -eo please
thanks

Comment 3

[Eduardo Trápani]

Sure, I've already sent it directly to you.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #1)
> There are a couple of search engines that should be erased/changed.  Should I
> attach a zip with the whole l10n/eo/browser/searchplugins?

A diff generated with |cvs diff -up8N| would be best.

Comment 5

[Eduardo Trápani]

We haven't landed on CVS, and I couldn't find a way to recreate the cvs diff.  So find attached a diff -ruN (the patch should use -p1) and a .tar.bz2 of the l10n/eo/browser/searchplugins.  Will one of those do?

Comment 6

[Eduardo Trápani]

Attachment: diff -ruN of l10n/eo/browser/searchplugins

Comment 7

[Eduardo Trápani]

Attachment: .tar.bz2 of full l10n/eo/browser/searchplugins

Comment 8

[Mic Berman]

permission from Liberafolio

Sent: Thursday, February 21, 2008 8:22:04 AM GMT -05:00 US/Canada Eastern
Subject: [Bug 402032] Firefox 2 productization,  Esperanto (eo) - contact information for RSS feed

Hi Mic,

I've talked with Kalle Kniivilä, in charge of Liberafolio and he says he'd be glad to be included as an RSS feed in the esperanto version.

Comment 9

[Mic Berman]

I would like to shift this for Firefox 3 and change the title of this bug - Axel any reason not to do that?

Comment 10

[Mic Berman]

checking back in on productization elements

for Search - the current list i have is based on en-US defaults: Google, Yahoo, Answers, AMazon, CC, eBay, Wikipedia.
We can use Wikipedia for Esperanto http://eo.wikipedia.org/

mailto: defaults i.e., Yahoo, Gmail, Hotmail
webcal: 30 boxes

RSS readers: defaults are Google Reader, Bloglines, My Yahoo

Comment 11

[Eduardo Trápani]

See comment #7 on this bug.  Those are the search plugins.  I had forgotten to include them in the language pack.  Both Wikipedia and Google should be in Esperanto.

Here is the new searchplugins directory for Firefox 3.

Comment 12

[Eduardo Trápani]

Attachment: tar.bz2 of l10n/eo/browser/searchplugins

Comment 13

[Mic Berman]

i have asked for gavin to review and then close
i am good to go so would resolve closed fixed upon patch review

Comment 14

[:Gavin Sharp [email: [e-mail]]]

I took a look at that tarball. I noticed that you have google.xml, yahoo.xml and creativecommons.xml files, which aren't necessary. The en-US ones will be picked up if you specify them in list.txt. You should just remove those files (but keep the reference in list.txt).

The format for the wikipedia plugin should be based on an existing plugin like http://mxr.mozilla.org/l10n-central/source/ja-JP-mac/browser/searchplugins/wikipedia-ja.xml , and it would be best to have it's filename contain "wikipedia" to help searching.

Both the wikipedia and the reta-vortaro plugins use the "os" namespace and OpenSearch format. In general we recommend using "MozSearch" format for shipped search plugins, which is a bit simpler. See http://developer.mozilla.org/en/docs/Creating_MozSearch_plugins for more details.

Comment 15

[Axel Hecht [:Pike]]

We should really review what's in CVS when it's in CVS. For example, I never include the en-US plugins in my initial landing anyway. Nor do I really intend to piece the initial landing together from multiple tarballs.

Sorry for the confusion here, and the lag. Too much stuff going on right now, and sadly I'm still seeing major risk in big landings.

Comment 16

[Eduardo Trápani]

Maybe I'm missing something, I thought the initial landing process was actually moving the tarball to cvs (adding pointers and other internal stuff too, of course).

It's ok by me if you want to review the stuff in CVS, but how do we get the CVS access to upload it?  It looks like a chicken and egg situation ...

(I'm already using SVN for 'website', in case that makes things easier, the account is already set up)

Comment 17

[Axel Hecht [:Pike]]

Not to spoil this bug even further (we're going to kill it anyway in favour of a good set of bugs), but yes, landing means landing in CVS. Just that that currently tends to shut down systems we need for release for hours due to load problems. So I need IT to be there and watching that system when I attempt to land.

Comment 18

[Axel Hecht [:Pike]]

Better bugs have been filed now, resolving this bug INCOMPLETE.