Closed Bug 723964 Opened 8 years ago Closed 7 years ago

[my] Search engine setup for Firefox for Burmese.


(Mozilla Localizations :: my / Burmese, defect)

Not set


(Not tracked)



(Reporter: Pike, Assigned: Milos)




(Keywords: productization)


(1 file, 1 obsolete file)

We want to ship Firefox with a good list of search engines for Burmese. 

We're going to work towards this in three phases. First, the localization team and Milos (Milos Dinic) will look at the market for the language and come up with a good set of search providers. tinaunglinn, Arky, we'll need your input on this, the guidelines for making recommendations are on <>. 

For en-US, we currently use this set, to which we can fall back in the case of lacking localized alternatives:
Google, Yahoo!, Bing, Amazon, eBay, Wikipedia

After we decided on a particular search engine, Milos will contact the owner and ask for permission, and for specifics like proper search flags. tinaunglinn, Arky, we'll likely need your help to at least get the contact information.

Once we have a specification on what the searchengines for Burmese should look like, the localization team and Milos will work on an implementation on that. This should happen by the localization team creating and attaching patches for the desired changes, and requesting review from Milos. After a successful review, the localization team will land them.

Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by Milos, Stas, Axel or someone else appointed by Milos. The data here is sensitive to users and our search partners, thus the extra care here.

The Burmese team will be driving this bug to completion.
Component: Other → my / Burmese
QA Contact: my
I am getting on it Mr.Axel.
Welcome, and thanks, great.
Chit, maybe you have some ideas or comments, too?

Also, if you're interested in the bugs we file on the Burmese localization, you can start watching either the component or the my@localization.bugs alias.
Hi Alex 
I get to know this message and will spread through the Localization team. This weekend we will make our Community meetup and I do share the idea of this.
Google's Burmese Localization now get hit the 100% in search engine. Should we count it into this bug discussions?

As mentioned in description of this bug, we first need to come up with a list of search engines for Burmese. As already noted, en-US defaults are:

Google, Yahoo!, Bing, Amazon, eBay, Wikipedia.

So, as you might know, we have 3 groups of search plugins:

Generic search, e-commerce search and specific interest search groups. There's a good wiki document explaining how to decide on which search engines should you look for and use in each of the group:

After you read that paragraph thoroughly, please give it some time to explore the web in your language and find suitable candidates. I'd recommend some, too, but I didn't have much luck finding search engines in Burmese. That said, I'm more than happy to help you in the process of figuring out what's best for your users.

Once we know which search engines we'd like to include, we'll start talking about the implementation.

As for your question about Google, I'd need to double check that, but yes, we should think about it.
I got it. U means you wanna get the list of search engines to which most of our users are going and giving traffic. Okie first of all it is like the en-us and there is no more change in arranging.

Most of the Myanmar's Internet User us for general purposes and like this so wikipedia for knowledge and glossary search. 

Ok lets rock on the listed search services.
I vote for google for default search engine[]

Thanks you.

I can see that Google search has been translated in Burmese, as well, but it's apparently not yet available on production site.

So now, I can also tell that Wikipedia is available in Burmese(

So, if you don't think we should change anything else, we're left with:

Google, Yahoo!, Bing, Amazon, eBay, Wikipedia(my).

As we're going to use en-US defaults, we don't need any changes to list.txt file for any of the search engines that are already there, except for Wikipedia search plugin instance.

To have wikipedia search in Burmese, we'll need to create a new opensearch plugin, and have an instance referring to it in list.txt. That means that we want to remove 'wikipedia' from list.txt and add 'wikipedia-my' instead.

After we do that, Firefox in Burmese(after being built) will look for wikipedia-my.xml file in /browser/searchplugins/ to get the definition of the search plugin. There's a good document on how to create searchplugins at

After you have made changes to list.txt and created the file as per instructions, you'll want to 'hg add' the new file, save the 'hg diff' output to a file, attach that file here, and ask me for a review. It's really important that you don't commit any changes to these files before you get a positive review from either me or someone else in the team.

Now, if you're not sure you understand any of the stuff above, don't hesitate to ask here, or ping Arky or me.
Ok I will reply detail soon.Now I am discussion with some guys!
Google, Yahoo!, Bing, Amazon, eBay, Wikipedia(my) Lets left with this list. All services are in already user choices.
Anyone got my response.I did a really general research with L10 guys to get this out.
Please let me know this bug was solved ?

I have described in comment 8 in this bug what else we need to do to call this bug fixed. We'll need to create opensearch plugin for wikipedia, and I can help you with that in case you get stuck with coding.

A good working example is:

Please let me know if I can help.
Thanks Milos you get me notified TO DO SEARCH PLUGIN and I will try on my nightly build and test.
If I have any ques I will make you know here.


Just a note: you don't need to wait for builds to be done to test your search plugin. You can do following:

1) create a new profile in firefox and name it ie. testing
2) close firefox
3) open your profiles folder - you can find info on where it is at
4) open directory that has word *testing* in it (or whichever name you used for profile in step 1)
5) Open searchplugins directory. In case it's not there, create it, and open it
6) paste your opensearch plugin in searchplugins folder
7) start firefox and use the *testing* profile

did you manage to create and test searchplugins we've been discussing so far? Also, do you need any help with that?
Attached file Wikipedia Search Plugin - my (obsolete) —
Attached is the Wikipedia search plugin that should work. I based this off of the example in comment 12. 

Warning: I'm no developer and this has not been QA-ed formally.
Comment on attachment 677604 [details]
Wikipedia Search Plugin - my

Hi Laura, welcome to the beautiful world of patching localizations :-)

The Description should be "Wikipedia (my)", I think you took the one from the Bosnian example. The SearchForm should be

The rest looks good.

We've been changing our policy around who's doing patches for search engines, and made Milos the default author of those. so if you'd like him to take over, just say so.

For a full patch, we'd want a 'hg diff' with both the fixed xml added, and an edited browser/searchplugins/list.txt that makes the builds pick this up.
Attachment #677604 - Flags: review-
Thanks Axel! I just realized I left that old description in there and was going to upload a corrected version. You're fast! Thanks for making the correction. 

It would be great if Milos can take over from here since I'm not sure how to do a 'hg diff' and the rest as you describe above.
Assignee: nobody → milos
Hey Axel or Milos -- what are the next steps here?
Any updates? What are the next steps here?
Any updates here ? We all been reacting remaining strings and errors on new pootle. Any updates ?
Milos, can you drive this to completion? Seems we only need to change the wikipedia plugin to a local copy.
What you guys need to do for that wikipedia plug-in ?
Attachment #677604 - Attachment is obsolete: true
Attachment #715460 - Flags: review?(l10n)
Attachment #715460 - Flags: review?(l10n) → review+
Done in
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.