pet_griffin Posted August 16 Share Posted August 16 Hi I have just started using Affinity Publisher as an alternative to InDesign and am very impressed so far, especially after faffing around with Scribus and MS Publisher! I am working on a simple document where I modified the "Heading 1" style as follows: I set the font weight to "Bold" but this is not reflected in my document: The "active" text is still showing as "regular" (LHS) when it should be bold according to the style above. I notice the the style in the ribbon is "Heading 1+" - in ID that would mean that I have tweaked the current style but I don't think I have done that here. Is this something to do with me modifying an existing style? BTW the font in question (Mulish) is a Google Open font Best regards Alun G Quote Link to comment Share on other sites More sharing options...
Old Bruce Posted August 16 Share Posted August 16 10 minutes ago, pet_griffin said: I notice the the style in the ribbon is "Heading 1+" - in ID that would mean that I have tweaked the current style but I don't think I have done that here. The "+" means you have in fact modified the text. To find out what has been changed look at the Text Styles studio and ht the little triangle next to the name (once you have the text caret in the heading as in your screen shot). There is a "T" with a bizarre looking arrow around it on that panel, hit it and you'll go back to the original format with no overrides. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
pet_griffin Posted August 16 Author Share Posted August 16 Hi @Old Bruce thanks for your comment. I highlighted the text, found the Text Style window and clicked the "T + arrow" but still have the override and the wrong font weight so am a bit confused ... Quote Link to comment Share on other sites More sharing options...
thomaso Posted August 16 Share Posted August 16 1 hour ago, pet_griffin said: clicked the "T + arrow" but still have the override and the wrong font weight Try this way to reset the assigned style: With the text selected right-click its style name and choose the option to assign + clear Character Style. Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
pet_griffin Posted August 17 Author Share Posted August 17 Hi @thomaso sorry, that didn't work either - still have "Heading 1+" in the style dropdown. I tried creating a new text frame but the text style showed up as "Heading 1+" before I had even typed anything in the text box. I quit and reloaded Affinity but that didn't solve the problem. I suspect I am doing something dumb but just don't know what ... Quote Link to comment Share on other sites More sharing options...
thomaso Posted August 17 Share Posted August 17 Can you show the selected text frame and the Text Frame Panel with its top text field unfolded to see details about the deviating attributes? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
pet_griffin Posted August 17 Author Share Posted August 17 Do you mean like this: Quote Link to comment Share on other sites More sharing options...
thomaso Posted August 17 Share Posted August 17 13 minutes ago, pet_griffin said: Do you mean like this: Sorry, I meant to say Text Style Panel (not Frame). Glad you show both. At its top, above the style names, it says "Heading 1" without the '+' character, while the '+' still appears in the Context Toolbar. Do you get this conflict with every use of this style, even with new text objects? If yes, this style definition might be broken, perhaps confused by its Base Style "Base sans serif"? – What if you delete "Headline 1" from the Panel + create a new one from scratch? If you have it assigned already to multiple paragraphs it is easier to test in a separate, new document + a copied sample text frame that has "Headline 1" assigned. (Then, if deleting + recreating the style does fix the issue you may need a workaround in the larger document: Create the new style with a different name -> assign this new style via Find & Replace to the text that has "Headline 1" currently assigned -> delete "Headline 1" and rename the new style to the wanted "Headline 1". Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
Old Bruce Posted August 17 Share Posted August 17 2 hours ago, pet_griffin said: Do you mean like this: That is weird, what @thomaso pointed out rebuilding may be the quickest way to fix this. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
pet_griffin Posted August 17 Author Share Posted August 17 I did some experimenting and the issue only seems to occur when I change the font weight to eg Semi-bold in the style definition. The "+" symbol appears next to the style name but the font weight change does not get applied. The typeface in question (Mulish) is a variable Google font so maybe Affinity is getting confused with these? Old Bruce 1 Quote Link to comment Share on other sites More sharing options...
Old Bruce Posted August 17 Share Posted August 17 1 minute ago, pet_griffin said: I did some experimenting and the issue only seems to occur when I change the font weight to eg Semi-bold in the style definition. The "+" symbol appears next to the style name but the font weight change does not get applied. The typeface in question (Mulish) is a variable Google font so maybe Affinity is getting confused with these? Variable fonts create all sorts of gotchas. I should point out that I am not a fan of them so I have a bias against them and their use. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
thomaso Posted August 17 Share Posted August 17 5 minutes ago, pet_griffin said: The typeface in question (Mulish) is a variable Google font so maybe Affinity is getting confused with these? Good hint. Sorry, I can't test it with variable fonts in V1, so just a guess: Does the "Based on" style influence the issue? What if 'Headline 1' does not base on 'Base sans serif' – or, vice versa, is it possible to select the (semi-)bold weight for 'Base sans serif'? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
pet_griffin Posted August 17 Author Share Posted August 17 If I create a new style called "Heading 1" that is not based on another style then it seems to work. I guess this is a workaround but it is a bit of a PITA as I want to try different sans serif fonts in the document and hoped I could just get away with changing the "base sans serif" font and have the changes flow through to its descendants. But it's only a minor inconvenience ... Quote Link to comment Share on other sites More sharing options...
thomaso Posted August 17 Share Posted August 17 28 minutes ago, pet_griffin said: If I create a new style called "Heading 1" that is not based on another style then it seems to work. (…) hoped I could just get away with changing the "base sans serif" font May be it works if the "Based on" font avoids just variable fonts in particular, or just this "Mulish"? In case the order of the style setup triggers the issue, you could try other ways to setup the desired styles, for instance a different font for the "Based on" style during setup, then switching to the problematic "Mulish" after both styles were created. – Or first setup both styles separately and then activate "Based on" for "Headline 1" and reset its required [No change] options. – Or first setup the "base sans serif" style as (semi-)bold, then create the style "Headline 1" and then set "base sans serif" as desired (e.g. normal/regular). – While experimenting keep an eye on the Context Toolbar and an occurring '+' symbol after a certain change. Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
pet_griffin Posted August 19 Author Share Posted August 19 I did a bit more experimenting and created a document with three styles: Heading 1, Heading 2, Heading 3. All are based on the "Base" style which is set to Arial. The differences are Heading 1: Bold/ 36 pt Heading 2: Semi-bold/24 pt Heading 3 Medium/18 pt In the style dropdown, Heading 1 has no "+" after it but Heading 2 and Heading 3 do. It seems that the issue is with "non-standard" weights like semi-bold and medium rather than with the typeface itself. Is this the sort of thing I ought to report to Serif as a bug? Quote Link to comment Share on other sites More sharing options...
thomaso Posted August 19 Share Posted August 19 14 minutes ago, pet_griffin said: Is this the sort of thing I ought to report to Serif as a bug? Yes, you could, but also you can wait a few days before creating a bug report in an according Bugs Forum, often a Serif moderator confirms a bug in this Questions forum and logs it as bug without an explicit bug report. If you create a bug report: A link to this thread may help, and possibly also a screencast, demonstrating the issue from style creation to the appearing '+' symbol. Below a sample in V1 without the '+' issue: next style V1.m4v Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
R C-R Posted August 19 Share Posted August 19 7 hours ago, pet_griffin said: I did a bit more experimenting and created a document with three styles: Heading 1, Heading 2, Heading 3. All are based on the "Base" style which is set to Arial. Before reporting this as a bug, it might help if you could upload this file you created (or a similar one with minimal content) to this topic so we can see if there is anything obvious about it that suggests why this issue is occurring. Quote All 3 1.10.8, & all 3 V2.5.5 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
thomaso Posted August 19 Share Posted August 19 21 minutes ago, R C-R said: so we can see if there is anything obvious about it that suggests why this issue is occurring. Does this mean you can't reproduce the issue with two simple self-made based-on + next-styles in V2? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
R C-R Posted August 19 Share Posted August 19 (edited) 51 minutes ago, thomaso said: Does this mean you can't reproduce the issue with two simple self-made based-on + next-styles in V2? It just means I don't know how the OP made those styles & applied them to text so I don't want to guess about it. Edited August 19 by R C-R Old Bruce 1 Quote All 3 1.10.8, & all 3 V2.5.5 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
thomaso Posted August 19 Share Posted August 19 23 minutes ago, R C-R said: I don't know how the OP made those styles & applied them to text so I don't want to guess about it. If it is a bug, it will happen in other files too, not just the OP's document and styles, right? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
R C-R Posted August 19 Share Posted August 19 3 minutes ago, thomaso said: If it is a bug, it will happen in other files too, not just the OP's document and styles, right? But what if it not a bug but something about how the OP's document is constructed or the stye is applied that makes it appear so? How would we know if that is a possibility without a sample from the OP? Quote All 3 1.10.8, & all 3 V2.5.5 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
Old Bruce Posted August 19 Share Posted August 19 5 minutes ago, thomaso said: If it is a bug, it will happen in other files too, not just the OP's document and styles, right? And if it is not a bug we will spend hours trying to unsuccessfully reproduce it. If it is something that the document has in one or more of its Paragraph styles we would waste a lot of time. R C-R 1 Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
thomaso Posted August 19 Share Posted August 19 10 hours ago, pet_griffin said: "Base" style which is set to Arial. The differences are Heading 1: Bold/ 36 pt Heading 2: Semi-bold/24 pt Heading 3 Medium/18 pt Can you confirm that your used Arial has the weights "Semi-bold" and "Medium"? And if not, what weights get used instead in your setup if you applied with "Then Next Styles"? 50 minutes ago, R C-R said: How would we know if that is a possibility without a sample from the OP? 49 minutes ago, Old Bruce said: And if it is not a bug we will spend hours trying to unsuccessfully reproduce it. If it is something that the document has in one or more of its Paragraph styles we would waste a lot of time. "How would we know…": Just by trying with two self-made styles. If the issue does not occur we would know the OP's description of switching the font's weight does not lead to a bug and the OP's issue would have another reason. "we will spend hours…": Creating and applying two Based-on + Next styles takes a few minutes, right? While examining the setup of another document may take longer, and it may take even more time if doubts occur about specific font files. However, I am aware that the OP should possibly prove the problem himself, e.g. with a delivered document or screencast. Just in this case I assume setting up two based-on + next styles is not a big thing. So, I don't request or demand you both to test yourself, I just see this as an easy option (which will be done anyway if the OP's document indeed leads to a bug on your computers). R C-R 1 Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
pet_griffin Posted August 20 Author Share Posted August 20 Sorry to cause so much trouble with this one. To clear up some confusion, if I set Arial as the base font, then Affinity honours the font weight (see attached file test_file_arial.afpub) but still adds a "+" to the style. With eg Mulish (or another Google variable font - haven't tried other eg WIndows variable fonts 'cos I'm not sure if I have any installed) then Affinity does not honour the font weight set in the style (see attached file test_file_mulish.afpub). However, if I go into the text box and apply eg a semi-bold variation directly then it does honour the font weight. test_file_arial.afpub test_file_mulish.afpub 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.