Add 360 search engine to Chromium

components/search_engines/prepopulated_engines.json

Index: components/search_engines/prepopulated_engines.json
diff --git a/components/search_engines/prepopulated_engines.json b/components/search_engines/prepopulated_engines.json
index 083a6e983a661104fceb71186740b1412acdde2e..abd688d98e7921ef6a0fa5b7e8c5e14225d2136f 100644
--- a/components/search_engines/prepopulated_engines.json
+++ b/components/search_engines/prepopulated_engines.json
@@ -11,7 +11,7 @@
 // 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.
 //
@@ -30,7 +30,7 @@
 
     // 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
@@ -189,6 +189,16 @@
       "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",