Discretionary Hyphen (00AD) not respected

[LinqLover]

Describe the Bug

When rendering a BPMN element, such as an activity, discretionary hyphens (code point 00AD; on Windows, they can be typed using ALT + 0173) are not respected. As a result, long words cannot be wrapped correctly.

Steps to Reproduce

1. Create an activity
2. Name it:

   Fight Hippopoto­monstro­sesquippe­daliophobia
   

   (Note that most web browsers will not even show the discretionary hyphens in the code box, but still you can copy them into another application.)
3. During editing, the hyphens are used for word-wrapping correctly:
   
4. But after accepting the label, the word-wrapping disappears and the hyphens are no longer respected:
   

Expected Behavior

Discretionary hyphens should be respected correctly for word-wrapping.

Environment

• Browser: Chrome 86
• OS: Windows 2004
• Library version: https://demo.bpmn.io at 2020-12-02

[azeghers]

Hey Linq,

First of all, thank you for this issue, I've learned about a character I didn't know before 😄
I'm posting a screenshot of a tool that shows special/invisible characters because it isn't clear in your step 2 that you're adding those hyphens to the word.

I have a couple of questions for you regarding this topic :

• Have you considered using regular hyphens and line-breaks for those cases?
• How often are you confronted to the usage of words too long to visually fit in bpmn task elements? Would you consider this problem a blocker for your purposes?

[LinqLover]

Thanks for the reply! :D

Have you considered using regular hyphens and line-breaks for those cases?

Yes, I could do that, but I think this is a suboptimal solution in terms of maintenance. :-)

Would you consider this problem a blocker for your purposes?

No, it's just about convenience.

How often are you confronted to the usage of words too long to visually fit in bpmn task elements?

I'm using German terms for my models, and in German, compound words are not separated by a space, e.g. "Modellierungsrichtlinie" rather than "modeling guideline". So yes, actually, I miss a proper word-wrapping quite frequently. Automatic word-wrapping would be best, of course, but I see this would be a major effort ...

[azeghers]

I will look into how labels are formatted and get back to you. 🙂

[LinqLover]

Great, thanks for implementing! Looking forward to the next release :-)

[fml2]

Will these chars be supported and interpreted correctly both in the camunda modeler and in the cockpit when displaying process models and process instances?

[nikku]

Will these chars be supported and interpreted correctly both in the camunda modeler and in the cockpit when displaying process models and process instances?

Nope.

[fml2]

Where will they be supported then? Isn't the bpmn.js library used in both products? Thank you.

[nikku]

The feature will first land in the Camunda Modeler, likely with the next modeler release. The feature may end up in the next version of Cockpit, once the Camunda Platform team decides to update the dependency.

I am afraid there does not exist an automatic update step here.