Shortcuts can be so Goth, you know?

by Michael S. Kaplan, published on 2006/08/25 11:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/08/25/723880.aspx


Cameron mentioned to me via the Contacting Michael... link:

In your blog posting "Getting rid of your extra yen" on 2005/12/28, someone made a comment that even after the locale was changed from Japanese back to English, "MS Gothic" (rather than Lucida Console) remained in the list of available fonts for the Command Prompt. Today, I ran into exactly the same problem/behavior that Nicholas Allen (the commenter) was describing. Then I realized that any shortcuts made to cmd.exe while the OS was in Japanese locale retained the MS Gothic font whereas cmd.exe itself always displayed the list of fonts applicable to the current locale. So there appears to be something sticky about the codepage that gets recorded in the Shortcuts to cmd.exe. Thought you would like to know.

Thanks,

Cameron

The post Cameron is referring to is here. :-)

This seemed like a worthwhile tip to share with people here, as it isn't terribly obvious that this is the case and I don't think I've ever seen it in the documentation....

 

This post brought to you by "¥" and "" (U+00a5 and U+20a9, a.k.a. YEN SIGN and WON SIGN)


# Heath Stewart on 25 Aug 2006 6:42 PM:

PIF files used to store configuration information for consoles, but in modern Windows platforms this is actually stored under HKEY_CURRENT_USER\Console, using the path to the executable - translating "\" into "_" - or the name of a shortcut.

# Michael S. Kaplan on 26 Aug 2006 5:10 PM:

I believe the principle is still the same though, right?

# charless on 29 Aug 2006 5:29 PM:

In my wanderings today throught the docs for IShellLink, I discovered that this is actually described on MSDN. The interface is IShellLinkDataList and one of the MS documented data blocks is NT_FE_CONSOLE_PROPS The console's code page.

go to newer or older post, or back to index or month or day