Run the JSON Schema Compiler's bundle compilation on JSON files. Previously it

chrome/browser/extensions/api/i18n/i18n_api.cc

 // Copyright (c) 2012 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.
 
 #include "chrome/browser/extensions/api/i18n/i18n_api.h"
 
 #include <algorithm>
 #include <string>
 #include <vector>
 
 #include "base/string_piece.h"
 #include "base/string_split.h"
 #include "chrome/browser/prefs/pref_service.h"
 #include "chrome/browser/profiles/profile.h"
+#include "chrome/common/extensions/api/i18n.h"
 #include "chrome/common/pref_names.h"
-#include "chrome/common/extensions/api/i18n.h"
 
 namespace GetAcceptLanguages = extensions::api::i18n::GetAcceptLanguages;
 
 // Errors.
 static const char kEmptyAcceptLanguagesError[] = "accept-languages is empty.";
 
-bool GetAcceptLanguagesFunction::RunImpl() {
+bool I18nGetAcceptLanguagesFunction::RunImpl() {
   std::string accept_languages =
       profile()->GetPrefs()->GetString(prefs::kAcceptLanguages);
   // Currently, there are 2 ways to set browser's accept-languages: through UI
   // or directly modify the preference file. The accept-languages set through
   // UI is guranteed to be valid, and the accept-languages string returned from
   // profile()->GetPrefs()->GetString(prefs::kAcceptLanguages) is guranteed to
   // be valid and well-formed, which means each accept-langauge is a valid
   // code, and accept-languages are seperatd by "," without surrrounding
   // spaces. But we do not do any validation (either the format or the validity
   // of the language code) on accept-languages set through editing preference
@@ skipping 10 matching lines @@
                   languages.end());
 
   if (languages.empty()) {
     error_ = kEmptyAcceptLanguagesError;
     return false;
   }
 
   results_ = GetAcceptLanguages::Results::Create(languages);
   return true;
 }