Jump to content
You must now use your email address to sign in [click for more info] ×

pfbt

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by pfbt

  1. On 1/31/2024 at 9:01 PM, Hangman said:

    Hi @pfbt,

    The issue you're seeing is likely a known bug in Affinity Publisher, logged under AF-1288 and AF-1342 and can happen if the document dpi has been changed at some point in its history in between new text frames being added to the document or if a page or pages are added to the document using Add Pages from File when the two Publisher documents have different dpi settings or you're adding pages directly from an IDML file to your Publisher document assuming your Publisher document has a dpi greater than 72 dpi...

    This happens when opening IDML documents which are interpreted by Publisher at 72 dpi but can also happen, as is the case here, with documents created directly in Publisher...

    Your document is 192 dpi and if you look at the change in font size for the heading and body text when it is brought over from Page 5 to Page 4 you'll see that it is being scaled by 37.50%, so you effectively have two text frames using different resolutions, 192 dpi and 72 dpi.

    Text Style Heading 2 - Changes from 14 pt to 37.33 pt

    (14 / 37.33) x 100 = 37.50%

    Text Style Normal - Changes from 11 pt to 29.33 pt

    (11 / 29.33) x 100 = 37.50%

    When you insert the page break the font is scaled in the opposite direction because it's going from Page 4 to Page 5 but it's still being scaled by 37.50%

    Text Style Normal - Changes from 11 pt to 4.13 pt when the Page Break is inserted

    11 x 37.50% = 4.13 pt

     

    Steps to Rectify the Issue

    1. Change the Document dpi from 192 dpi to 72 dpi
    2. Unlink the Text Frames linking Page 4 to Page 5
    3. Delete Page 5
    4. Insert a new page after Page 4 using the 'Follow on' Master
    5. Add a text frame to the newly added page
    6. Link the text frame on Page 4 to the text frame on Page 5
    7. Re-apply the respective text styles to the oversized text
    8. Change the document back to 192 dpi
    9. Save the document and all should be back to normal

    Note: You may need to repeat this exercise for Pages 10 and 11 where you see the same issue when text is deleted from Page 10...

     

    Screen Recording

     

    Worked a treat.  Thank you.

  2. 1 hour ago, MikeTO said:

    Hi, what's happened is you accidentally dragged the content scaling handle (the outer bottom right handle) on the text frame. This is a very common problem because it's not obvious that you've done it.

    Try this with a blank document. Draw two small text frames on a page and link them together. Type some text, enough to fill both frames. Scale the first frame using the bottom right size handle (the inner one). That scales the frame without scaling the contents. Scale it small. Now drag the content scaling handle (the other one). That scales the frame and the text inside it. Scale it about twice as large, doubling the text size. Now if you edit text in the first frame, either pushing text to frame 2 or pulling text forward to frame 1, you'll see that the text size changes depending on which frame it is in.

    Unfortunately, Publisher doesn't show the content scaling factor for a text frame like it does for a picture frame so there's no way to see this or reset it to 100% except by reverting the frame to defaults. Select the frame with the Move tool and choose Edit > Defaults > Revert. You might have to do this for both frames depending on which one is messed up. Or just delete the frames and draw new ones.

    Good luck!

    Just tried it, and your exercise works as suggested.

    However, I think what I'm getting is different. The frames on the pages in question haven't been changed. Simply deleting text on page 1, say, so that text moves from page 2 back to page 1 causes the text to change size to something MUCH bigger than the text in page 1. Conversely, adding a page break on page 1 causes text to move to page 2 and the moved text is then much SMALLER than the other text on page 2.  

    Seems to me it's a different issue as the text frames, as far as I can tell, have not been scaled.

  3. 1 hour ago, MikeTO said:

    Hi, what's happened is you accidentally dragged the content scaling handle (the outer bottom right handle) on the text frame. This is a very common problem because it's not obvious that you've done it.

    Try this with a blank document. Draw two small text frames on a page and link them together. Type some text, enough to fill both frames. Scale the first frame using the bottom right size handle (the inner one). That scales the frame without scaling the contents. Scale it small. Now drag the content scaling handle (the other one). That scales the frame and the text inside it. Scale it about twice as large, doubling the text size. Now if you edit text in the first frame, either pushing text to frame 2 or pulling text forward to frame 1, you'll see that the text size changes depending on which frame it is in.

    Unfortunately, Publisher doesn't show the content scaling factor for a text frame like it does for a picture frame so there's no way to see this or reset it to 100% except by reverting the frame to defaults. Select the frame with the Move tool and choose Edit > Defaults > Revert. You might have to do this for both frames depending on which one is messed up. Or just delete the frames and draw new ones.

    Good luck!

    Thanks MikeTO, I'll play with that later today. 
    You're right that it's not obvious that I've dragged the scaling handle as to my knowledge I went nowhere near it. However, I'll try your suggestion.

  4. 1 minute ago, pfbt said:

    Hi Dan, I finally got the video (attached) done for you. 

    I've attached two afpub files. The one labelled v1-01 was the one I started with: the video shows me working on that to create a shorter version (the 2nd document labelled "Short Version DRAFT 1").  (I'd be grateful if you only keep these documents while they're needed as they're part of a product a colleague and I are launching at the end of the month.)

    As mentioned in the video, these documents were originally created in AP version 1, but now in AP version 2.

    I've had documents where this happens a lot; and documents where it doesn't happen at all; so it's hard to track down a reason. Could it be a screen redraw issue? A caching issue? or corruption in the file? Or something else?

    I've seen forum comments when people have been changing the frame size and that's changed font size, but as you can see that's not the case here; it's simply text being moved from one page to another.

     

    GCT Foundations Participant Guide Part 3 v1-01.afpub 2.27 MB · 0 downloads GCT Foundations Guide Part 3 v1 Short version DRAFT 1.afpub 3.2 MB · 0 downloads

    Forgot to mention:

    Hardware Mac Mini M1 running Sonoma 14.2.1

    I can check (given time) if the same happens on my Mac Studio and my MacBook Pro (intel chip).

  5. Hi Dan, I finally got the video (attached) done for you. 

    I've attached two afpub files. The one labelled v1-01 was the one I started with: the video shows me working on that to create a shorter version (the 2nd document labelled "Short Version DRAFT 1").  (I'd be grateful if you only keep these documents while they're needed as they're part of a product a colleague and I are launching at the end of the month.)

    As mentioned in the video, these documents were originally created in AP version 1, but now in AP version 2.

    I've had documents where this happens a lot; and documents where it doesn't happen at all; so it's hard to track down a reason. Could it be a screen redraw issue? A caching issue? or corruption in the file? Or something else?

    I've seen forum comments when people have been changing the frame size and that's changed font size, but as you can see that's not the case here; it's simply text being moved from one page to another.

     

    GCT Foundations Participant Guide Part 3 v1-01.afpub GCT Foundations Guide Part 3 v1 Short version DRAFT 1.afpub

  6. Version 2 installed an up and running. FINALLY ... delighted that footnotes and endnotes are in. I would love to have known that they were in development, but given the extraordinary offerings in the announcement, I can see why they were keeping quiet about what they were up to. It's been a long wait ... Haven't played with v2 much yet, but it looks like the wait was worth it for my purposes, at least.

    Thank you Serif.

  7. I love Publisher for what it does do, but it's been a major disappointment that, to date, it's not lived up to the promise of being a replacement for InDesign. I think we can truthfully say it was a reasonable expectation.

    Via Twitter, I reminded Serif that communication is everything. Companies like Apple might be able to get away with saying nothing about what they're developing because we know that at least twice a year they deliver something.

    Right now, there seems to be no hint of whether Serif is even working on Publisher. Their lack of communication on topics like footnotes might have been excusable for, say, a year. But more than 4 years down the track, they're saying nothing. Very poor form and does nothing to engender ongoing trust in the company.

    I'd  like to see them concentrate less on all the fancy integration between Designer, Photo, & Publisher for a time while they simply get in the functionality that we've been pleading for.

    Meanwhile, I will keep using Publisher for documents that don't require footnotes, etc. However, for documents/books requiring footnotes, endnotes, cross-referencing it's Mellel (which is truly fantastic with those features).

  8. 1 hour ago, fde101 said:

    Mellel is a great word processor for this type of thing, but is not a page layout app.  Right now to avoid the subscription model and get footnote/endnote support in a layout app you are basically looking at QuarkXPress or possibly one of a few lesser-known or overall less capable products.  Most of the less expensive products I have looked at do not support them.

    Scribus is apparently adding them but they are not in a stable release yet.

    There is also LaTeX, of course - a bit different to work with but it can produce excellent results once you wrap your head around it.

    That's true in principle. However, I had a number of diagrams in my thesis and was happy that I could place them where I wanted. Can also do text wrap around, etc. Yes, it's not as flexible as Aff. Pub. where I can put the diagram virtually anywhere and pin it (or put it inline), but I was more than happy with the layout and placing of text. It's brilliant with headings and table of content (although there is one quirky bit with that). If I had to do another thesis, Mellel would be my first choice ... until Aff. Pub. gets footnotes, endnotes and proper cross-referencing (which Mellel is stunning at).  The integration with Bookends is marvellous.

  9. There must be some instructions somewhere that explain how the paragraph spacing options in Tables of Content work that would help with the issue I'm having.

    I'm trying to create a TOC from Headings 1, 2 and 3 and to get a simple 6pt space before each TOC entry. No matter what I try, Publisher keeps putting spaces that I haven't asked. And, on one occasion it even changed the font to italic when I tried changing the spacing.

    The instructions are sparse and there seems to be no way to work out what the interactions between the spacing settings really do.

    Publisher is great, but in some parts the instructions are so superficial that they're next to useless.

    Can someone please advise.  I've wasted hours trying to work out what Serif has done with TOC paragraph spacing.

     

  10. 10 hours ago, LibreTraining said:

    First, a direct link to the actual article: https://affinityspotlight.com/article/interview-with-emily-goater-affinity-publisher-product-expert/

    There is no mention of footnotes at all.

    How is this relevant to this discussion?

    Agreed. How is it relevant?  I suppose we can give it some in this sense: it highlights what we already know – that what Publisher does well it does spectacularly well. And, it highlights the point I made earlier about the concentration on magazine-type production.

    However, the number of people calling for footnotes/endnotes (and better cross referencing, in my case) ... and the number of years they've been doing so ... should be sending a clear message to Affinity. People are desperate to dump InDesign and QuarkXpress, but the lag with introducing basic, essential DTP features is a major issue.

    Further down this topic's timeline there is mention that Publisher is maybe not the best for academic publishing. Agreed. If I were to do an academic article/book, I would use Mellel as it's ideally suited to that purpose and integrates wonderfully with Bookends for reference management. However, one could do academic publishing in InDesign or QuarkXpress. Now, Affinity came on the scene with a clear indication – albeit implicitly to a large extent – of taking on Adobe. So many of us are sick of Adobe's price gouging and ridiculous subscription system that gives you "value" by forcing you to pay for a pile of stuff you don't need (in many cases).  I only use Illustrator (and will dump that when Affinity provides calligraphic pens) and InDesign; but to subscribe to both those would be as expensive (nearly) as getting the whole thing. Given the gauntlet that Affinity has thrown down, you might expect that Publisher would provide the essential, basic tools that InDesign has, for example.

    Moreover, if people were able to effectively use Publisher for academic writing, there is a HUGE market out there, especially given the very sensible pricing.

    There is also the potential for disaffection of existing customers having to wait too long for what, in my opinion, they consider to be fundamental tools in the app. Recently, I found myself doing training documents in Publisher because it's so much nicer to use, generally, than Quark or InDesign. BUT, I need footnotes, so I've been wondering whether to just give up on Publisher and use Mellel (more laborious and much fiddlier with placing images, but it has all the essential tools).

    Affinity, take note: I'd quite happily pay twice the price to have footnotes/endnotes, and fully-functional cross referencing. (And calligraphic pens in Designer.). 

    Just don't EVER go to subscription model though.

  11. Looking through this topic, we can see that people have been begging for footnotes and endnotes for 3 years now. I absolutely love Publisher, but like many people cannot abandon InDesign or QuarkXpress until Serif provides really basic, essential features for desktop publishing. It seems there is a lot of concentration on magazine-y stuff with lots of clever Designer & Photo integration, BUT that's not nearly as important to many of us as essential DTP features like footnotes. 

    Cross-referencing could use a serious boost too. I often want to refer to an example by number. Sometimes that number will change if I add in a new, preceding example. In Quark, I can update the cross-reference to that example. In Publisher I can't even (as far as I can see) cross-reference specific text – though I can link to an anchor, but that's not the same nor as useful for my purposes.

    It's been a long, long, long time Serif. We love the program but you're making it too hard to complete the transition from InDesign/QuarkXpress.  You're at risk of losing your market edge with this really slow response to basic, essential DTP features. Even the $80 Mellel app that I wrote my PhD in has had such features as long as I've known it (going back to 2005). 

    Drop the glitzy graphics stuff (which I bet of lot of us might not be using) for a while, and quickly catch up with the features your dedicated, but exasperated, customers are asking for.

  12. 23 hours ago, Lee D said:

    @pfbt Is this occurring with an existing document, a new one or both? Are you editing one of the preset paragraph styles or a custom one?.

    New document.  Used a Footer style, but also tried with a plain Body style. When editing the style, could make the selection for Towards spine or Away from spine, but as soon as I click on OK Publisher instantly closes.

  13. Undoubtedly this request is already somewhere in the many; and a google search shows lots of energetic pleas for it:

    The ability to move the ruler origin is essential for my work. 

    I can't dump Illustrator until I get this feature as well as arrowheads and calligraphic brushes.

    Designer has some amazing features, but if we're to have a satisfactory replacement for Illustrator, wouldn't it be better to provide the absolutely basic and essential features first and then add the arcane stuff later?  (Same problem in Publisher – can't anchor images and that's absolutely basic and essential for dumping InDesign.)

    Affinity team, please focus on the can't-live-without features of Illustrator and put them in Designer ... until you do, we're still being price gouged by Adobe.  Meanwhile, I find I'm using Graphic far more than Designer because at least it has arrowheads (not as good as Illustrator, but acceptable) and calligraphic brushes.

    There's so much to love about Designer but the missing essential features become a source of resentment the longer they're missing. 

    I guess Affinity is still deciding whether they want us to leave Adobe or just use Designer as well ...??

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.