[ja] Support i18n 70-base64 node. (#591)

* [ja] Translate 70-base64 node.

* Fix PR review #591 "Buffer" -> "バッファ".

We have used Japanese katakana words of "buffer" in http-request and file-out nodes.

* Fix PR review #591 "Base64" -> "base64"

* Fix PR review #591 "Base64から文字列へデコード" -> "Base64から文字列へ変換"

parsers/base64/locales/en-US/70-base64.html

@@ -0,0 +1,7 @@
+<script type="text/x-red" data-help-name="base64">
+    <p>A function that converts the chosen property (default <code>msg.payload</code>) to and from base64 format.</p>
+    <p>If the input is a buffer it converts it to a Base64 encoded string.</p>
+    <p>If the input is a Base64 string it converts it back to a binary buffer.</p>
+    <p>You can also fix coding into base64, and base64 to buffer if required.</p>
+    <p>Note: Using "Encode to Base64" will encode an already encoded string.</p>
+</script>

parsers/base64/locales/en-US/70-base64.json

@@ -0,0 +1,24 @@
+{
+  "base64": {
+    "base64": "base64",
+    "label": {
+      "action": "Action"
+    },
+    "convert": {
+      "buffer": "Convert Buffer <-> Base64",
+      "encode": "Encode as Base64",
+      "decode": "Convert Base64 to String"
+    },
+    "log": {
+      "nonbase64encode": "Not a Base64 string - maybe we should encode it..."
+    },
+    "warn": {
+      "cannothandle": "This node only handles strings or buffers.",
+      "noproperty": "No property found to process"
+    },
+    "error": {
+      "invalid": "Invalid Base64 string",
+      "nonbase64": "Not a Base64 string"
+    }
+  }
+}