Pedrober Posted March 3, 2023 Share Posted March 3, 2023 When I have to replace missing fonts and I set a font for substitution, the box becomes empty and it's necessary to redo the process with every font. It's a minor bug but... Quote Link to comment Share on other sites More sharing options...
Staff NathanC Posted March 3, 2023 Staff Share Posted March 3, 2023 Hey @Pedrober, I've replicated this issue on Windows and it has now been logged with the developers, many thanks. 🙂 Quote Link to comment Share on other sites More sharing options...
Pedrober Posted March 4, 2023 Author Share Posted March 4, 2023 Please note that this minor bug is also present in the Mac OS version. Quote Link to comment Share on other sites More sharing options...
Pedrober Posted March 16, 2023 Author Share Posted March 16, 2023 Not yet fixed in the last beta (1730). Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted March 16, 2023 Share Posted March 16, 2023 37 minutes ago, Pedrober said: Not yet fixed in the last beta (1730). Just a comment: It was not expected to be fixed. If Serif believed it fixed, then the release notes for .1730 would have mentioned it, and a post would have been made automatically to this topic saying it was fixed. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted March 21, 2023 Staff Share Posted March 21, 2023 The issue "Font Manager - Fonts disappear after selecting substitute" (REF: AFB-7442) has been fixed by the developers in internal build "2.1.0.1732". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.