Problem when opening SQL file having utf8 without BOM
When opening sql file containing Cyrillic symbols and being in the utf8 encoding without BOM, the encoding is determined as win1251 and it seems to be not possible to change it.
Тим
shared this idea
You would need to select the ‘Unicode – (UTF8)’ encoding in the ‘Encoding’ dropdown menu of the ‘Open File’ dialog.
-
Christophe Torre
commented
Hello,
I've the same problem. My sql file is in UTF-8 (Without BOM) when i check it in Notepad++. When i open it in DBForge Studio Express (Oracle), with the encoding UTF-8 (65001), i've the problem again.
Any solutions ?
-
yg
commented
Cyrano is right, your solution is too time consuming for common import scenarios from mysql dumps. Please add this a setting in preferences
-
Cyrano
commented
Ok, it's ok.
But this way is not really Usefull. May i suggest some improvement : move this choice in the preferences should be a great choice, as in many other softwares. Or may be as in Notepad++, you have a default choice in preferences, and for each opened file, you can choose the encoding in the menu after opening. As it, you can open a file with the Studio from the explorer. Other wise, you must open the file directly from the studio and chose the right encoding before opening
-
Cyrano
commented
Hi,
unfortunately, i've the same problem, any answer should be welcome...