de German web services addition for Firefox 3

VERIFIED FIXED

Status

Mozilla Localizations
de / German
VERIFIED FIXED
10 years ago
10 years ago

People

(Reporter: Mic Berman, Assigned: atopal)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments, 2 obsolete attachments)

(Reporter)

Description

10 years ago
Per Jan 7 google discussion, decided to add LEO as a new search plug in. Rationale is for specific search engine's this is a well used service for translating German to English (among other languages). It would be a good UE addition for German users
(Reporter)

Comment 1

10 years ago
waiting on permission from LEO directly and seach plug in to be built

Updated

10 years ago
Assignee: nobody → a.topal
(Assignee)

Comment 2

10 years ago
Martin linked to the plugin in his mail, is this good to go? 
(Reporter)

Comment 3

10 years ago
good to go for me. received permission from Martin of Leo:


----- Original Message -----
From: "Martin Riethmayer" <martin@leo.org>
To: mic@mozilla.com
Cc: "a topal" <a.topal@uni-duisburg.de>, axel@mozilla.com, "Hans Riethmayer" <riethmayer@leo.org>
Sent: Tuesday, January 22, 2008 12:26:37 PM (GMT-0500) America/New_York
Subject: Re: [mic@mozilla.com: Re: AW: Firefox 3 release]

Hi Mic
we would very much appreciate to be included in the upcoming German 
Firefox release as one of the pre-configured search engines. I will try 
to look into the OpenSearch documentation to make sure our current 
search engine file complies to it. I will send the final version ASAP.

Best regards

Martin
Whiteboard: needs-patch
(Reporter)

Comment 4

10 years ago
received from LEO:

http://tdict.leo.org/plugins/Shared/Searches/leo_ende_de.xml (German
strings version)
http://tdict.leo.org/plugins/Shared/Searches/leo_ende_en.xml (English
strings version) 
(Reporter)

Comment 5

10 years ago
ping
(Reporter)

Updated

10 years ago
Blocks: 415583

Comment 6

10 years ago
The fine thing about LEO is that it works both ways, en=>de and de=>en sametime, you don't need to specify which direction is preferred. A well working but undocumented .xpi for SEAMONKEY/Mozilla exists at 
http://leodict.mozdev.org/installation.html

I'm using the en<=>de extension in seamonkey, and en<=>de and fr<=>de s:

http://dict.leo.org/?lp=ende&lang=de&searchLoc=0&cmpType=relaxed&relink=on&sectHdr=on&spellToler=std&search=%s
http://dict.leo.org/frde?lp=frde&lang=de&searchLoc=0&cmpType=relaxed&relink=on&sectHdr=on&spellToler=on&search=%s

Sorry for the bugspam, I just wanted to show a very special usability advantage of LEO, besides its forums where you can talk or ask about things LEO doesn't yet/correctly/complete know.

more about bookmarklets: http://smoothwheel.mozdev.org/bookmarklets.html
(Reporter)

Comment 7

10 years ago
Abdulkadir - can you attach a patch or a diff to the bug so we can close please, thanks :)
(Assignee)

Comment 8

10 years ago
Created attachment 303223 [details] [diff] [review]
Adding leo to searchplugins
(Assignee)

Comment 9

10 years ago
I'm not sure, is a review needed for this? If not, I'm going to check it in.
Status: NEW → ASSIGNED
(Reporter)

Comment 10

10 years ago
review needed, yes, gavin is alerted he will review thanks
Whiteboard: needs-patch → needs-gavin
Comment on attachment 303223 [details] [diff] [review]
Adding leo to searchplugins

>Index: leo_ende_de.xml

>+<SearchPlugin xmlns="http://www.mozilla.org/2006/browser/search/" xmlns:os="http://a9.com/-/spec/opensearch/1.1/">

Please remove the "os" namespace definition, and all "os:" prefixes, they aren't needed.

>+<os:ShortName>LEO De-Eng</os:ShortName>

When I visit http://dict.leo.org/ , the search bar advertises the engine with the name "LEO Eng-Deu". It would be good to stay consistent, so that the search bar doesn't offer to install an engine that's already installed. This is a problem with their current plugin, too - when you install it you still see an available engine to install, because the title attribute they use in the <link rel="search"> doesn't match the ShortName in the engine description file. Should probably point that out to them.

><os:InputEncoding>UTF-8</os:InputEncoding>

http://dict.leo.org/ seems to use ISO-8859-15, are you sure this is correct? I guess it matches their plugin, so it's probably OK.

>+<os:Url type="text/html" method="GET" template="http://dict.leo.org/?lp=ende&amp;search={searchTerms}">
>+</os:Url>

I guess they didn't request a specific Mozilla parameter? I'm not sure whether we include one by default usually or not. Mic?

>\ No newline at end of file

Please add one :)

