'script_char_set' is applied incorrectly for migration scripts about mybatis HOT 7 CLOSED

And I prefer 'utf-8' to be the default rather than the platform's default 
encoding when 'script_char_set' is not specified explicitly.

Attached a patch against trunk revision 2390.

By the way, this is not a simple cosmetic change. Without this fix, migration 
scripts containing data in languages such as Chinese do not work and renders 
the migration tool useless in such context.

Please up the priority of this fix.

Attached a new patch against r3830.
I had to modify two existing test cases this time, but I believe the change was 
reasonable.
And with this version, the default charset is used when 'script_char_set' is 
not specified.

Thanks,
Iwao

Thanks for keeping this updated Iwao. 

This is indeed an encoding bug, once the File is opened with the wrong charset 
it is too late to fix it with new String(byte[], encoding)

I think it is better not to use utf-8 by default to avoid backwards 
compatibility problems.

Fixed in r3836

Eduardo, Thank you for committing the patch!