Bug #107950 workspace does not restore if a script file has Hebrew letters in the folder nam
Submitted: 22 Jul 2022 21:11 Modified: 26 Jul 2022 11:46
Reporter: Zvi Barak Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.29 OS:Windows (10 PRO)
Assigned to: CPU Architecture:Any
Tags: hebrew, workbench, workspace

[22 Jul 2022 21:11] Zvi Barak
Description:
When my script file is in a Hebrew folder, workspace does not restore and gives an error on trying to open the file

How to repeat:
1. Create a folder with Hebrew characters
For example C:\Dropbox\לימודים\SQL\Udemy_Practice_Advance_course

2. Save a script file eg. index.sql in that folder

3. Start Workbench and open that script file, then close Workbench

4. Open Workbench again, using the same connection (In my case there is only one connection - local)
Then you'll get the error message
[22 Jul 2022 21:21] Zvi Barak
If I make a change to the script, but do not save it, the next time I open Workbench the script is opened but with * as file name

The info file in the folder 
C:\Users\drbarak\AppData\Roaming\MySQL\Workbench\sql_workspaces\Local_instance_MySQL80-1.workspace
 where one can see that Hebrew folder is missing
C:\Dropbox\לימודים\SQL\Udemy_Practice_Advance_course 
------------
type=file
filename=C:\Dropbox\
orig_encoding=
title=
show_special=0
word_wrap=0
caret_pos=7748
first_visible_line=0
[26 Jul 2022 11:24] MySQL Verification Team
Hello,

Thank you for the bug report.
Imho this is duplicate of Bug #87520, please see Bug #87520.

Regards,
Ashwini Patil
[26 Jul 2022 11:46] Zvi Barak
The answer I received is that the problem is a duplicate of bug 87520. However, it does not help me because the bug still exists. How do I overcome it?