<Chris Lamey>
Not Registered
From: N/A
Messages: N/A
|
 |
cmd.exe font? |
|
|
|
Hi all,
I really like ProFont in Vim on Win2k, thanks to all who did the work! However, I like my shell and editor to have the same font and unfortunately cmd.exe doesn't list ProFont as an option. I know cmd.exe is pretty stringent in the fonts it will use, but I don't know much beyond that.
So I guess I'm wondering if ProFont is close to being ok for cmd.exe and if anyone has a version of ProFont that cmd.exe will use? I'm using the FON version, if that makes a difference.
Cheers,
Chris
|
Tobias
Administrator
From: the vaults
Messages: 89
|
 |
cmd.exe font? |
|
|
|
Some time ago, we had a similar ProFont problem (the "monospaced bug") which was fixed by changing some header information in the ProFont .fon file.
Maybe there's another header information that must be changed to get ProFont to work with cmd.exe?
Again, my advice is to get a copy of Softy font editor:
http://www.pctip.ch/downloads/dl/23412.asp
... and then start tinkering.
Sorry I can't offer a better solution. But if you succeed, it'd be nice if you post again here to tell us what you did...
Tobias
~~~~~~~~~~~~
What can't we face if we're together?
|
<Chris Lamey>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
OK, thanks. I'll give it a shot.
|
<Chris Lamey>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
This document is helpful for understanding what fonts can be used by the Windows 2000 console (cmd.exe):
http://support.microsoft.com/default.aspx?scid=kb;en-us;247815
Using that as a starting point, here's what I did to get ProFont in both Vim and cmd.exe (cygwin bash.exe) on Windows 2000 SP4. I had to do this because Vim didn't like the default TTF ProFontWindows and trying to modify the headers in the FON version causes problems in Vim.
- Download both the FON and TTF ProFonts
- Unzip the FON version and drop that into %WINDIR%Fonts This is the version for the applications
- Unzip the TTF version
- Open the TTF version in Softy
- Change all instances of the string ProFontWindows in all the Platform->Names controls to TTProFontWindows
- Save As a new TTF file
- Drop new TTF file in %WINDIR%Fonts This is the version for the console
- Follow the Microsoft technote and edit the registry to add TTProFontWindows to the ConsoleTrueTypeFonts key
- Open up cmd.exe/bash.exe and TTProFontWindows will be an option in the Font select box
The basic idea is to make the FON version available to applications and to make a modified True Type version with a different name for the console. Putting both the TTF and FON versions in %WINDIR%Fonts causes name collisions, so renaming one gets around that problem. And since fonts aren't automagically picked up by console, you have to make registry edits to get it listed as an option.
|
Tobias
Administrator
From: the vaults
Messages: 89
|
|
cmd.exe font? |
|
|
|
Boy, thanks a LOT for this detailed description!
And now, have fun with ProFont in all your apps. :-)
btw, I've really got to fix that nasty bug that the forum scrambles those URLs containing special chars...
Tobias
[edit: o.k., the URL bug seems to be fixed now]
~~~~~~~~~~~~
What can't we face if we're together?
|
<Scott>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
The procedure outlined above didn't work for me, for two reasons. First, the TrueType version of ProFont really looks terrible at small sizes. Second, and more importantly, though I was able to get TTProFont to show up as a font choice in Command Prompt Properties, choosing it didn't have any effect. Command Prompt windows would still use Lucida when I opened them.
The good news is that I was able to get the FON version of ProFont working with Command Prompt windows with only a little effort. Open the FON version of ProFont in Softy. Be sure you open the exact size of the font you will want to use in your Command Prompt windows, as your edits will only affect one size of the font (I chose the 11 point size). Go to the Font->Header dialog, and change the Character Set radio button selection to OEM from ANSI. Save your changes, exit Softy, and drop your modified FON file your Fonts folder. Now open a Command Prompt window and open the Properties page. On the Font tab, select Raster Fonts, and scroll through all of the size choices, looking carefully at the example text. One of the sizes will actually be ProFont (my 11 point example became 6x8 in the Command Prompt Properties). It should be easy to tell from the others, as it will be the only one that looks good. Select it and OK your way out of the Properties page, and your cmd.exe window will be using a good-looking, raster version of ProFont.
It's worth noting that, according to the Knowledge Base article linked above, this procedure will not work on Far East versions of Windows. As ProFont does not implement a Far East character set, you'll be stuck with the TrueType version of ProFont on Far East versions of Windows.
I'll end with a question. It appears that ProFont actually implements an OEM character set and not an ANSI character set. It has boxdraw characters and such where a true ANSI character set would have latin diacritics. I'm no font expert, but I think it would be more correct to mark all of the raster (FON) ProFont sizes as being OEM character sets. Also, it would make the FON version of ProFont "just work" for Command Prompt windows on non-Far-East versions of Windows. Would it be worth making a ProFontWindows v3 FON version where the fonts are marked as OEM character sets?
|
<Scott>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
Er, oops. Disregard my entire previous post. That procedure does not make ProFont available. There are just some variations of the "Terminal" font that look similar to ProFont. Sigh.
|
<parameter>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
The above is not working too well for a few of us here. If others have gotten this to work it would be encouraging to see a 'worked for me comment'. Also it would be great if someone got it working after having trouble with it (so you could explain what you did to overcome the last hurdle). Can we get the fixed-up TTProFont on the downloads to we can skip mistakes editing the font file? Thanks for your work on this so far.
|
<Mikael>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
<Chris Lamey>,
Got the following from http://blogs.msdn.com/tonyschr/archive/2004/02/03/66552.aspx :
Quote:
The tip of the day today is adding extra fonts to use from the command line - stop being limited to “raster fonts” and Lucida Console! The trick is to add string values under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont. Each string value must increment the 0's, for example:
0 (reg_sz) Lucida Console
00 (reg_sz) Andale Mono
000 (reg_sz) Your Monospaced Font
...
You get the idea, although not all monospaced fonts work. Yes, as discoverable and usable as the command line itself! :-P
Try it, it might work...
|
<Mike Agney>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
I had some success with making the .FON file work. What I did is this:
* Opened PROFONT.FON in Softy and selected the 11-point font.
* Changed the header information to Font Family: Modern and Character Set: OEM (and changed the font name to ProFontTerminal).
* Saved the modified font to PROTERM.FON
* Repeat the above three steps for the point sizes I wanted (I only did 10-point, 11-point, and 12-point).
Then copied the resulting PROTERM.FON to the Fonts directory.
Result: ProFontTerminal did not show up in the list of fonts in cmd.exe. HOWEVER, three new entries showed up in the Raster Fonts section. When I selected them, they were ProFont variants!
|
<Erik>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
The registry solution worked just fine -- except it requires the TT font to be used, not the postscript ... and it doesn't quite work at all sizes ... but, handy for how well it does work, anyway. I suppose if I really wanted to be anal about it, I'd just write a wrapper for cmd.exe and perl and use ProFontWindows in that .... in fact, I might do just that ... I've been looking for an excuse to build something with the mozilla framework (and I wonder why I never get any paid work done)
- Erik
|
<lost>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
Please explain more about font file hacking in softy?
I dont know what to do when I open the font~~ where to change name,and ,,,,,?
|
<hennes>
Not Registered
From: N/A
Messages: N/A
|
|
cmd.exe font? |
|
|
|
<lost>,
i got the true type fonts to show up in the selection box but i cant use them :(
anyone with success?
|
