That is strange, but glad to hear it! We're aiming to make this better in the future!
Strangely this is now working fine. I didn't do anything except view the language settings.
Thanks for the answer. The work-around is a bit of a red herring though, as the language I want for non-unicode programs is... unicode. But its not an option. I guess I could set it to Greek but then everything else would be wrong. Thanks anyway.
Hi @andybev,
Currently, FME handles attribute names with systems default encoding and doesn't have the same encoding application as the data values, which is why the values are displaying correctly but the header row is not. Our team is working hard on extending that functionality for the future (in either a future 2019 release or 2020) so that the attribute names will be handled correctly. The issue is FMEENGINE-56578. Thanks everyone for raising the issue and for your patience.
In the meantime, a potential workaround is to set your systems encoding on your computer to the desired encoding. You can find that your Region and Language settings on Windows, and you can set the Country or Region, Language, and in Administrative Language Settings, the language for non-Unicode programs, and see if that might work for you.