Jump to content

Recommended Posts

Posted

I'm raising this as a new issue because I've now seen two separate instances of what initially appears to be the same problem...

There appears to be an issue where text flowing between text frames in certain (as yet unknown) circumstances has both it's font size and leading scaled to exactly 12% of it's original size.

The initial assumption in the first instance was that perhaps the text frame had been scaled but after a lot of testing this doesn't appear to be the case. The user simply copied and pasted text into the first text frame but as soon as it flows into the second linked text frame the 12% scaling issue occurs... The issue doesn't currently have a resolution...

 

The second instance involves opening an IDML file in Publisher, creating a new text frame and linking a text frame from the source document to the newly created Publisher text frame, again when the text flows between the two both the font size and leading are scaled by exactly 12% when the text flows into the second linked text frame.

As far as I'm aware, in the first instance, there was no association with an IDML file...

Opening the files in Publisher v1.X and v2.0.4 exhbit the same issue so it appears that there is something internal causing the scaling issue but it's not immediately obvious what that is...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Isn't this perhaps the dpi difference issue?
If document A is say 96 dpi and you copy/paste into document B  with 300 dpi it may alter the sizing.
 

I think Serif wants us to be only creative in finding workarounds to use their tools.

I have an affinity with Jumping through Hoops and over Humps.
Dealing with Speedbumps and finding Work-A-Roundabouts.
I'm getting dizzy from all that spinning and jumping.

Posted

Hi @Return,

I don't believe so... the issue is happening in the following circumstances in the second case...

  • Open an IDML file all looks as expected
  • Create a new text frame in Publisher
  • Link one of the text frames created in the IDML document to the newly created text frame in Publisher
  • Font and Leading are both scaled to 12% of their original size when flowed into the newly created Publisher text frame

So, in this particular instance there is no dpi difference.

In the first instance, as far as I know, there was no IDML element involved and the user tried pasting text to notepad and then copy pasting from there to remove any source formatting, so again no dpi conflicts...

Likewise, if you take two Publisher documents, one with 96 dpi, the second with 300 dpi, add 12 pt text with 14 pt leading to a text frame in the first document, copy and paste the text into a text frame in the second document and the text will remain 12 pt / 14pt so dpi isn't the issue as far as I can tell...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

I'm not using idml files so cannot tell if that's the culprit.
Perhaps it's an underlying issue that makes textframes behave badly.
IMO it has to do with the setup(code) for the textframes in relation to the extra handle which I believe is a redundant function and should be eliminated altogether.

I think Serif wants us to be only creative in finding workarounds to use their tools.

I have an affinity with Jumping through Hoops and over Humps.
Dealing with Speedbumps and finding Work-A-Roundabouts.
I'm getting dizzy from all that spinning and jumping.

Posted
14 minutes ago, Return said:

I'm not using idml files so cannot tell if that's the culprit.

I would be very suprised if IDML files are the culprit because I think we would have seen many reports of similar issues if it were...

15 minutes ago, Return said:

IMO it has to do with the setup(code) for the textframes in relation to the extra handle which I believe is a redundant function and should be eliminated altogether.

Why do you feel that, the two handles in the bottom right corner of a text frame serve different purposes... The inner resizes the text frame and subsequently reflows the text, the outer scales the text frame and the text within...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

I know what the second handle does but it gives more grievances and is very error prone.
If one needs to adjust the size, use the fontsize option.
If one needs to stretch text, use the options in the characterpanel.


 

I think Serif wants us to be only creative in finding workarounds to use their tools.

I have an affinity with Jumping through Hoops and over Humps.
Dealing with Speedbumps and finding Work-A-Roundabouts.
I'm getting dizzy from all that spinning and jumping.

Posted
41 minutes ago, Hangman said:

I would be very suprised if IDML files are the culprit because I think we would have seen many reports of similar issues if it were...

We have seen a significant number of reports, as I recall, that involved IDML files. And I think there is a bug logged for that, but they may not yet have figured out the underlying cause.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
12 minutes ago, walt.farrell said:

We have seen a significant number of reports, as I recall, that involved IDML files.

Hi Walt,

Do the reports relate to the same issue, do you happen to have links to any of the reports, it would perhaps be helpful to compare if they are related to this specific scaling issue...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted
26 minutes ago, Hangman said:

Do the reports relate to the same issue, do you happen to have links to any of the reports

