Special Character display in menus

[klownboy]

I just upgraded my Windows 7 (x64) computer to Windows 10 and I'm experiencing a few issues unlike the upgrade of my Windows 8.1 machine which went great. Some special characters like the bell symbol I use in menus do not display (see pic). I know I've experienced something similar before but everything was fine before going to Windows 10. I include another capture from Help | Various info. I tried changing fonts. I'm currently using Segoe UI 9 regular as I was previous to the 10. I haven't changed the text files as far as how they are saved. Most of my XY scripts are saved in ANSI encoding. I just checked the other computer and it also doesn't display the bell symbol whereas it did before on Windows 8.1. The code page info is the same on both computers. Any ideas or thoughts on what may have happened? Thanks.

Side Note: Windows 10 is also insisting on running Defender even though I have Norton anti-virus installed and it's properly recognized by Windows as being installed - really nuts - after turning Defender off, on reboot it's back on along with a working and recognized Norton. I see others are having similar issues. I don't know who to blame on that issue Norton or Microsoft. I was getting 19 second start-up times for XY. I get 300ms start-up times on my other computer.

bell_not displayed.jpg

bell_not displayed2.jpg

[bdeshi]

No suggestion for hollow bells, but

"Side Note: Windows 10 is also insisting on running Defender" - that's a "feature" of Windows 10, like automatic updates. If you have Windows 10 Pro, the group policy editor (run gpedit.msc) can disable Defender (and auto-updates) permanently. Computer Config > Administrative templates > All Settings > Type-ahead-Find "turn off windows d"

[klownboy]

It's very strange because I do get the stars like in the rating script/catalog, but the solid bell in the center of a line does not display instead I get as shown in the capture (i.e., the rectangular open block).

Thanks Sammay, I read the postings concerning gpedit.msc yesterday. Unfortunately I had Windows Home Premium on this computer and Windows 10 upgraded me to Windows 10 Home. I wouldn't mind so much, but I had purchased (rather cheaply ($39) directly through MS) an upgrade for Windows 8 Pro for use on this Windows 7 Home Premium computer and never ended up using it on the computer in question. I never gave it a thought about the fact that it would only upgrade this one to Windows 10 Home not Pro. Oh well. I made drive images of my C: and D: drives before the upgrade so I can always plop Windows 7 back on. Which I should consider doing even if just to upgrade to Windows 8 Pro. So in the end I end up with Windows 10 Pro as I have on my other computer...that also means I have to upgrade 8 to 8.1 also...yikes.

By the way as of this morning (so far), on cold boot-up, it seems as if the virus situation may have rectified itself. I have Norton anti-virus showing as up and running and Defender is properly turned unlike before when it insisted on being on with Norton....and resulted in 18 plus seconds for XY to load...it was really sad.

[bdeshi]

Code: Select all

::text asc('a'); //ALT+numpad 9,7; returns 97. OK

Code: Select all

::text asc('•'); //ALT+numpad 7; but returns 8226! (bullet)

I saw those rects on the Store app slider arrows, like in this image, but back when the arrows were on a black bg.

It was fixed in an update.
besides (don't know if it's relevant), I read that the Segoe fonts, and symbols, were changed/updated/shuffled in 10. Maybe this springs from there.
Or, more likely, WinX does something different in codepage handling.

Meanwhile, replacing the rects with alt+numpad7, and saving in UTF with BOM, or even ANSI, seems to take care of the issue.

[klownboy]

Thanks Sammay. I'll check it out further. I'm supposed to be getting a call from a 'higher' level Microsoft rep today concerning my issue above. I upgraded a computer from Win7 Home to Win8 Pro, but had 163 updates to install before I could do the update to Win8.1. The updates continually end up failing even when I apply a limited number at a time. All just to finally arrive at Win10 Pro instead of Home. Luckily I made images of Windows 7 and also have a Win10 image (Home). I do have Win10 Pro on another computer and it looks great though I do have the issue above. I did change some of the xys files to different encoding and got my big fat bullets (007) back. In general, is there a preferred encoding for xys files or does it matter? Maybe only when publishing does it matter. I was usually using ANSI. Yes, MS is coming out with updates quite often. Thanks.

[bdeshi]

I generally use UTF-8 for my scripts. UTF-16 and ANSI also works. I don't have know much in this regard (didn't have to) .

I hope you get to Win10 pro without further complications. I know how aggravating it can get, especially with all that OS juggling.

[klownboy]

Thanks Sammay for the info. I never did get the call back yesterday from the higher level MS tech rep...maybe today.