currently the way to change project encoding is by having at least
one project created and then changing its encoding in the props
of that project - then all next created projects will use that encoding,
until that or some other project does the same kind of change in properties.
although the typical user model might be that if they want to change
project encoding, they will do it once in a session, and all of their
projects will be using that one changed encoding.
but there are some users who might need to use multiple project encodings,
and also users might not want to in any case need to go to effort of changing
some encoding of some existing project, in order to impact encoding of next
projects vs just having some global property in options.
This was already discussed and rejected. I cannot find the Issuezilla number at the moment. The logic is that (1) we do
not want additional things to configure in Options; (2) you can easily change the encoding of any existing project with
the existing GUI; (3) the encoding for new projects is just a guess, and if you don't like it, change it on that project.