Protocol handlers are a new feature in Firefox 3.1 that allows links like mailto:email@example.com to be handled by a webmail application. In order to do that, the site needs to support a special API described on http://developer.mozilla.org/en/docs/Web-based_protocol_handlers. For en-US, we're currently shipping with GMail and Yahoo! Mail for mailto: and 30boxes for webcal: urls, and we're on a ongoing evangelism effort to add more. ms live mail are coming up shortly. For Malayalam, we'd like to do that, too. First, the localization team and Stas (Stas Malolepszy) will look at the market for the language and come up with a good candidates. Ani, we'll need your input on this, the guidelines for making recommendations are on http://wiki.mozilla.org/Firefox_web_services_guidelines. Following that is a reach out by the evangelism team to try to get the vendor to support protocol handlers. Once that happens, Stas will take over in reviewing the actual implementation, which will need to change the gecko.handlerService.* entries in ml/browser/chrome/browser-region/region.properties. Please don't make changes to that file without getting a positive review by Stas or somebody else appointed by Stas/Sethb on a patch for that change upfront.
Malayalam team: Have you made any progress here? We would love ml to ship with Firefox 3.5 during the beta development cycle. As of today, you are very close, with just 145 strings remaining to translate for FF 3.5 beta 4. However, we should do some research about what protocol handlers should be included in your localized build. Can you make some suggestions for us? You are definitely the best resource for us to ask what is most appropriate for Malayalam users. :) Please do send us some suggestions.
Ani and Joyce, Do you have any suggestions for the protocol handlers that we should include with the Malayalam version of Firefox? We'd like to resolve this bug as we approach the release of Firefox 3.5. If we complete the translation of all strings and fix all the "productization" bugs, we will will consider moving the Malayalam version into "official" status. Please advise. Thank you for all the hard work. We look forward to your comments.
Any suggestions for the protocol handlers that we should include with the Malayalam version of Firefox?
There is no popular Protocol handlers for malayalam. GMAil has malayalam version but it is based on user preference. IMHO this shouldnt be a release blocking bug. GMail and Yahoo! Mail should do fine.
Great, thanks for weighing in with your feedback. We'll go with the en-US defaults: GMail and Yahoo! Mail for mailto:, 30boxes for webcal: and Mibbit for irc: urls. I took a look at region.properties for Malayalam here: http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ml/file/dc06f4e647d4/browser/chrome/browser-region/region.properties ...and saw that the Mibbit handlers are missing. Would you mind creating a patch to add them? Copying the lines 43-49 from the en-US file should be OK: http://hg.mozilla.org/releases/mozilla-1.9.1/file/31a6c9d58956/browser/locales/en-US/chrome/browser-region/region.properties#l43 Also, please remember to increment gecko.handlerService.defaultHandlersVersion by 1. Please attach the patch to this bug and request a review from firstname.lastname@example.org. Please do not commit the change without getting a review first. Thanks! :)
Ani, Joyce, Ashik: ping? Please let us know if you have troubles creating the patch. I'll be more than happy to help.
Created attachment 407744 [details] [diff] [review] Patch for the missing IRC handler I have attached the patch for the missing IRC handler. Hope its ok.
Comment on attachment 407744 [details] [diff] [review] Patch for the missing IRC handler r=me, thanks Ani. This is ready for landing. Please land it on l10n-mozilla-1.9.1, l10n-mozilla-1.9.2 and l10n-central. Please use a descriptive commit message, e.g. "Bug 475017: protocol handler setup for Malayalam, add Mibbit, r=stas". For l10n-mozilla-1.9.1: when the patch lands, please add fixed1.9.1 keyword to this bug. Next, please test the patch in a nightly build and if it's OK, please reply in the current opt-in thread in mozilla.dev.l10n <http://groups.google.com/group/mozilla.dev.l10n/browse_frm/thread/4b9ad68b32106157/> with the new revision number. If Axel approves it please set the status1.9.1 flag in this bug to 'x-fixed' where 'x' is the number of the earliest version of Firefox that includes the fix. For instance, .4-fixed would mean "fixed in 3.5.4." For l10n-mozilla-1.9.2: when the patch lands, please please test the patch in a nightly build and if it's OK, please reply in the current opt-in thread in mozilla.dev.l10n <http://groups.google.com/group/mozilla.dev.l10n/browse_frm/thread/7c4389587d453ff1/> with the new revision number. If Axel approves it please set the status1.9.2 flag in this bug to 'x-fixed' where 'x' is the number of the earliest version of Firefox that includes the fix. For instance, beta1-fixed would mean "fixed in 3.6 beta 1." For l10n-central: when the patch lands, feel free to mark this bug as fixed. Thanks.
Attachment #407744 - Flags: review?(stas) → review+
I have committed the patch on mozilla 1.9.1, l10n-central and mozilla-1.9.2. But I could not test it as I cant build the pack. Please help. Have added the keyword fixed1.9.1 and marking bug as fixed. Kindly advise how to go further.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(In reply to comment #10) > I have committed the patch on mozilla 1.9.1, l10n-central and mozilla-1.9.2. > But I could not test it as I cant build the pack. Please help. Have added the > keyword fixed1.9.1 and marking bug as fixed. Ani, you can test in a 1.9.1 nightly build available here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1-l10n/. I tested it and the change looked OK, but I would appreciate it if you could test as well. For 1.9.2, you'll have to fix an installer bustage, see bug 524502 for details. > Kindly advise how to go further. After the testing and verification is done, please post the new opt-in revision number in the opt-in threads I linked to in comment 9 above.
l10n-src-verification for 1.9.1 updated in: http://hg.mozilla.org/l10n/l10n-src-verification/rev/810ddf3fdf09 l10n-src-verification for 1.9.2 updated in: http://hg.mozilla.org/l10n/l10n-src-verification/rev/0e24c816f9a2 http://hg.mozilla.org/l10n/l10n-src-verification/rev/296d82a048ec FWIW, we're still waiting for a new opt-in from Ani here.
Stas, I have a doubt here. I understand mibbit does not support FreeNode, hence we have to use http://webchat.freenode.net/ for channels in freenode. So is there anything that can be done now, or you want me to go ahead with opting in ?? Sorry for the delay Stas :(
FreeNode is very popular for irc and mibbit does not support it. It would be great to have freenode Web IRC also added to irc handlers. The format used is http://webchat.freenode.net/?nick=&channels=&prompt=1 can nickname and channels be passed to webchat.freenode.net ? Or do they need to provide handling of irc:// urls?
freenode is blocking mibbit, not the other way around, AFAIK.
That is indeed the case, AFAIK too, but the result is - you cannot access freenode with mibbit. If we have only mibbit configured and it does not work with freenode, that is not good. Also, most of the Free Software developer community/project channels are on freenode.
http://webchat.freenode.net/ is not an irc: protocol handler per se: it's web interface to freenode.net and works only with this server. Which means that you're not able, AFAIK, to open an irc: link like irc://irc.mozilla.org/l10n in webchat.freenode.net. That's why I don't think we should include it in Firefox--it would effectively break the support for irc: protocol handling for all networks except freenode.net.
Ok then. We can go ahead with the current settings for Malayalam. Though it would be disappointing when users can't access freenode irc urls - though that is not a problem firefox created or can solve.
axod @ Mibbit has promised to redirect freenode requests to freenode web gateway. #mibbit on irc.mibbit.net tomaw axod has already agreed to redirect affected freenode users. #freenode on irc.freenode.net <tomaw> axod has agreed to forward freenode users here via some redirect to our webchat but I'm not sure if he's still planning on honouring that. There was a request to handle it differently, don't know how complex it would be, may be it is already rejected. mquin> AIUI that feature should allow gateways to be specified by network, so freenode, quakenet etc who run their own gateways can be handled <tomaw> mquin: That was a proposal they seem to have rejected
I have opted in for both mozilla 1.9.1 and mozilla 1.9.2 threads as mentioned in comment #9
You need to log in before you can comment on or make changes to this bug.