I believe what I had seen was pull #9339 commit 52e8c68 … though it looks like it’s not working yet.

AFAIK, that is separate from wingup commit 9b193fa.

I don’t have the time right now to check, but I thought I remembered seeing recently that there was a issue and/or commit to change at least some of the XML config files to UTF-8. I don’t know whether themes were a part of that “some” or not. (Also, maybe my imagination is running wild, and it’s not happening.)

But theme XML files usually don’t use anything besides ordinary ASCII characters so it really not that important IMO.

Ok, but it just seems to propagate ancient history. :-)
These files could just as easily be UTF8.

Isn’t using 1252 a bit, well, dated?

But theme XML files usually don’t use anything besides ordinary ASCII characters so it really not that important IMO.
This is critical for the localization XML files, they have a declaration like this:

<?xml version="1.0" encoding="UTF-8"?>

It’s already saved into a file.
If you locate the “themes” folder underneath the main N++ program folder, you’ll see a file called Twilight.xml. It contains any customizations you’ve made after selecting that theme.

Now, if your intent was to keep the original Twilight settings intact, and create your custom theme entirely separately, the proper path would have been to copy the xml file to a new name, e.g. Twilight2.xml and then select that theme and start modifying it. But of course you didn’t, and couldn’t, know that was the path in advance. :-)

Question for others:

BTW, I’ve just noticed that the themes xml files are all encoded as follows:

<?xml version="1.0" encoding="Windows-1252" ?>

Isn’t using 1252 a bit, well, dated?