Re: Fonts in ACS

On Tue, May 10, 2022 at 1:32 AM John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

On Mon, May 9, 2022 at 6:42 PM Peter Dow <petercdow@xxxxxxxxx> wrote:

Then some googling to figure out how to add fonts to the JVM for ACS.
In my case, it was fairly easy - copy/paste the andalemo.ttf file into

C:\Users\Public\IBM\ClientSolutions\Fonts

then rebooted Windows to make sure the JVM restarted, and voila! Andale
mono now shows up in the ACS font selection drop down.

Thank you. That was very helpful. For the record, I didn't have to
reboot the whole system; I just exited all the way out of ACS and
restarted ACS, and that was enough to make the added fonts show up.

What's kind of funny is that I just now found this post from 2016,
titled "IBM i Access Client Solutions (ACS) fonts":

https://archive.midrange.com/midrange-l/201608/msg00263.html

Relevant snippet from there:

If someone can tell
me how to import fonts into ACS, I may give that a try.
I've already tried copying font files into

C:\Users\<myusername>\IBM\ClientSolutions\Fonts

but ACS doesn't seem to pick them up.

I don't know why it didn't work then. Maybe the old version of ACS I
was looking at back then behaved differently? Maybe that one *did*
require Windows to be rebooted? I dunno.

In that old post I also said:

I suspect it's really just the way ACS renders fonts that
makes them so crappy.

I do think ACS font rendering is still not as good as it could be
(because the very same fonts look better in other applications, at
least to some of us), but apparently it used to be even worse, because
a year after the above, I also wrote this:

https://archive.midrange.com/midrange-l/201708/msg00146.html

which suggests antialiasing was added to ACS later. (Which would also
create a plausible narrative for why the status line is *still* not
antialiased.)

John Y.