Barrowman Posted March 4, 2020 Share Posted March 4, 2020 Hi Very weird thing, I'm using this font called "Rockness", and it displays perfectly fine in Adobe Suite yet when I try and type the same thing in Affinity I get this. Doesn't really matter what I type, the whole character mapping seems all over the place. Frustratingly I'm not having to go back to Adobe CS just to type out this line. Any explanation appreciated. Thanks in advance. Quote Link to comment Share on other sites More sharing options...
lacerto Posted March 5, 2020 Share Posted March 5, 2020 (...) Quote Link to comment Share on other sites More sharing options...
Barrowman Posted March 5, 2020 Author Share Posted March 5, 2020 Hi Thanks. It’s OTF & on the Mac and I tried switching the obvious type characteristics, the weird thing is that it’s just that font . I just can’t see how/why Adobe renders it correctly when it even shows up oddly (like Affinity) in the font manager as well. Quote Link to comment Share on other sites More sharing options...
lacerto Posted March 5, 2020 Share Posted March 5, 2020 (...) Quote Link to comment Share on other sites More sharing options...
Barrowman Posted March 5, 2020 Author Share Posted March 5, 2020 Hi, it doesn't matter how I do it, if I cut and paste from Indesign, or open an IDML, even importing a PSD, it changes it, it's very odd and Caps Lock isn't the problem. What I don't understand is why Adobe can display it correctly. Quote Link to comment Share on other sites More sharing options...
Barrowman Posted March 5, 2020 Author Share Posted March 5, 2020 8 hours ago, Lagarto said: Yes, odd. Do you mean that offset +1 is automatically added to glyph code when you change to All caps, or how is the "31 $" row produced? (I assume that you type "20 % off" but get this instead?) (Tried to post an .afpub file with text typed with the same font but for some reason attachments do not get through at the moment...) What happens if you open this one. oddrockfont.afpub Thanks - That is so weird, I downloaded your file and it doesn't look like that on my machine. How bizarre, what font management app are you using out of interest? Quote Link to comment Share on other sites More sharing options...
Barrowman Posted March 5, 2020 Author Share Posted March 5, 2020 Out of interest, as I'm new to Affinity, how did you do that black line block behind the text? Decorations? Quote Link to comment Share on other sites More sharing options...
lacerto Posted March 5, 2020 Share Posted March 5, 2020 (...) Quote Link to comment Share on other sites More sharing options...
Barrowman Posted March 6, 2020 Author Share Posted March 6, 2020 (edited) Yes, very odd, I'm glad in a way it's NOT Affinity at fault, however I can't see why Adobe manages to render correctly irrespectively. Thanks so much for that background colour tip, never knew about that! Edited March 6, 2020 by Barrowman Quote Link to comment Share on other sites More sharing options...
G13RL Posted March 6, 2020 Share Posted March 6, 2020 It's weird, if you go back in the text or if you delete it and type it again, it shows up as expected. I just downloaded the free version to try it, so I don't have the numbers. Quote Link to comment Share on other sites More sharing options...
lacerto Posted March 6, 2020 Share Posted March 6, 2020 (...) Quote Link to comment Share on other sites More sharing options...
MikeW Posted March 6, 2020 Share Posted March 6, 2020 3 hours ago, Lagarto said: ... But the erroneous behavior is definitely font-related and not caused by apps. Adobe just seems to have the necessary know-how to be able to use the font properly even if it has defects... Gotta remember that Adobe applications do not use the font sub-system in either OS. Bypassing the OS font sub-system is both a blessing and (can be a) curse in Adobe applications. If the font works in Windows and the exact same font doesn't work on the Mac no matter the application, that doesn't mean the font is in error (and it isn't gonna be related to the code pages in the font). More than likely the issue is related to the OS' handling of this very simple font. The creator string of the font was generated in FC 11.5, which as far as I know is a stable version of FC (I use it as well). There are a few double-mapped glyphs but do not believe these particular glyphs would cause the issue on the Mac (but I don't have one to try with). Quote Link to comment Share on other sites More sharing options...
lacerto Posted March 6, 2020 Share Posted March 6, 2020 (...) Quote Link to comment Share on other sites More sharing options...
Barrowman Posted March 8, 2020 Author Share Posted March 8, 2020 Thanks!! 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.