Yes, they do. And no, I don't. I'm sure Serif is well aware of them, though.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
1 hour ago, walt.farrell said:

Yes, they do. And no, I don't. I'm sure Serif is well aware of them, though.

Thanks for the heads up... I've found a couple of reports dating back to late 2021 relating to v1.X, there appears to be no resolution and there's no bug reference attached to either so I'm unsure if it's logged or not...

and...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Reading through the other threads and looking at the sample files there is a common theme when the text scaling takes place which is certainly influenced by the dpi of the document though it seems unrelated to actually changing the document dpi, copying and pasting between documents with differing dpi's or the scaling of text frames...

On the Publisher documents I've looked at exhibiting this behaviour:

  • In every instance where the document is 600 dpi, the flowed text size and leading is scaled to exactly 12%
  • In every instance where the document is 300 dpi, the flowed text size and leading is scaled to exactly 24%

This sounds too conicidental to have anything to do with scaling text frames as the chances of everyone who's experienced the issue scaling the text frame by exactly the same amount is extremely low to nil.

This also seems to happen when only Publisher is involved which leads me to think IDML files may be a red herring and just coincidenctal...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

I've had the issue of the linked text frame always scaling up. However, I had been attributing it to somehow inadvertently having scaled the page 1 text frame at some previous unknown time, thus causing issues for the flowed page 2 text frame. My solution has been to move the original text frame off page 1, create a fresh, new text frame on page one, then copy/no-format-paste the original text back into the new page 1 frame. It then flows to subsequent pages fine.

I hadn't bothered to check the exact scale, so don't know if it's the 12% number or not. I had just assumed that perhaps at setup of the original what was a 1-page doc that at some point I must have resized that page 1 text frame, but don't recall that I ever did. Perhaps this is the same issue. None of this was using an IDML file that I can recall, But I do remember when it first happened. Took me forever to sort it out! I still come across it every so often, and never remember if this was a doc that I had already fixed or not. I'll have to see if I can find one that still does it. 

--------------------

New: 2023 Mac Studio M2 MAX 12-Core CPU/38-Core GPU 64GB Memory • 5k Studio Display • Sonoma
Prev: 2020 iMac 27 i7 (5k Rez), 72GB, AMD Radeon Pro 5700XT 16GB • Sonoma
MacBook Pro, 13", M1 2020 • 16 GB • macOS Sonoma
iPad Air 2022

Posted

Hi @Hangman,

Thanks for your report & my apologies for the delayed response here!

I've been able to replicate this issue with the imported IDML from this thread, which I'm getting logged for further investigation now as I don't understand the cause of this.
I'll be sure to check for similar IDML import reports as I've not personally seen this being reported previously, but it's certainly possible it's a known issue with some background 'scaling' being interpreted incorrectly when Publisher imports this IDML.

However, I'm unable to replicate this in a new document and all other reports linked above are with documents from 1.10.6 - as I understand it there have been many fixes to text and scaling issues between 1.10.6 and 2.0.4 and therefore it's possible that either:

a) This issue only occurs when importing certain IDML documents, as above

b) The issue was present in 1.10.6 and has since been resolved such that it can longer occur in 2.0.4 - though opening 1.10.6 documents in V2 would retain any incorrect scaling already present in the file.

If yourself, or any other users are able to replicate this issue within V2 without importing an IDML file, or opening a V1 file, then we'd certainly love to hear the steps to replicate this and we can log it with the devs as required.

I hope this helps :)

Posted

Hi @Dan C,

Many thanks for your reply...

I spent quite some time trying to figure out what on earth was going on with the IDML in this particular instance, even looking at the IDML's XML data didn't show anything untoward, in as much as it all looked as expected so I was starting to think the IDML element may be a red herring as mentioned above.

Helpful to know however, that this could be directly related to 1.10.6, I'll do some further testing and see if I can replicate this and if so I'll put together a step by step...

That most definitely helps, thank you... :)

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Hi @Dan C,

Okay, so it turns out to be unbelievably easy to reproduce the text scaling issue and it occurs directly in all versions of Publisher, on macOS i.e., 1.10.6, 2.0.4 and 2.1.0 (1806)... It would be interesting to know if the same happens on Windows...

