Skip to main content

Change font for non-legacy command prompt in Windows 10 with non-ASCII charset - Properties vs default values?


I am fiddling with Windows 10 new command prompt. I am with code page 936 (GBK).


I say "new" because I see in the Properties of cmd that there's a check to run legacy command prompt (need restart), by default unchecked, so I guess this one I am using is "newer".


The question is, searching the web only gives me some ways to add a font in registry to make legacy cmd to recognise it and show in "Properties"/"Default values" settings, like this:


http://www.techrepublic.com/blog/windows-and-office/quick-tip-add-fonts-to-the-command-prompt/


It mentions to add a font entry to the shown location in:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont

to make Windows aware of this font. I note that the fonts already listed there are the same ones that I can see in legacy cmd. In normal cmd I see more fonts.


enter image description here


Note that in the picture I opened a legacy cmd prompt, with some Terminal fonts, and in the Properties setting dialog, the fonts from which I can choose are Consolas and Lucida Console, same as in the registry.


And, if I switch to normal cmd, there are two cases:



  1. If I choose to edit "Properties", I see less fonts and the change works.

  2. If I choose to edit "Default values", I see more fonts but the change does not take effect.


In Properties:


enter image description here


I can choose between Yahei Consolas Hybrid and other fonts here, and cmd respects my settings and change the font immediately.


In Default values:


enter image description here


You can see more monospaced fonts here, like Dejavu Sans Mono, Monaco and so on, but you cannot make cmd change to these fonts.


I don't know the difference here, but it just doesn't make sense. Some settings that cannot be respected should not exist, not to mention the confusion caused: "Properties" and "Default values" are identical.


What I want, is to change the font in normal cmd to be Monaco, or Dejavu Sans Mono. If not possible, in legacy cmd.


And by the way, if someone can clarify the difference between "Properties" and "Default values", it would be great.



Answer



Now I find the answer, thanks all for helping. I will not accept my own answer in a week to see if anyone can post a better answer.


The problem lies in the code page. I set my default display language for Windows 10 to be Simplified Chinese, with GBK code page (936). So, in cmd windows, the system intends to show all the information in Chinese. Actually, we see that in the first images I posted in the question, the beginning lines of help information are shown in Chinese.


To show something in Chinese, you have to find a proper font to provide the hinting information for Chinese characters. Apparently, Windows checks all fonts beforehand to see its support to current code page characters. When it sees that the set font has no Chinese support, it will abandon this font and falls back to the default font. Also, it will get rid of this font from the font setting list in the Default panel. Yahei Consolas Hybrid supports both English and Chinese, so it can be shown in the list in Default and Properties settings. Monaco and Dejavu, however, disappeared from the Default panel, but remain in the Properties panel.


Why does it not clear the Properties font list, too? Because as the comments say, "Properties" applies to the current cmd windows/session, while "Default" settings controls all the subsequent cmd sessions, e.g., more global. It ensures that if the user changes the code page in the run-time, it has not to do the font list checking again for Properties, and the user can change font directly. That's exactly what happens in my case. I must say that Windows has done much background work here.


You can see in the following screenshot that I changed the code page with chcp 1252 and the font change takes effect immediately. It's Monaco now.


enter image description here


So, the question turns to: "How to change the code page upon starting a cmd window?" And I found a very useful question:


Change default code page of Windows console to UTF-8


And I simplify the change to:



  1. Create a .reg file, name it as you wish.

  2. Copy these lines into the file and save.


Just type:


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor]
"Autorun"="chcp 1252>>nul"

1252 can be other values. >>nul is to avoid printing


Active code page: 1252

every time you launch cmd.



  1. Run the file to import the settings.

  2. Run cmd. Now you can set your font easily in Properties. (I note that if you run from a link in desktop, the font is Simsun, but if you run from anchor in the task bar, it's Yahei Consolas Hybrid. I don't know why. But you can just change the font.


Set the default font in Default doesn't work for subsequent sessions of cmd, though. It still falls to Simsun, so I cannot achieve "Open cmd and with Monaco font". I think it is because Windows checks current language code page with fonts, not the "autorun" code page with fonts., so changing the default language can be working but that's not what I want. I am still with this topic.


Comments

Post a Comment

Popular Posts

How do I transmit a single hexadecimal value serial data in PuTTY using an Alt code?

I am trying to sent a specific hexadecimal value across a serial COM port using PuTTY. Specifically, I want to send the hex codes 9C, B6, FC, and 8B. I have looked up the Alt codes for these and they are 156, 182, 252, and 139 respectively. However, whenever I input the Alt codes, a preceding hex value of C2 is sent before 9C, B6, and 8B so the values that are sent are C2 9C, C2 B6, and C2 8B. The value for FC is changed to C3 FC. Why are these values being placed before the hex value and why is FC being changed altogether? To me, it seems like there is a problem internally converting the Alt code to hex. Is there a way to directly input hex values without using Alt codes in PuTTY? Answer What you're seeing is just ordinary text character set conversion. As far as PuTTY is concerned, you are typing (and reading) text , not raw binary data, therefore it has to convert the text to bytes in whatever configured character set before sending it over the wire. In other words, when y...
Post a Comment
Read more

linux - Extract/save a mail attachment using bash

Using normal bash tools (ie, built-ins or commonly-available command-line tools), is it possible, and how to extract/save attachments on emails? For example, say I have a nightly report which arrives via email but is a zip archive of several log files. I want to save all those zips into a backup directory. How would I accomplish that? Answer If you're aiming for portability, beware that there are several different versions of mail(1) and mailx(1) . There's a POSIX mailx command, but with very few requirements. And none of the implementations I have seem to parse attachments anyway. You might have the mpack package . Its munpack command saves all parts of a MIME message into separate files, then all you have to do is save the interesting parts and clean up the rest. There's also metamail . An equivalent of munpack is metamail -wy .
Post a Comment
Read more

ubuntu - Why does my USB hdd returns SG_IO: bad/missing sense data?

I am able to boot and run commands from external USB hdd; the message in question appears for about 45 seconds then booting continues. GRUB2 is installed on internal HDD. When choosing to boot directly to /dev/sdb the message doesn't appear, however boot time is about the same as booting to internal HDD. /dev/sdb: Timing cached reads: 1018 MB in 2.00 seconds = 508.97 MB/sec Timing buffered disk reads: 80 MB in 3.03 seconds = 26.37 MB/sec pfeiffep@de:~$ sudo hdparm -i /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 10 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_GET_IDENTITY failed: Invalid argument Gparted correctly identifies the drive as SAMSUNG MP0402H. Any ideas how to remedy the HDIO & SG_IO messages?
Post a Comment
Read more

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...
Post a Comment
Read more