[fcx]

adarsh wrote on Jun 29 2007, 04:48 PM:

Hello,

We had some problem in our algorithm to differentiate ANSI and UTF8 encodings. Now we have improved our algorithm and released SQLyog 6.04 Please try this.

Yes, it works !

Thanks a lot

adarsh wrote:

This problem is there in notepad also ( in some situations) you can check from here.

http://weblogs.asp.net/cumpsd/archive/2004/02/27/81098.aspx

No problem in Notepad with my SQL source files.

I can reproduce the bug described in this page, except that the text isn't completly invisible but replaced by squares. Saved in ANSI and opened in UTF8.

adarsh wrote:

Thanks for reporting

Thanks for the job, and for WebYog !

[fcx]

Thanks in advance for the work.

peterlaursen wrote:

Maybe the problem is that the API has problems in detecting the character set/codepage correctly with short files

OK, but it works for shorter files…

[fcx]

Here's another example

[edit]reduced to less than 200 characters, it works[/edit]

Thanks

[fcx]

peterlaursen wrote:

1) what does it mean that you “reload” the file!

2) I write a “é” .. And you write in SQLyog editor? or in the grid of the DATA/RESULT tab?

3) you “open again” .. how??? You mean open in SQLyog?

I write my select query in the SQLYog editor, save with Ctrl+S, and reopen the file with Ctrl+O

peterlaursen wrote:

is there a SET NAMES statement in the file?

you do not SET NAMES from the editor yourself?

No set names.

peterlaursen wrote:

Now please attach such file!! Words won't bring us anywhere!

You may take an existing file form 5.19 and create a new one as well with 6.x!

Don't forget to tell which is which!

see below

peterlaursen wrote:

Create a dump of a table with a few tables and rows, export it, xip and attach here.

AND paste a screnshot of data should display (in whatever program you want)!

It's not a problem of data, only source code

Here's an example, in the same Tst.sql :

This works

Code:

— Ne doit pas faire
— é
select PARC.CONTYP
, PARC.CONSTA
, count(*)
from ParcNonCede PARC
, PLAN P
and PARC.CONSTA not in ('Stock', 'Détourné')
group by CONTYP, CONSTA
;

Only with more spaces, this doesn't work

Code:

— Ne doit pas faire
— é
select PARC.CONTYP
, PARC.CONSTA
, count(*)
from ParcNonCede PARC
, PLAN P
and PARC.CONSTA not in ('Stock', 'Détourné')
group by CONTYP, CONSTA
;

After save and open

Code:

— Ne doit pas faire
— é
select PARC.CONTYP
, PARC.CONSTA
, count(*)
from ParcNonCede PARC
, PLAN P
and PARC.CONSTA not in ('Stock', 'Détourné')
group by CONTYP, CONSTA
;

The file is attached with extension txt

Thanks for your help

[fcx]

It seems happened only with file containing more than 1 query.

Source files are well recognized as UTF8 with notepad or textpad.

[fcx]

peterlaursen wrote on Jun 22 2007, 04:48 PM:

Please tell with what program those files are created!

Probably the data is UTF8 encoded but the file itself is not.

The file was created by the previous version of SQLYog (5.15)

I tried to create a new one with the release 6.03. It's the same. I write a “é”, save and reload the file, it become “é”. I modify something else, save and erload and it's now “é”

peterlaursen wrote:

SQLyog 6.0 does both: encode data and the file tiself with utf8 – sqlyog encoded only the data in utf8 – the file itself was ANSI. Ypou will see the same with most versions of 'mysqldump'.

Accented characters are encoded using two bytes in utf8 – only one in ANSI.

It won't change existing files to change character set settings!

What is the porblem? Doesn't the file restore OK? or do you want the file to be editable and readable?

Try open in Notepad –> 'save as' and select utf8 encoding for the file. Next open again.

I try to save with notepad, both UTF8 or ANSI. With the both versions, SQLYog reacts in the same way.

[Author]

Posts