Also need to add a SearchForm element (that just points to http://dict.leo.org/ , I guess - it's used for blank queries).
Attachment #303223 - Flags: review-
Whiteboard: needs-gavin → needs-patch
(Reporter)

Comment 12

10 years ago
AFAIK it's not a requirement but we usually ask if they want something like: from=fx3
I don't believe Martin (Leo) requested one but I will ask him if he'd like one and post response to the bug
(Reporter)

Comment 13

10 years ago
----- Original Message -----
From: "Martin Riethmayer"
To: "Michal Berman" 
Cc: "a topal" "Hans Riethmayer" 
Sent: Saturday, February 16, 2008 5:46:46 AM (GMT-0500) America/New_York
Subject: Re: Firefox 3 release]

Mic
the proposed solution (from=fx3) would be great, thanks.
(Assignee)

Comment 14

10 years ago
Created attachment 303878 [details] [diff] [review]
Next try for LEO-plugin
Attachment #303223 - Attachment is obsolete: true
(Assignee)

Comment 15

10 years ago
(In reply to comment #11)
> http://dict.leo.org/ seems to use ISO-8859-15, are you sure this is correct? I
> guess it matches their plugin, so it's probably OK.

I tried all German characters and it worked flawlessly, so I guess it's okay. 


> Also need to add a SearchForm element (that just points to http://dict.leo.org/
> , I guess - it's used for blank queries).

I don't know the spec at all, but the current form seems to handle blank queries quite well, forwarding to http://dict.leo.org/
How would another searchform element be added anyway?
(In reply to comment #15)
> > Also need to add a SearchForm element (that just points to http://dict.leo.org/
> > , I guess - it's used for blank queries).
> 
> I don't know the spec at all, but the current form seems to handle blank
> queries quite well, forwarding to http://dict.leo.org/
> How would another searchform element be added anyway?

Yeah, the search service code uses the <Url>'s host as a best-guess, but it would be better to be explicit. You just need to add "<SearchForm>http://dict.eo.org</SearchForm>" to the plugin.
(Assignee)

Comment 17

10 years ago
Created attachment 303908 [details] [diff] [review]
Leo plugin including seachform element

Alright, this should be it then.
Attachment #303878 - Attachment is obsolete: true
(Reporter)

Updated

10 years ago
Whiteboard: needs-patch → needs-gavin
Comment on attachment 303908 [details] [diff] [review]
Leo plugin including seachform element

>Index: leo_ende_de.xml

>+<Url type="text/html" method="GET" template="http://dict.leo.org/?lp=ende&amp;from=fx3&amp;search={searchTerms}">
>+</Url>

Just a nit: it would be easier to read if the parameters were in <Param> elements, e.g. http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/locales/en-US/searchplugins/google.xml&rev=1.13&mark=7-11 .
Attachment #303908 - Flags: review+
Whiteboard: needs-gavin
(Assignee)

Comment 19

10 years ago
Created attachment 304224 [details] [diff] [review]
Leo plugin including param elements

Checking in with seperate Param elements, thanks Gavin
(Reporter)

Updated

10 years ago
Whiteboard: needs-gavin
(Assignee)

Updated

10 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Whiteboard: needs-gavin

Comment 20

10 years ago
Gavin, this didn't make it into the l10n-src-verification reference, right? Did that slip, or is that intentional?
Sorry, I forgot about this one. Just added it now.
(Reporter)

Comment 22

10 years ago
my only outstanding issue on this is whether we will include gmx as a mailto provider - please advise thanks
(Assignee)

Comment 23

10 years ago
GMX is certainly one of the bigger mail providers here in Germany, including them would depend on how many providers we currently have and how many should be on the list as a maximum?

Comment 24

10 years ago
http://wiki.mozilla.org/Firefox_web_services_Review#de doesn't reference any real discussion on mail handlers, gmx.de is just one I knew about. Other recommendations?

We have two things on the plate here:

One is to get those providers to support protocol handlers on their site, the other is for us to decide which ones to support by default. We'll come up with limits today-ish, but that shouldn't keep us from reaching out to providers in Germany and lobby for supporting this. As they can add themselves as handlers on their site themselves, all their users would benefit from them supporting that, independent on whether we ship them or not.

http://developer.mozilla.org/en/docs/Web-based_protocol_handlers is the MDC documentation to point to.

Reopening to get traction that we still have things in the air here. CCing Jane, not sure if she could help in the communication here.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 25

10 years ago
comment #23, a maximum hasn't been determined yet. what's important is to have local choices to improve user exprience
(Assignee)

Comment 26

10 years ago
then I would recommend web.de, gmx.de, gmail.com, hotmail.de and yahoo.de for Germany. That should cover the most popular free mail providers.
(Reporter)

Comment 27

10 years ago
moving the balance of this discussion on web handlers to a new bug so we can close this one out for RC1
Status: REOPENED → RESOLVED
Last Resolved: 10 years ago10 years ago
Resolution: --- → FIXED

Updated

10 years ago
Blocks: 427374

Comment 28

10 years ago
Marking verified with yahoo and 30 boxes defaults in for protocol handlers, reference is http://hg.mozilla.org/users/axel_mozilla.com/l10n-src-verification/index.cgi/file/f0658577965d/reference/HEAD/de/.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.