Preflight check for text frame overflow doesn't work?

[Blake_S]

After the data merge I have multiple text frames where text overflows past the frame, and even past the edge of the document.

However, preflight shows none of that as if everything is fine, why?

Example:

text overflows past the frame and past the edge of the document

[MikeTO]

I'm unable to duplicate this on macOS with v2.0.3. I can see you're on Windows but which version of Publisher are you using?

If you save, close, re-open the document, and then check pre-flight is there an error shown?

Cheers

[Old Bruce]

Try using a default instead of <Custom> Profile in the Preflight panel.

I misunderstood the problem.

The Text overflow is for text in a Frame Text Text Frame that is not all fitting in the Frame. It is hard to tell if the text in the Frame that is selected is actually overflowing.

There is no sign of the overflow indicator, it would be lower down.

[PixelEngineer]

In my merge tests preflight shows me text overflow warnings before and after completing the merge even when it falls past the edge of the document.

[Blake_S]

17 hours ago, MikeTO said:

I'm unable to duplicate this on macOS with v2.0.3. I can see you're on Windows but which version of Publisher are you using?

If you save, close, re-open the document, and then check pre-flight is there an error shown?

Cheers

v 2.0.3

This is consistent, doesn't matter if program is closed and re-opened, document re-saved, etc.

16 hours ago, Old Bruce said:

It is hard to tell if the text in the Frame that is selected is actually overflowing.

What does this even mean? You can extremely clearly see that the text is overflowing both past its frame and the edge o0f the document itself.
And yes, no overflow icon is shown, no preflight error, thus the existence of this thread

[Blake_S]

3 hours ago, PixelEngineer said:

In my merge tests preflight shows me text overflow warnings before and after completing the merge even when it falls past the edge of the document.

Check with "No break" selected in Character settings

[laurent32]

What is the typo used Blake ?

Can you use a well known typo like Arial or Helvetica to see if the problem is still there ?

Are you using special spaces between letters and/or words ?

Is the text justified or aligned to the left or right. ?

[Blake_S]

6 minutes ago, laurent32 said:

What is the typo used Blake ?

Can you use a well known typo like Arial or Helvetica to see if the problem is still there ?

Are you using special spaces between letters and/or words ?

Is the text justified or aligned to the left or right. ?

Gotham SSm

The bug happens with any font.

Types of spaces or characters don't matter.

Alignment doesn't matter.

What matters is having "No break" selected in Character settings.

[laurent32]

3 minutes ago, Blake_S said:

Gotham SSm

The bug happens with any font.

Types of spaces or characters don't matter.

Alignment doesn't matter.

What matters is having "No break" selected in Character settings.

OK, the answer is clear !

[Pšenda]

3 hours ago, Blake_S said:

What does this even mean?

[Pšenda]

On 1/18/2023 at 9:14 AM, Blake_S said:

and even past the edge of the document.

However, the specified check option only checks for overflow within the Text Frame, not within the document.

[Blake_S]

Well in that case there is no overflowing text indicator.

To me it seems like selecting "No break" disables overflow check.

[Pšenda]

1 hour ago, Blake_S said:

To me it seems like selecting "No break" disables overflow check.

Yes. With this option, you are telling the application that you are not interested in aligning this text to the Text Frame, and therefore its overflow is not monitored - which defacto did not happen (although the text is visually displayed outside the frame boundaries).
In my opinion, overflow monitoring is mainly intended so that the user does not miss cases when the text does not fit into the frame, and then it is not even displayed. In your case, the entire text is displayed - because you have actively turned off frame alignment.

Edited January 19, 2023 by Pšenda

[Blake_S]

26 minutes ago, Pšenda said:

Yes. With this option, you are telling the application that you are not interested in aligning this text to the Text Frame, and therefore its overflow is not monitored - which defacto did not happen (although the text is visually displayed outside the frame boundaries).
In my opinion, overflow monitoring is mainly intended so that the user does not miss cases when the text does not fit into the frame, and then it is not even displayed. In your case, the entire text is displayed - because you have actively turned off frame alignment.

Where did you get all of this? Its not in the documentation.
Like I want to use text frame to align multiple lines, and warn me when the line goes outside of the bounds of the frame, and this goes directly against your assumptions above.

Also, currently "No break" is the only way to maintain word integrity.

If I disable it, Text Frame will start breaking words into chunks and placing them on multiple lines even after disabled hyphenation - any way to prevent this besides "No break"?
 

[MikeTO]

If you have "no break" set you will not get an overset warning - it's always been this way in Affinity because this setting allows the text to extend past the right edge of the frame. Other programs may handle no break differently.

If you don't have "no break" set, you will get an overset icon. The overset text won't be displayed unless you have Text Frame > Hide Overflow deselected. Perhaps for your data merge use case you should consider turning off no break and hide overflow - this would give you the preflight warning you want plus a visual indication of the overset text.

[loukash]

1 hour ago, MikeTO said:

If you have "no break" set you will not get an overset warning - it's always been this way in Affinity because this setting allows the text to extend past the right edge of the frame.

Just for the record: I consider this a great feature.
For example, it allows to partially work around the missing span columns – as we have discussed two years ago in this thread ff.