Moving DECW$TERMINAL fonts to OS-X
JF Mezei
xset fp+ "tcp/chain.chocolate.ca:7100" so that the X server on the Mac
knows where to get the fonts needed by X terminal.
The problem I have found is that when the chain.chocolate.ca is
shutdown, Xwindow server on the Mac freezes because it can no longer
access that font server. Pain in the derri�re because to save
electricity, I now run the DS10L on demand only.
One option is to move the fons needed by decw$terminal to OS-X so they
would be local to OS-X and not need to be tied to the alpha, or change
the fonts used by DECW$TERMINAL to some that are local to the Mac.
I know how to get the font files from VMS. Not sure the .PCF are
platform independent though.
Question:
Ine the DECterm Windows Options, only 3 fonts are specified:
Big Font: -bitstream-terminal-*-*-*--18-*-*-*-*-*-*-*
Little font: -dec-terminal-*-*-*--14-*-*-*-*-*-*-*
German Standard Font: -dec-terminal-*-*-*-gs-14-*-*-*-*-*-*-*
Are these the onlt 3 fonts used by DECterm ? Does it synthetize other
variations of the VT font sets (double height, double width, reverse
video etc) ?
In other words, if I were to specify some existing fonts on the Mac,
would changing those 3 do the job ?
Where does it get the VT220 line drawing fonts from ? Are these
contained in the dec-terminal fonts ?
In the good old days, I had a package called Fontographer on my old mac
and was able to convert some VAX fonts over to be used by the X11
application on the old macclassics (forget what name it was).
Alas, fontographer doesn't run on OS-X, (although i guess I could fire
up sheepshaver to emulate the old classic environment) and I am not sure
if .pcf are usable.
Anyone been thourgh this before ? What route did they choose at the end
of the day ?
VAXman-
>Right now, to run DECW$TERMINAL displayed on my mac I need to issue the
>
>xset fp+ "tcp/chain.chocolate.ca:7100" so that the X server on the Mac
>knows where to get the fonts needed by X terminal.
>
>The problem I have found is that when the chain.chocolate.ca is
>shutdown, Xwindow server on the Mac freezes because it can no longer
>electricity, I now run the DS10L on demand only.
>
>One option is to move the fons needed by decw$terminal to OS-X so they
>would be local to OS-X and not need to be tied to the alpha, or change
>the fonts used by DECW$TERMINAL to some that are local to the Mac.
>
>I know how to get the font files from VMS. Not sure the .PCF are
>platform independent though.
Portable Compiled Format. They should be.
This is what I've done because of issues trying to set the font path to
a VMS font server when on-the-road.
>Question:
>Ine the DECterm Windows Options, only 3 fonts are specified:
>
>Big Font: -bitstream-terminal-*-*-*--18-*-*-*-*-*-*-*
>Little font: -dec-terminal-*-*-*--14-*-*-*-*-*-*-*
>German Standard Font: -dec-terminal-*-*-*-gs-14-*-*-*-*-*-*-*
>
>
>Are these the onlt 3 fonts used by DECterm ? Does it synthetize other
>variations of the VT font sets (double height, double width, reverse
>video etc) ?
Just get the 100dpi font off of VMS. SYS$COMMON:[SYSFONT.DECW.100DPI]
>In other words, if I were to specify some existing fonts on the Mac,
>would changing those 3 do the job ?
>
>Where does it get the VT220 line drawing fonts from ? Are these
>contained in the dec-terminal fonts ?
>
>
>In the good old days, I had a package called Fontographer on my old mac
>and was able to convert some VAX fonts over to be used by the X11
>application on the old macclassics (forget what name it was).
>
>Alas, fontographer doesn't run on OS-X, (although i guess I could fire
>up sheepshaver to emulate the old classic environment) and I am not sure
> if .pcf are usable.
>
>Anyone been thourgh this before ? What route did they choose at the end
>of the day ?
Move the SYS$COMMON:[SYSFONT.DECW.100DPI] to your Mac account. I use
/Users/VAXman/.fonts/100dpi/
Then, use mkfontdir on the /Users/VAXman/.fonts/100dpi/
Once this is done, xset fp+ /Users/VAXman/.fonts/100dpi/
This way is a world faster than xset fp+ to the VMS font server too!
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.
JF Mezei
> Move the SYS$COMMON:[SYSFONT.DECW.100DPI] to your Mac account. I use
> /Users/VAXman/.fonts/100dpi/
>
> Then, use mkfontdir on the /Users/VAXman/.fonts/100dpi/
>
> Once this is done, xset fp+ /Users/VAXman/.fonts/100dpi/
>
> This way is a world faster than xset fp+ to the VMS font server too!
>
Many thanks. This seems to work. Only moved the TERMINAL*.PCF files, and
DEC$TERMINAL still seems to work, able to display the various font
sizes that FMS can create.
Now, if I can figure out which file I should add the xset fp+ command
to, i'd be set. Ever since they changed X11 from Tiger to Leopard, I
haven't been able to figure out which file to put X commands in so they
get executed only ones (as opposed to whenever a process is created)
It used to be that I kept typing DIR and TYPE when on Unix. Now I am
finding myself typing LS and CAT when on VMS :-( :-(
VAXman-
THere is, in the system xinitrc, code to execute xset to add user's fonts
in ~/.fonts/fond.dir.
You can move your 100dpi fonts to ~/.fonts and run mkdir or edir the file
in /usr/X11/lib/X11/xinit/xinitrd.d/10-fontdir.sh to include:
[ -e "$HOME"/.fonts/100dpi/font.dir ] && fontpath = "$fontpath,$HOME/.fonts/100dpi"
This is what I've done... I like to keep my NON-Apple distributed X11
additions separate.
Bob Koehler
>
> It used to be that I kept typing DIR and TYPE when on Unix. Now I am
> finding myself typing LS and CAT when on VMS :-( :-(
If you have LSE installed, typing ls on VMS by accident can take
more that a second or so to back out from. 8(
Fortunately it is VMS, so if you "instinctively" try ^Z you will
get out.