MySQL Bugs: #73693: Exporting a model produces an SQL file that is not loaded in an SQL Editor tab

Bug #73693	Exporting a model produces an SQL file that is not loaded in an SQL Editor tab
Submitted:	24 Aug 2014 0:26	Modified:	12 Feb 2016 1:16
Reporter:	Fotis Kokkoras	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	6.1.7	OS:	Windows (Microsoft Windows 7 Service Pack 1 build 7601, 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
When I am exporting a model (File > Export > Forward Engineering...) and then trying to load the SQL code in a SQL Editor tab, Workbench pops up a dialog BOX saying "Unknown File Encoding" and asks to type the Character Set Encoding Name (promting with LATIN1). 

Notepad++ says that the encoding of the file is "ANSI as UTF-8" while is was supposed to be UTF-8 (at least that was the situation with past versions of Workbench). If I Copy-Paste the code from Notepad++ to the SQL Editor tab, the code is executed OK.

I converted the file to UTF-8 (from whithin Notepad++) but the problem remains. If that helps, I opened the converted file with PSPad (text editor) and found some strange bytes in the very begining:  ο»Ώ

How to repeat:
use the following file:

https://dl.dropboxusercontent.com/u/2690181/mvp_auxdb.mwb

export it to SQL and then try to load the file from whithin an SQL Editor tab.

Dialog

Attachment: encode.png (image/png, text), 157.95 KiB.

Thank you for the bug report.

Please try version 6.2

Please try version 6.3.6

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".

fixed

Posted by developer:
 
Fixed as of the MySQL Workbench 6.3.6 release, and here's the changelog entry:

The Forward Engineering SQL output sometimes contained a BOM character.

Thank you for the bug report.