Extract translations from viz and tidelines

Translations are now extracted from blip's two submodules. That
way they don't need the extra-tooling, only i18next as a dependency.

Furthermore, they can prefix their translatable strings with
'viz|' or 'tideline|' to use a different namespace and separate
their translations from blip's translation.

app/core/language.js

@@ -17,7 +17,7 @@ i18n
     // To allow . in keys
     keySeparator: false,
     // To allow : in keys
-    nsSeparator: false,
+    nsSeparator: '|',
 
     debug: true,
 

i18next-parser.config.json

@@ -1,6 +1,6 @@
 {
   "keySeparator": "__NO_KEY_SEPARATOR__",
-  "namespaceSeparator": "__NO_NAMESPACE_SEPARATOR__",
+  "namespaceSeparator": "|",
   "lexers": {
     "js": ["JavascriptLexer", "JsxLexer"]
   },

package.json

@@ -17,7 +17,7 @@
     "install-selenium": "./node_modules/selenium-standalone/bin/selenium-standalone install --version=2.53.0",
     "build-docs": "./update-gh-pages.sh",
     "serve-docs": "./node_modules/.bin/gitbook serve",
-    "update-translations": "i18next 'app/**/*.js' -c i18next-parser.config.json -o ."
+    "update-translations": "i18next 'app/**/*.js' 'node_modules/tideline/js/**/*.js' 'node_modules/@tidepool/viz/{stories,storybook}Datatypes/**/*.js' -c i18next-parser.config.json -o ."
   },
   "dependencies": {
     "@tidepool/viz": "0.10.0",