aka message bundles, language bundles, localization bundles, language modules, ...

...

sudo port install aspell
sudo port install aspell-dict-$NEW_LOCALE
# or brew install aspell

for f in $(find . -name *$NEW_LOCALE.properties); do
  echo "~~~~~~~~~ $f ~~~~~~~~"
  cat $f | sed -E 's;.=(.);\1;' | grep -vE '^(#|$)' | aspell -a -l $NEW_LOCALE --dont-suggest
done

TODOs

• Do we need an MVH (to setup/check /server/i18n/system/languages) ?
  • we could perhaps start shipping default config with just english in there, and each module would add its own at install.
  • If so, where do we put it ? Just depend on core... or have it in core ? (kinds of put a hard dependency on core version tho)
  • Or another module that has optional deps on the lang modules (so it is installed AFTER all langs, but that wouldn't kick in if someone ADDS a lang, unless it does so at startup time rather than update-time)
• process(es) for transla-tions/-tors
• tools to visualize completeness of translations
  • since we have the key generation mechanism, we probably want tooling to verify translations based on that (e.g for example certain languages will need to override certain specific keys, while some won't – tooling should allow to see translation completion regardless)
  • when adding/remove keys, workflows should be triggered (human or machine) to get translations done for those keys.