MySQL Bugs: #120516: Data export fails with UMLAUT in table name

Bug #120516	Data export fails with UMLAUT in table name
Submitted:	21 May 11:23
Reporter:	Hans-Joachim Ballin	Email Updates:
Status:	Won't Fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.47	OS:	Windows
Assigned to:		CPU Architecture:	x86

Description:
The data export for tables (transactional data included) fails with the following error message:
12:05:46 Dumping DLDB (TblÜbungsstunden)
Running: mysqldump.exe --defaults-file="c:\temp\tmpi0nw5qn3.cnf"  --host=mysql-3d79e92b-taunusstein-1ea6.h.aivencloud.com --port=12839 --default-character-set=utf8 --user=avnadmin --protocol=tcp "DLDB" "TblÜbungsstunden"
Error executing task: 'utf-8' codec can't decode byte 0xdc in position 728: invalid continuation byte
Operation failed with exitcode None
Error executing task cannot access local variable 'result' where it is not associated with a value
12:05:46 Export of C:\Users\IEuser\Documents\dumps\Dump20260521 (5) has finished

I could isolate that the failing table data export is related to the fact that the table name contains at least one Umlaut (TblÜbungsstunden).

The MySQL Db is hosted as a managed service in the AIVEN cloud. A command-line access is not given at this time. 

Is there any option available in the MySQL Workbench to met 'utf-8' problem?

How to repeat:
Steps to reproduce 
1. Open MySQL Workbench
2. Go to "Server" > "Data Export"
3. Chose your Schema to be exported.
4. Chose your Tables (with Umlaut) to be exported.
4. Klick on "Start Export".

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.