Aptos Font Fix?

[kentgorrell]

Does anyone know if MS have, or are about to, release a fix for the Aptos font rendering issue?
Or does anyone know a trick to setting it back to Calibri for Access.
If not then I'll write some code to change every control's fontname. sigh!

 

[The_Doc_Man]

Do a Google search with Gemini AI enabled and ask it "Is there a fix for the Aptos font problem?" There are a couple of things you could try.

One is to install the Aptos font on machines where it would be locally rendered. Another is when you create the PDF, if you have the option, tell it to include the font in the PDF file so that it will be available for local rendering. If you do that search, you might find something useful.

 

[kentgorrell]

there is plenty of info on Outlook, Word and PDFs but nothing on Access. It is the rendering in Access controls and datasheets that's causing me grief.

 

[isladogs]

The issue with truncated 'descenders' has been investigated by the Access team and appears to be fixed in Beta version 2510 build 19322.20006

I believe it only affected Aptos (Detail) 11pt - see https://www.isladogs.co.uk/bug-summary-2508/

So as a workaround you could change to e.g. 12pt or revert to Calibri by changing the default theme for new databases in Options | Client Settings.
Or change default control properties - see https://isladogs.co.uk/default-control-properties/
Or just wait till the fix works its way through the channels

 

[kentgorrell]

The main issue for me, is that the cursor appears one character to the right of where it actually is.
This affects Aptos <=11 but as you say, >11 works OK.
I can fix this in controls but for datasheet view, there is no option for fontname and I can't even get ds forms to respect my setting for font size.
I tried changing the theme to no avail.
Next test is to create a new db with the new Theme setting and import everything into it.

 

[isladogs]

Both issues were reported to the A-team by Karl in April with a reminder early in August
I'd not noticed problems with the cursor - only with descenders

Using Beta 2510 19322.20006, I have just checked for cursor position issues using Aptos 11pt in a datasheet but cannot replicate your findings.
So my presumption was that the issues were now both fixed in that build

However I have just discussed this with the Access team.
The issue hasn't been fixed but doesn't appear consistently
Indeed I have now found (and reported) a way of triggering it reliably as follows

Create a form datasheet with Aptos (Detail) 11 pt.
From th Home tab, change it to e.g. 14 pt.
Descenders are displayed correctly. Place the cursor on a letter and select it. Again OK

Using the Home ribbon, revert to 11 pt.
Descenders truncated and the cursor now appears midway between two letters

So for now, I suggest you change the font size to 12pt - the setting will stick for each datasheet
Or change the default font size to 12 pt in Options | Datasheet

 

[kentgorrell]

Thanks Colin, changing the font/fontsize using the ribbon resolves the issue.

 

[isladogs]

Glad I could help. The Access team are currently investigating the various issues.

 

[kentgorrell]

I've now added the Text Fomatting group to the Datashseet tab on the ribbon. This would seen the logical place for users to find it. I'm still a little intrigued as to how Aptos inflicted itself into these forms.

Calibri was the default font for Access/Office/365, that changed to Aptos at some point. Now that I'm aware, I'm looking at fonts in forms and seeing Calibri, Aptos and Tahoma and I'm left wondering how they got that way.

You wrote an article on changing the defaults for controls for each form which inspired me to write a procedure to loop through forms and change the detaults for each control. And of course we can have a Normal form from which new forms inherit these defaults.

But how did the new default (Aptos) enter the picture? Was this via a Theme or Form Template (Normal by Default) or did it wriggle in via some other undocumented route?

BTW: I tried to change my 365 channel with no success, CoPilot offered various methods including PowerShell scripts, none of which worked and the registry setting that was supposed to show the channnel, didn't. I usually use a batch file to install the specific build that I want but I couldn't get that to work with the Beta. Even tried with the ODT.