Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Text Wraps Unexpectedly

Featured Replies

I have a form document using merge fields that includes the language "SCPA 1708.2(a)" as part of the boilerplate  There is no space between the 2 and the (a), yet sometimes the merge fields cause SCPA 1708.2(a) to go all the way to the right margin.  When that happens, I get SCPA 1708.2 at the end of the line, and the (a) at the beginning of the next line.  They really need to be together since it is a section of law from the Surrogate's Court Procedure Act.

 

Is there a way to force text to be kept together, no matter what?

 

Thanks,

Kevin

For those who might not understand the specific issue, here is an example of the break and a possible fix:

 

snapshot.png

 

Hi Kevin,

 

The issue is that, to FM, parentheses are word break between a number and an alpha (one of three special sets of word delimiter rules).  It can be resolved by taking advantage of non-breaking space if  you could accept the string being changed to  SPCA 1708.2 (a) ...  notice a space between 2 and (

 

This calc can be placed on the layout,  used as merge field or used in conditional format object with merge variable).  You could also script data change itself but if more text came in then you would have some with and some without and that could be a mess. Addressing this at the display level and not the data level would most likely be best.

 

Also the ~ is to protect from regular open parenthesis being changed by changing them to ~ then back when done.

Let ( [
parenth = Char ( 40 ) ;
nonbreak = Char ( 160 ) 
] ;
Substitute ( origtext ; [ " (" ; "~" ] ; [ parenth ; nonbreak & parenth ] ; [ "~" ; " (" ] )
)

nonBreak.zip

  • Author

Hi, LaRetta.  Thanks so much for your help.  Your example of the problem is right on the money.  That's exactly what's happening.  I thought the ( was the problem, but I had no idea how to get around it.

 

I'm going to use your calc.  The added space is of no consequence -- it's most important that the reader of the document does not overlook paragraph (a) of the subsection, otherwise, the intent of the document could be misconstrued.

 

Thanks again, and have a great weekend.

 

Kevin

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.