Closed
Bug 403020
(fx3-wsl10n-gu-IN)
Opened 17 years ago
Closed 16 years ago
[gu-IN] web services review
Categories
(Mozilla Localizations :: gu-IN / Gujarati, defect)
Mozilla Localizations
gu-IN / Gujarati
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: mic, Assigned: ankit)
References
Details
checking on list of web services it appears you removed amazon creative commons wikipedia was there a reason or can those be added back in as the standard defaults we ship with? please confirm the RSS feed: BBC thanks mic
Assignee | ||
Comment 1•17 years ago
|
||
The reason is: There is no Gujarati (Indic) quivalent url for these web services.
Reporter | ||
Comment 2•17 years ago
|
||
thanks, we have a new set of guidelines for replacing these defaults with better local choices. the guidelines are available: http://wiki.mozilla.org/Firefox_web_services_guidelines i have done some research but need some help. can you take a review and offer any suggestions for gujarati?
Whiteboard: needs-mic
Assignee | ||
Comment 3•17 years ago
|
||
For Gujarati, there are only three searchplugins available which is Google, eBay, and Yahoo... And I think, it's better to provide the local searchplugins only to the end user. Because providing some bits in english would distract them & they will not like it. However most of Gujarati speaking people understand english, but still I would suggest not to use english bits at all.
Assignee | ||
Updated•17 years ago
|
Summary: web services review → [gu-IN] web services review
Reporter | ||
Updated•16 years ago
|
Blocks: fx3-l10n-gu-IN
Reporter | ||
Comment 4•16 years ago
|
||
ankit my sincere apologies for taking so long to respond here. first question, i noticed that bug was marked for PC platform only, was that intentional? second - i understand your point about Gujarati only search - is there a Gujarait-English dictionary we might want to use as well? i did a minor search and found several including: http://www.gujaratilexicon.com/ what do you think? we could leave as is for b4 and figure this out for RC1
Hardware: PC → All
Reporter | ||
Updated•16 years ago
|
Whiteboard: needs-mic → needs-gavin
Reporter | ||
Comment 5•16 years ago
|
||
also - can you indicate what you are using for livebookmark news feed and RSS Readers for feed - I hope there is an interesting Feed in Gujarati language but don't know which ones? for readers - not sure any providers localized to gujarait except maybe netvibes - any ideas?
Comment 6•16 years ago
|
||
The existing search plugins look good. Would be nice to confirm the eBay parameters, though: <Url type="text/html" method="GET" template="http://search.ebay.co.in/search/search.dll"> <Param name="query" value="{searchTerms}"/> <Param name="MfcISAPICommand" value="GetResult"/> <Param name="ht" value="1"/> <Param name="ebaytag1" value="ebayreg"/> <Param name="srchdesc" value="n"/> <Param name="maxRecordsReturned" value="300"/> <Param name="maxRecordsPerPage" value="50"/> <Param name="SortProperty" value="MetaEndSort"/> </Url> They might not all be needed, and it might be good to add a Mozilla-specific parameter.
Whiteboard: needs-gavin
Reporter | ||
Comment 7•16 years ago
|
||
i will confirm with with eBay and write back in bug when i hear from them
Whiteboard: needs-mic
Reporter | ||
Comment 8•16 years ago
|
||
i heard from one contact in eBay who will double check tomorrow with contacts in eBay. in the mean time - fwiw - he has offered this, but i'm really not sure its that helpful/we should do anything different until I get the official word from eBay india: "You can default the search to: http://search.ebay.{TopLevelDomain}/{query} That then outputs the standard result set (although I'll double check if this is the best route tomorrow) "
Comment 9•16 years ago
|
||
(In reply to comment #8) > "You can default the search to: > http://search.ebay.{TopLevelDomain}/{query} > That then outputs the standard result set (although I'll double check if > this is the best route tomorrow) " The "{query}" part is what we want more information about. What parameters are required? Should there be a Firefox-specific parameter?
Assignee | ||
Comment 10•16 years ago
|
||
(In reply to comment #4) > ankit > my sincere apologies for taking so long to respond here. > first question, i noticed that bug was marked for PC platform only, was that > intentional? > second - i understand your point about Gujarati only search - is there a > Gujarait-English dictionary we might want to use as well? i did a minor search > and found several including: http://www.gujaratilexicon.com/ > what do you think? > > we could leave as is for b4 and figure this out for RC1 > Yes, I am fine with http://www.gujaratilexicon.com/ , it's good resource.
Reporter | ||
Comment 11•16 years ago
|
||
awesome. i will get permission to include them and see if they are interested in building a plug in for Firefox.
Reporter | ||
Comment 12•16 years ago
|
||
i have used their feedback form to ask for permission but i haven't heard from them yet. Ankit if you get a chance and can contact someone there and get me an email address that'd be great. http://www.gujaratilexicon.com/index.php?action=contact
Reporter | ||
Comment 13•16 years ago
|
||
ankit, any news on your side? i have not been successful yet on my side to contact gujaratilexicon
Comment 14•16 years ago
|
||
I will look into issue. Thanks.
Assignee | ||
Comment 15•16 years ago
|
||
(In reply to comment #14) > I will look into issue. Thanks. > Thanks Kartik!
Comment 16•16 years ago
|
||
This bug didn't mention protocol handlers yet, I guess we'll go for en-US defaults? If so, we still need to get yahoo mail landed for mailto: protocol.
Alias: fx3-wsl10n-gu-IN
Reporter | ||
Comment 17•16 years ago
|
||
sounds good to me. Ankit we can revisit mailto and webcal for release in 3.0.1 if you think of other local services that would be better
Reporter | ||
Updated•16 years ago
|
Whiteboard: needs-mic
Reporter | ||
Comment 18•16 years ago
|
||
permission from Gujaratilexicon, thanks everyone :) ----- Original Message ----- From: "Ashok Karania" < To: mic Sent: Monday, April 7, 2008 6:27:42 AM GMT -05:00 US/Canada Eastern Subject: Gujaratilexicon.com As Search Engine Dear Mic Hi! We would be more than pleased to allow Gujaratiexicon in Gujarati Version of Firefox. Please consider this as our approval. Regards Ashok Karania
Reporter | ||
Comment 19•16 years ago
|
||
per bug 380785 we need to include wikipedia. can you please add a patch for this. here is how to grab english version Search is all (*) in browser/searchplugins. Task: Replace en.wikipedia.org with gu.wikipedia.org. So, first, we need a plugin for the latter, for which a good name will be wikipedia-gu.org. You should create this by following what we do for en-US closely, that one is at http://mxr.mozilla.org/mozilla/source/browser/locales/en-US/searchplugins/wikipedia.xml. Use that as a template, and change the Urls accordingly, and use the link title of the rel="search" link on your wikipedia site as ShortName. That matches what the site sends, so Firefox will detect that it already has the search plugin. So, now you have the plugin in gu/browser/searchplugins/wikipedia-gu.xml, and to get it picked up, you replace the wikipedia with wikipedia-gu in list.txt. To create the patch, do, in browser/searchplugins cvs add wikipedia-gu.xml cvs -z3 diff -uN and attach the output here, and mark it as patch, there's a checkbox for that. To request review on that, set the "Review" flag to '?', and the requestee to my bugzilla ID. (*) The search ordering stuff is in region.properties, too, but that's changed rarely.
Assignee | ||
Comment 20•16 years ago
|
||
Done!
Comment 21•16 years ago
|
||
Ankit fixed list.txt, I fixed wikipedia-gu.xml to actually match what the site sends.
Comment 22•16 years ago
|
||
Marking FIXED, thanks. Reference is http://hg.mozilla.org/users/axel_mozilla.com/l10n-src-verification/index.cgi/file/924dd9d75a03/reference/HEAD/gu-IN/.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 23•16 years ago
|
||
If we want to pick up Gujaratilexicon.com still, we should do that in a new bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•