Sublime Forum

Build 3143 - does not take work with bitmap fonts on Windows 8.1 any more?

#1

Hi there,

yesterday I updated sublime text 3 to build 3143 on windows 8.1 and since then I can’t use the bitmap font: https://www.donationcoder.com/Software/Jibz/Dina/

Is this a bug or a feature - or did I misconfigure anything?

I know there is a true type version but a bitmap font is rendered more sharply on my system…

Regards & thanks for the gorgeous work!

0 Likes

#2

other people are experiencing the same problem

0 Likes

#3

Confirming same issue on Windows 7 and Windows 10. Moreover, I can’t get ST3 build 3143 to recognize ANY bitmap font.

0 Likes

#4

Confirm this on Windows 10 Education, Version 1703, OS build 15063.674, Intel i5-4590 BPU @ 3.30GHz, 16Gb Ram. ST Build 3143.

Come on ST folks, it’s been six weeks since this was mentioned on this thread, and since July 5th post by BourgeoisBear for prior build 3140, which means subsequent build 3143 retained this font issue (yes, it is an issue). Status please.

I’m reverting to previous build until this is fixed.

0 Likes

#5

Downloaded Build 3153 Portable and issue remains unresolved. Only bitmap font I can use as true bitmap is Courier New – all others, Dina, Sheldon, etc. will not load as bitmapped font.

Looking through the Build Notes I see the following that reference fonts:

BUILD 3152 - Fix font_style typo when parsing .sublime-color-scheme files
BUILD 3149 - Mac: Fixed incorrect text rendering when LCD Font Smoothing is disabled
BUILD 3149 - Linux: Fixed underscores getting clipped in some fonts
BUILD 3146 - Windows: DirectWrite is now used by default for all fonts
BUILD 3138 - Windows: Improved font selection logic
BUILD 3132 - Themes: Default to font.size = 11 when theme doesn’t specify size
BUILD 3131 - Fixed labels getting clipped incorrectly after changing theme_font_options
BUILD 3131 - Windows: Added support for no_antialias font option when using DirectWrite
BUILD 3130 - Added setting theme_font_options to control font rendering of UI elements
BUILD 3130 - Windows: Improved fallback font handling in UI elements
BUILD 3128 - Fixed incorrect auto complete font size in Windows and Linux
BUILD 3127 - Improved font selection on all platforms, allowing selection of different weights by name
BUILD 3127 - Font geometry issues that prevent bold or italics are now printed in the console
BUILD 3127 - Windows font rendering defaults to DirectWrite unless using Consolas or Courier New
BUILD 3127 - OS X 10.11 and macOS 10.12+ default to using San Francisco for the UI font
BUILD 3127 - minihtml now respects font options from the settings

Perhaps it was Build 3127 that introduced this issue. Can “Font rendering default to DirectWrite” be the culprit? Note this is also indicated in Build 3146 for some reason.

0 Likes

#6

Yes, build 3127 introduced the issue and I have not gotten back to trying to figure out why Windows would be returning false when querying bitmap fonts. Previous to 3127 we just sent the Windows API a font name and hoped for the best. Now we use an API to check so we can tell the user if we couldn’t find the font. This was necessary for certain minihtml features also (font stacks).

Hopefully I’ll get a chance to look into this in one of the next few dev builds.

0 Likes

#7

Thank you :slight_smile: Very much appreciate the update.

I was just going to post that Build 3126 does not have this issue, which obviously you and your team know.

0 Likes