Joachim_L Posted August 16, 2019 Share Posted August 16, 2019 Title and attached image say all. Not just a render problem in Publisher, it looks the same in exported PDF. Quote ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed Link to comment Share on other sites More sharing options...
matisso Posted August 20, 2019 Share Posted August 20, 2019 Does it persist if you change the font? Perhaps something has been overlooked in the font file itself. Quote Link to comment Share on other sites More sharing options...
Joachim_L Posted August 20, 2019 Author Share Posted August 20, 2019 31 minutes ago, matisso said: Does it persist if you change the font? Perhaps something has been overlooked in the font file itself. Correct, not all fonts do have this problem, but some like: Corbel, Milo, Gabriola, Minion Pro, Myriad Pro, Source Sans Pro and Tahoma. These are the ones I found in my installed fonts. Quote ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed Link to comment Share on other sites More sharing options...
matisso Posted August 20, 2019 Share Posted August 20, 2019 That’s pretty odd, I would assume this would happen in rather poorly designed fonts. Maybe the reason is somewhere else, or maybe the ones you mentioned do have bugs (not entirely impossible). However, given how popular Minion, Tahoma and Myriad are, it’s hard to assume no one else noticed it before using software other than Affinity, so maybe there’s indeed a glitch… Quote Link to comment Share on other sites More sharing options...
kenmcd Posted August 21, 2019 Share Posted August 21, 2019 @Joachim_L Please list some fonts you have tested which do not show this issue. Thanks. I have looked at the fonts you listed above and there may be a common thread. Quote Link to comment Share on other sites More sharing options...
Joachim_L Posted August 21, 2019 Author Share Posted August 21, 2019 Too much work. I add a screenshot instead. Apart from a few fonts recently added like Milo, LCD and some more coming from CS6, the fonts were already installed on a brand new Windows 10 PC. Quote ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed Link to comment Share on other sites More sharing options...
Dave Harris Posted August 21, 2019 Share Posted August 21, 2019 I can reproduce it with Tahoma. I've not tried anything else. It happens because the font gives the soft hyphen character (U+00A0) the same glyph index as a normal hyphen (U+002D). It then kerns 't' with the normal hyphen's glyph index, effectively specifying that 't' kerns with soft hyphens. Arguably the font should not give soft hyphens any outline at all; we already have code that prevents them being drawn, but they were still being passed to the OpenType engine. Looking into this I've found several other issues where kerning or other OpenType rules are affected by things they shouldn't be. For example, if you have an index mark between "AW" it won't kern. If between "fi" it won't form a ligature. A floating object pin will also make a difference. I've logged this to be fixed in a future update. Thanks for reporting it. matisso, Patrick Connor, Joachim_L and 1 other 4 Quote Link to comment Share on other sites More sharing options...
kenmcd Posted August 21, 2019 Share Posted August 21, 2019 8 hours ago, Dave Harris said: I can reproduce it with Tahoma. I've not tried anything else. It happens because the font gives the soft hyphen character (U+00A0) the same glyph index as a normal hyphen (U+002D). That was part of the "common thread" I was seeing - the multi-mapped glyphs. Also take a look at Source Sans Pro where it is not multi-mapped but the softhyphen is using the metrics from the hypheminus. Per above this also causes this issue. Quote Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted November 1, 2019 Staff Share Posted November 1, 2019 We believe the issue "Soft hyphens affect kerning" has been fixed in 1.8.0 [Publisher beta is currently available if you care to check]. Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon 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.