Kenneth Bruskiewicz

Will come in with https://github.com/cidgoh/DataHarmonizer/tree/dh2-431-export-as-json as I can reuse the same code. @ddooley the "Save as..." vs the "Export to..." feature – should this only be supported in the "Save...

@ddooley Should this be distinct from the "Save as..." functionality? It seems like the most natural place for this.

@pkalita-lbl If you want to take a quick look I'd be happy for any feedback!

Some bugs came out in testing. Also one extra request c/o @ddooley , support `translations.json` option for additional mapping in "`/locales/translations.json`".

Update on the completion status of this PR: - The DataHarmonizer should still "work offline", i.e. as a standalone HTML file rather than provided through a server. (this was broken...

> Thanks for working on this PR. We host a version of the Data Harmonizer and having localization support will make our lives easier to address concern from our external...

@ddooley I needed to rework the multi select internationalization to have a simpler implementation, particularly so copy-paste was less fragile. I merged the current master with this branch.

@ddooley I believe you've tested all of the changes made two weeks ago for i18n support (multi select menus are translated, provide values, and switch back and forth between languages;...

Keeping tabs on what support says here: https://forum.handsontable.com/t/shared-data-edits-between-tables-with-different-filters/7220 This looks like a similar problem/issue (multiple editors and data synchronization between tables): https://forum.handsontable.com/t/multiple-tables-with-custom-editors/6764 https://jsfiddle.net/1dLzb7st/ https://github.com/handsontable/handsontable/issues/7560

@BestQuark I notice that link to the Flow class is not yet merged into `main`. Is that something we should do? Also does it have more up-to-date flow methods?