Sorry, I guess I wasn't clear in my last post. You can override what the "charset" is set to in the exported file by changing it in the template, as I described. But as I mentioned, the data will still be exported in the necessary encoding. In other words, if there is no data that NEEDS to be encoded in Unicode, it will NOT be encoded in Unicode.
Furthermore, the file code doesn't have the ability to specify an encoding. It can only specify ASCII or Unicode. If the data can be written using ASCII, it does so. If it cannot (if the data has characters that can not be encoded in ASCII), it switches to Unicode. However, it cannot specify whether to use UTF-8, UTF-16, or UTF-32. The system code makes that decision, and if I am not mistaken, I believe it defaults to UTF-16. Right now, there's no way to force the TD to save files in Unicode (but I'll put something down to look into this).
So, the change to the template you made (and I described) is not necessary. The exported file will either be encoded in ASCII or UTF-16, based on what is being exported. And the charset tag will be set appropriately.
The only way I can think of to force it to be exported in Unicode is to make sure something that is being exported requires Unicode. In other words, change a player name or the tournament description or other piece of data so that there is a Unicode character in it.