Steps to Reproduce

  1. Create a new A4, 72 dpi Affinity Publisher Document (the document size and dpi don't matter but the dpi will determine the text percentage scaling)
  2. Add a text frame using the frame text tool with a height of around 50mm (the height isn't important)
  3. Paste some text into the text frame so there is overflow text available, e.g., 12 pt text (the size isn't important)
  4. Save the document
  5. Close the document
  6. Reopen the document
  7. In the Document Setup dialog window change the document dpi from 72 dpi to 300 dpi
  8. Add a second text frame using the frame text tool
  9. Link the first text frame with overflow text to the newly created text frame
  10. The text in the second text frame will now be scaled by the change document resolution factor, e.g., ((72 / 300) x 100) = 24% or ((2.88 pt / 12 pt) x 100) = 24%

If done in reverse, i.e., you start with a 300 dpi document and follow the steps above, changing the document dpi from 300 dpi to 72 dpi in step 7, then the flowed text in the second text frame appears proportionally larger, e.g.,

  • Increase in document dpi - 300 - 72 = 288
  • Percentage increase in text size - ((288 / 72) x 100 = 316.667% or 12 pt + 316.667% = 50 pt

Conclusion

  • The issue has nothing to do with IDML files, though opened IDML files will experience the same issue if the Publisher document dpi is changed.
  • The issue has nothing to do with scaling text frames in Publisher.
  • The issue is simply caused by a Publisher document resolution change when following the steps above.

 

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Hi @MickRose, many thanks for testing, it's interesting that this doesn't appear to affect the Windows versions as the assumption is that the code base is the same but I guess there's a subtle difference on Mac...

I'm now wondering whether or not it affects the iPad version, my assumption is unlikely but maybe someone can test there as well to confirm...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Many thanks for your further testing here @Hangman, it's certainly appreciated!

I can confirm that I've been able to replicate the above steps on Windows 2.1 - so I will be logging this with our developers now.
I'm not sure if this is related to the previous IDML report but I will be sure to 'link' these internally for our developers attention.

Hopefully this can be resolved ASAP :)

Posted
1 hour ago, Dan C said:

I can confirm that I've been able to replicate the above steps on Windows 2.1 - so I will be logging this with our developers now.
I'm not sure if this is related to the previous IDML report but I will be sure to 'link' these internally for our developers attention.

Hi @Dan C, following the same steps makes the previous IDML report reasonably easy to solve...

  1. Temporarily cut some text on page 2 to pull the chart back up to page 2 as well and for ease, temporarily unpin the chart and move to page 1
  2. Unlink the text frames on page three from those on page 2 and delete them
  3. As a result of the document scaling, the text below the chart heading text now has 100 pt leading, correct by either reapplying the appropriate text style or manually changing it back to 12 pt
  4. Save the document
  5. Close the document
  6. Reopen the document
  7. Change the Document dpi from 600 dpi to 72 dpi (since that is the factor the text is scaled by)
  8. Add a new two column text frame on page 3
  9. Relink the text frame on page 2 to the newly created one on page 3, paste back the text that was cut in Step 1 and the text now flows to page 3 at the correct size
  10. Reposition and repin the chart

 

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

  • 2 months later...
Posted

@Dan C: @Hangman has provided some additional diagnosis of the cause here, in case those details are not yet in the development report.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

  • 7 months later...
  • Staff
Posted

The issue "Flowing Story text is scaled unexpectedly after changing the documents DPI" (REF: AF-1288) has been fixed by the developers in internal build "2.5.0.2317".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

  • 6 months later...
Posted

@Affinity Info Bot

On 3/11/2024 at 10:04 AM, Affinity Info Bot said:

The issue "Flowing Story text is scaled unexpectedly after changing the documents DPI" (REF: AF-1288) has been fixed by the developers in internal build "2.5.0.2317".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

I'm still experiencing this issue in 2.5.5. It's happening when I'm extending a Notes (endnotes) frame onto the next page. I haven't been able to definitively say it's related to the DPI because I've potentially seen some progress when I play with that (i.e., changing document DPI), but I'm in the middle of a crunch, so I'm not able to drill down to say definitively that is the cause. But the issue is alive and well.

Posted

Hi @JuBe,

Are you able to share the document in question or if not a screen recording that shows the issue with your complete UI and the layers panel visible...

The bug has been fixed in 2.5.5 so there may be something else going on which we will likely be able to pick up quickly by taking a look at the document or a screen recording demonstrating extending the endnotes...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3106 | Affinity Photo Beta 2.6.0.3106 | Affinity Publisher Beta 2.6.0.3106

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.