My wild guess is that you would rather want to REMOVE the Colon rule completely...

It's my understanding is that you actually want the "-Eingangsspannung: 100-240V 50/60 Hz" and "-Konstanter Strom: 700mA DC" strings to NOT be splitted at the colon to two segments... right? If yes, then removing the Colon segmentation rule is what you want to do.

IMO the Colon rule should have been removed long time ago from the defaults as it does more harm than good in most cases. It could be worth for translating books, where the story characters say something... but CAT tools are normally not used for such translations... and in materials translated using CAT tools it's usually UNWANTED to break segments at colon (like in this example).

Sorry, I had written another post about modifying the colon segmentation rule but in fact, removing the default colon segmentation rule is all that's needed in this case.

The key to understanding why is that two different segmentation rules come into play when you have text like this.

Technische Daten: (1)

-Eingangsspannung:(2) 100-240V 50/60 Hz

-Konstanter Strom:(2) 700mA DC

Text is being segmented at (1) not because of the colon, but because of the new line (likely a hard return).

By removing the colon segmentation rule, text won't be segmented at (2) anymore.

IMO the "colon followed by hyphen" is actually what creates the confusion here... and what's in fact incorrect.

IMO, what Rachel was originally after was "colon followed by linebreak and hyphen at the start of the next line".
But the point is that - if I was right in what she actually needs(!) - what she is after is incorrect and looking in wrong direction.

If the original text really looks as weird as this:
Technische Daten: -Eingangsspannung: 100-240V 50/60 Hz -Konstanter Strom: 700mA DC
(i.e. WITHOUT LINEBREAK after "Technische Daten:"), then I would question the correctness of the source in the first place!
Simply because it looks like a buletted list incorrectly converted to plain text! I've seen this many times... as a result of lame HTML-to-text conversion... in particular an export from CMS database where someone had a bright idea to "help" us by blindly removing all HTML tags (re4sulting in such total mess).