Bug #84497 Encoding Error during migration from PostgreSQL database with Japanese Character

Description:
So far I've tried adding the encoding to my ODBC connection string with no luck. 

I get the error:   Traceback (most recent call last): File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\workbench\wizard_progress_page_widget.py", 
  line 192, in thread_work self.func() File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\migration_schema_selection.py", 
  line 175, in task_reveng self.main.plan.migrationSource.reverseEngineer() File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\migration.py", 
  line 369, in reverseEngineer self.state.sourceCatalog = self._rev_eng_module.reverseEngineer(self.connection, self.selectedCatalogName, self.selectedSchemataNames, self.state.applicationData) SystemError: DataError("('22P05', '[22P05] ERROR: character with byte sequence 0xe3 0x81 0x82 in encoding "UTF8" has no equivalent in encoding "WIN1252";\nError while executing the query (7) (SQLExecDirectW)')"): error calling Python module function DbPostgresqlRE.reverseEngineer ERROR: Reverse engineer selected schemas: DataError("('22P05', '[22P05] ERROR: character with byte sequence 0xe3 0x81 0x82 in encoding "UTF8" has no equivalent in encoding "WIN1252";\nError while executing the query (7) (SQLExecDirectW)')"): error calling Python module function DbPostgresqlRE.reverseEngineer Failed

How to repeat:
Try importing a UTF database with Japanese Characters from PostgreSQL

Suggested fix:
Allow the user to specify the client encoding

Looks like others have had related issues:

http://stackoverflow.com/questions/22688064/ms-sql-to-mysql-transition-using-workbench-err...

Please try development version 8.0.11 rc. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".