Add 360 search engine to Chromium

components/search_engines/prepopulated_engines.json

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // This file is used during build to generate prepopulated_engine.h/cc.
 // For more details see tools/json_to_struct/json_to_struct.py.
 
 // Engine definitions. See prepopulated_engines_schema.json for the field
 // definitions.
 
 // The following unique IDs are available:
 //    7, 11, 12, 13, 14, 18, 19, 20, 22, 24, 26, 28, 29, 30, 32, 33, 34, 39, 37,
 //    38, 40, 41, 42, 46, 47, 48, 49, 51, 52, 58, 59, 69, 71, 72, 82, 84, 86,
-//    88, 89, 91+
+//    89, 91+
 //
 // IDs > 1000 are reserved for distribution custom engines.
 //
 // NOTES:
 //   - CHANGE THE ABOVE NUMBERS IF YOU ADD A NEW ENGINE; ID conflicts = bad!
 //   - Make sure you update the int_variables below as required.
 //   - NOTIFY the Chrome Webstore team if you add/delete a search engine or
 //     change domain of an existing one (send email to webstore-eng@google.com).
 //     They need to know the mapping between an engine's "id" and its URLs.
 
 {
   "int_variables": {
     // The following id is for UMA stats only. Please update it if you add new
     // engines outside the current range or it will not be counted in stats.
     "kMaxPrepopulatedEngineID": 90,
 
     // Increment this if you change the data in ways that mean users with
     // existing data should get a new version.
-    "kCurrentDataVersion": 92
+    "kCurrentDataVersion": 93
   },
 
   // The following engines are included in country lists and are added to the
   // list of search engines on the first run depending on user's country.
   "elements": {
     "aol": {
       "name": "AOL",
       "keyword": "aol.com",
       "favicon_url": "http://search.aol.com/favicon.ico",
       "search_url": "http://search.aol.com/aol/search?q={searchTerms}",
@@ skipping 138 matching lines @@
     "seznam": {
       "name": "Seznam",
       "keyword": "seznam.cz",
       "favicon_url": "http://search.seznam.cz/r/img/favicon.ico",
       "search_url": "http://search.seznam.cz/?q={searchTerms}",
       "suggest_url": "http://suggest.fulltext.seznam.cz/fulltext_ff?phrase={searchTerms}",
       "type": "SEARCH_ENGINE_SEZNAM",
       "id": 25
     },
 
+    "so_360": {

[Peter Kasting, 2016/08/18 00:39:55]

Nit: I'd just name this "360" and put it atop the list, unless there are
restrictions against doing that.

[Ian Wen, 2016/08/18 03:13:36]

The reason why I put so_360 instead of 360_so or simply 360 is that the name of
the json entry will be converted to a C++ variable. And unfortunately C++
doesn't allow variable names to start with number.

+      "name": "360",
+      "keyword": "so.com",
+      "favicon_url": "https://www.so.com/favicon.ico",
+      "search_url": "https://www.so.com/s?ie={inputEncoding}&q={searchTerms}",
+      "suggest_url": "https://sug.so.360.cn/suggest?encodein={inputEncoding}&encodeout={outputEncoding}&format=opensearch&word={searchTerms}”",
+      "type": "SEARCH_ENGINE_360",
+      "id": 88
+    },
+
     "sogou": {
       "name": "\u641c\u72d7",
       "keyword": "sogou.com",
       "favicon_url": "http://www.sogou.com/images/logo/old/favicon.ico",
       "search_url": "http://www.sogou.com/web?ie={inputEncoding}&query={searchTerms}",
       "type": "SEARCH_ENGINE_SOGOU",
       "id": 56
     },
 
     "vinden": {
@@ skipping 794 matching lines @@
       "name": "Zoznam",
       "keyword": "zoznam.sk",
       "favicon_url": "http://www.zoznam.sk/favicon.ico",
       "search_url": "http://www.zoznam.sk/hladaj.fcgi?s={searchTerms}",
       "encoding": "windows-1250",
       "type": "SEARCH_ENGINE_ZOZNAM",
       "id": 85
     }
   }
 }