Policy Ui sends correct translations for risk tags.

chrome/browser/resources/md_policy/policy_resources.grd

Index: chrome/browser/resources/md_policy/policy_resources.grd
diff --git a/chrome/browser/resources/md_policy/policy_resources.grd b/chrome/browser/resources/md_policy/policy_resources.grd
new file mode 100644
index 0000000000000000000000000000000000000000..3f76c40f0d89d1ce3a0617a49adcfe6ed8f82fa7
--- /dev/null
+++ b/chrome/browser/resources/md_policy/policy_resources.grd
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<grit latest_public_release="0" current_release="1">
+  <outputs>
+    <output filename="grit/policy_resources.h" type="rc_header">
+      <emit emit_type='prepend'></emit>
+    </output>
+    <output filename="grit/policy_resources_map.cc"
+            type="resource_file_map_source" />
+    <output filename="grit/policy_resources_map.h"
+            type="resource_map_header" />
+    <output filename="policy_resources.pak" type="data_package" />
+  </outputs>
+  <release seq="1">
+    <structures>
+      <structure name="IDR_MD_POLICY_HTML"
+                 file="md_policy.html"
+                 type="chrome_html"/>

[Dan Beam, 2015/10/13 16:49:23]

why are you making a .grd file for 1 HTML file?  why not just put this in
chrome/browser/browser_resources.grd?

[fhorschig, 2015/10/14 14:50:23]

Assuming I would not move code into a separate file. In this case, all build
files, the changes in the policy_ui etc. would be introduced in the follow up
CL. And this is exactly where I am coming from. (Someone requested to put all
changes to policy_ui and build files into a separate CL. This is this separate
CL)

[Dan Beam, 2015/10/14 20:21:22]

I have no idea what this means

[fhorschig, 2015/10/14 20:53:44]

Sorry, the text is overly complicated. I _will_ need a lot of files in policy
resources grid [1]. The only file that is currently in there, _was_ already in
the browser_resources.grd [2]. The whole point of this CL is to introduce the
build files for this structure (so we don't have it merged with the other CL).
If you would like me to merge the two CLs, I can do so. But we already had a
point where both CLs were merged and someone proposed to separate them.

In case this still makes no sense, I will look up with whom I discussed this
earlier and ask if I misunderstood his intention.

[1] https://codereview.chromium.org/1371073003/patch/460001/470008
[2] https://codereview.chromium.org/1395073002/patch/2/80003

[Dan Beam, 2015/10/14 21:01:29]

makes sense but I had no way of knowing there'd be a lot more in this file

TODO(fhorschig): move other resources here

would've been a good clue ;)

[fhorschig, 2015/10/15 14:45:38]

TODO is a nice idea. Added one and kept this in mind for later CLs.

+    </structures>
+  </release>
+</grit>