Share
Report
2I’m encountering an issue in the Customer Insights Journeys email editor related to the display of compound terms with hyphens. Specifically, the editor does not treat the hyphenated compounds as a single unit, leading to instances where the hyphen appears at the end of one line and the next word is forced onto the following line. This breaks the intended flow of the text and looks visually inconsistent.
For example, this often occurs with Finnish phrases, as shown below:
Current (undesired) output:
- “Exploring options -” on one line, and “asiakkaat” on the next line.
- “Asiakkaiden etu -” on one line, with “ryhmässä” on the next.
Examples:
- Desired: “exploring options -” on one line, and “-asiakkaat” on the next.
- Current (undesired): “exploring options -” on one line, and “asiakkaat” on the next.
What I’ve Tried
To address this issue, I’ve experimented with the following CSS properties:
- white-space: nowrap; – This forces the text to stay on one line but is problematic as it doesn’t allow natural line breaks for longer sentences.
- word-break: keep-all; and white-space: pre-wrap; – These were added in an attempt to keep the hyphenated word together without forcing the entire sentence to one line, but it still breaks the compound term across lines.
- (non-breaking spaces) – I manually added between the hyphen and the compound term in HTML to prevent breaking. However, due to limitations with the editor, it’s not practical for longer texts or dynamic content.
Despite these attempts, the editor continues to break hyphenated compounds inconsistently.
The goal is to keep the hyphenated compound as a single visual unit to prevent the hyphen from being “orphaned” on one line. The ideal solution would be to incorporate an automation in the email editor that supports this functionality by automatically adding in the HTML code when entering hyphenated compounds in the visual editor. This would ensure that the compound term remains intact across lines, preserving readability and visual consistency without manual HTML edits.
Thanks in advance for any insights or solutions!
All responses (
Answers (
