Antwagonist Posted May 12, 2021 Share Posted May 12, 2021 As the title explains whenever i change the font size the comma dissapears. it only happens when i select a font size from the dropdown menu. It's probably not good practice to use mm as a font size but it's there. Before: After changing the font size: I first noticed this comming from 1.8 to 1.9 update. hope this can be fixed, it gets a little anoying after changing sizes a lot. Otherwise happy with affinity! Quote Link to comment Share on other sites More sharing options...
Komatös Posted May 12, 2021 Share Posted May 12, 2021 Hello and welcome to the forum Go to the preference --> Surface. Here, "Specify text size in points" should be ticked. Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296) AMD A10-9600P | dGPU R7 M340 (2 GB) | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) Affinity Suite V 2.4 & Beta 2.(latest) Better translations with: https://www.deepl.com/translator Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF Life is too short to have meaningless discussions! Link to comment Share on other sites More sharing options...
Antwagonist Posted May 12, 2021 Author Share Posted May 12, 2021 Thank you, and thanks for the reply. But yes, i know of this. I use mm units to design for cnc machining where i want to know the exact font size in metric. Manually it still works fine but i just wanted to point out this is a thing. Quote Link to comment Share on other sites More sharing options...
Komatös Posted May 13, 2021 Share Posted May 13, 2021 (edited) OK, I can confirm the bug. The font size does not use the system setting for the decimal seperator. For me, the decimal point is displayed although the system uses the comma here. The result is that the decimal separator is ignored and the value appears as an integer. The bug also affects Photo and Publisher. Edited May 13, 2021 by Komatös Information extended. Antwagonist 1 Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296) AMD A10-9600P | dGPU R7 M340 (2 GB) | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) Affinity Suite V 2.4 & Beta 2.(latest) Better translations with: https://www.deepl.com/translator Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF Life is too short to have meaningless discussions! Link to comment Share on other sites More sharing options...
Staff Sean P Posted May 13, 2021 Staff Share Posted May 13, 2021 Hi Antwagonist, This is caused by the font list not correctly showing , as a decimal separator and instead is still using . which is getting eaten up when applied. I'll get this raised and passed onto development. In the meantime you should still be able to specifiy the size yourself using , as a separator. It is just when choosing from the list that is the issue. Antwagonist 1 Quote Link to comment Share on other sites More sharing options...
JokeRat Posted May 26, 2021 Share Posted May 26, 2021 I second this issue. It's since the/one of the new updates, it worked perfectly fine in 1.8 Interestingly on my end it's exactly the opposite as Kommatös showed, as my system default as decimal separator is . and Affinity has ALL* my decimals with , * this means that this bug also effects the transform input fields which I use A LOT in my daily workflow in combination with the numpad. So this bug hits me pretty hard, unfortunately. Quote Link to comment Share on other sites More sharing options...
Komatös Posted May 27, 2021 Share Posted May 27, 2021 Have you selected German or German ( Swiss ) in the language settings of Windows? Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296) AMD A10-9600P | dGPU R7 M340 (2 GB) | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) Affinity Suite V 2.4 & Beta 2.(latest) Better translations with: https://www.deepl.com/translator Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF Life is too short to have meaningless discussions! Link to comment Share on other sites More sharing options...
JokeRat Posted June 3, 2021 Share Posted June 3, 2021 Sorry for the late reply. These are my settings: Quote Link to comment Share on other sites More sharing options...
JokeRat Posted November 2, 2021 Share Posted November 2, 2021 Since several release iterations have past now and the bug is still there, did you get any feedback from development when/if there are any plans to fix this? And unfortunately I can't downgrade to 1.8.5 as I have a lot of files to work with which are saved in newer versions of AD. Quote Link to comment Share on other sites More sharing options...
JokeRat Posted March 16, 2022 Share Posted March 16, 2022 *Bump*. This is still an issue that effects my daily work immensly. Any plans when this will be fixed? Quote Link to comment Share on other sites More sharing options...
Antwagonist Posted November 14, 2022 Author Share Posted November 14, 2022 So i just got affinity designer v2. Really happy with the new features, they are going to help me immensly! But i couldn't help myself to go to the font size box to check if this issue remained... and it does. Is is possible to fix this in v2? JokeRat 1 Quote Link to comment Share on other sites More sharing options...
JokeRat Posted November 17, 2022 Share Posted November 17, 2022 Yes, this is slowing my daily workflow DRASTICALLY. I was hoping that at least in V2 this issue will be gone, but I got dissapointed. It's even more frustrating as it worked in 1.7 (or 1.8 even?) so it should (hopefully) be easy to reproduce/locate the error. This is driving me nuts for over a year now. 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.