Not a bug  Importer icov source data encoding should be put to GUI


Importer scripts contain source data charset hardcoded like this:
protected $_charset = 'windows-1252';
To import data from any forum, that has it's content in any incompatible encoding (windows-1251 for example) we ought to fix encoding in the script. Otherwise we have all russian characters replaced by "?" signs after import.

Can we have this $_charset initializing from GUI, not hardcoded? Default value of this variable can be determined from the default charset of the source database btw.