Drop Big5-HKSCS and add IBM866 in the encoding menu.

Drop Big5-HKSCS and add IBM866 in the encoding menu.

The HTML encoding spec unified Big5 and Big5-HKSCS and we're not
distinguishing them any more.

The spec also has IBM866 that is not in the menu, yet.

BUG=None
TEST=manual:
1. load a page in ibm866 and check the encoding in More Tools|Encoding.
2. load pages labelled as in Big5 and Big5-HKSCS and check the encoding.
TEST=browser_tests --gtest_filter=*ncodin*
TEST=unit_tests --gtest_filter EncodingMenu*

Committed: https://crrev.com/03456dca25a19f8b445321ba5531b6693883cda5
Cr-Commit-Position: refs/heads/master@{#322068}

[jungshik at Google, 2015-03-20 22:56:15]

jshin@chromium.org changed reviewers:
+ jsbell@chromium.org

[jungshik at Google, 2015-03-20 22:58:53]

jshin@chromium.org changed reviewers:
+ sky@chromium.org

[jungshik at Google, 2015-03-20 22:58:54]

sky@chromium.org: PTAL for owner approval.
jsbell: PTAL at the encoding menu changes. 

Thanks

[jsbell, 2015-03-20 23:49:18]

lgtm

[sky, 2015-03-21 16:07:56]

https://codereview.chromium.org/1024713002/diff/20001/chrome/app/chrome_comma...
File chrome/app/chrome_command_ids.h (right):

https://codereview.chromium.org/1024713002/diff/20001/chrome/app/chrome_comma...
chrome/app/chrome_command_ids.h:101: #define IDC_ENCODING_KOREAN            
35509
Is there a reason you don't want adjust subsequent commands so we don't have any
holes?

[jungshik at Google, 2015-03-23 19:36:17]

https://codereview.chromium.org/1024713002/diff/20001/chrome/app/chrome_comma...
File chrome/app/chrome_command_ids.h (right):

https://codereview.chromium.org/1024713002/diff/20001/chrome/app/chrome_comma...
chrome/app/chrome_command_ids.h:101: #define IDC_ENCODING_KOREAN            
35509
On 2015/03/21 16:07:56, sky wrote:
> Is there a reason you don't want adjust subsequent commands so we don't have
any
> holes?

Initially, I thought that it'd lower the chance of a profile "conflict" between
versions, but it should not matter because the preferred encoding is stored as a
string (if somebody sets it to Big5HKSCS, which is very unlikely).  

I'll just remove the holes (there's one more hole created when removing
ISO-8859-1).

[sky, 2015-03-23 19:55:53]

LGTM

[jungshik at Google, 2015-03-24 00:16:51]

The CQ bit was checked by jshin@chromium.org

[jungshik at Google, 2015-03-24 00:16:52]

The patchset sent to the CQ was uploaded after l-g-t-m from jsbell@chromium.org
Link to the patchset: https://codereview.chromium.org/1024713002/#ps40001
(title: "remove holes in IDC ids")

[commit-bot: I haz the power, 2015-03-24 00:17:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1024713002/40001

[commit-bot: I haz the power, 2015-03-24 01:08:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-03-24 01:08:07]

Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[jungshik at Google, 2015-03-24 19:54:24]

The CQ bit was checked by jshin@chromium.org

[jungshik at Google, 2015-03-24 19:54:25]

The patchset sent to the CQ was uploaded after l-g-t-m from jsbell@chromium.org,
sky@chromium.org
Link to the patchset: https://codereview.chromium.org/1024713002/#ps60001
(title: "fix EncodingMenuControllerTest.EncodingIDsBelongTest")

[commit-bot: I haz the power, 2015-03-24 19:55:07]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1024713002/60001

[commit-bot: I haz the power, 2015-03-24 20:54:18]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2015-03-24 20:54:49]

Patchset 4 (id:??) landed as
https://crrev.com/03456dca25a19f8b445321ba5531b6693883cda5
Cr-Commit-Position: refs/heads/master@{#322068}