Kerning issue in text editor on Windows 11

I just upgraded to a new laptop with Windows 11 and Scrivener 3.1.1. I’m seeing extra space after the letter “m” in Times New Roman 12 regular, double spaced. It’s not apparent at a zoom of 300% or 110%. I also do not see the problem in Word. Unfortunately, I’m required to use this font for my writing submissions. I’m looking for any suggestions. Thanks!

Versions

Windows 11 Pro version 21H2 (Build 22000.795)
Scrivener for Windows 3.1.1.0 64-bit
Times New Roman v7.01 TrueType from Monotype (probably installed with Windows)
Windows system-wide scaling set to 100%.

Hi Jasoncable.
Not a fix to your issue in itself, but, meanwhile, you could use another font and just revert to the font you need your text to be in at compile.

1 Like

Screenshots of the different zoom sizes: https://www.flickr.com/gp/jasoncable/57Jp8p6wsY

Perhaps tweaking this might help ?

But, as I said, if it comes out right when printing, I’d just use another font, and convert it to the desired font at compile. I wouldn’t worry about it. (I mean, I’d look for a fix, sure, but I wouldn’t put my work on hold for it.)

1 Like

I tried that setting it didn’t do anything. HOWEVER, you have me an idea. I didn’t realize that the publish profile would change the output font. That’s all I needed! No more TNR in the editor for me. Thank you so much for your help!

1 Like

Also at 100% view the issue is not apparent and that would be normal print output. The difference is there but subtle.

I don’t know if the number of editors who care about stuff like this is zero, but it’s pretty close.

1 Like

Seems great replies and success all around, especially . But remembering back when a lot of work was done to get font kerning to work well in Win10, what Vincent suggests here could well gain a variation that Win11 would be happy with.

I go along with preferring to let Compile do your deliverable fonts, entirely - to quote a memorable film badly, ‘It’s the only way to be sure…’ :slight_smile:

2 Likes