Start a new topic

Please! Help the German Com-Munity! Crazy Binde-Striche

Would it be able to introduce a way that deals with the 'crazy Bindestriche' (superfluous hard hyphens), in words like:

Folgende Export-Möglichkeiten stehen zur Verfügung:

When your glossary contains Exportmöglichkeiten?

I'm not asking for any fuzziness here, I'd just appreciate an exact solution very much. This is really slowing me down.

I also see this a lot:

Folgende Export- Möglichkeiten stehen zur Verfügung:

1 person likes this idea

the placing of dashes is totally arbitrary

I disagree. it is not arbitrary, but sometimes right and sometimes wrong. "Arbitrary" choices are where the chooser is always right, no matter what. "Curing" a source document to make it find what your repositories contain will always be an uphill struggle. The best we can hope for is that "rubbish in" equals "refuse out".

Case closed. Problem solved. Moving on to a new challenge.

Dear Mr. Woorden Sir, you all-knowing genius!

Can Termbases be the solution for Crazy Bindastricha?

Tropföl-Sammelraum in Text

Tropfölsammelraum in Termbase

Can you please check and report.

Thanks in advance!

over and out

radio silence

I said silence!

Must I come over with a wooden hammer?

It's quite easy: put them where they are needed.

Although the problem is probably worse in Dutch and German, no one knows where to put them or whether to use them in English either.

How about this one:



Next Segment:


That would have required either a dash or a better construction (Mindestdurchmesser der Folienrolle, minimale F. etc.)

This proves that the placing of dashes is totally arbitrary and, er, crazy.

Hi Hans,

Do you mean you didn't know that the "Do not match" list applies to TXT glossaries? I always assumed it applies to TMs (used for segments and/or terms), and TXT glossaries.

I am puzzled though hos this might affect the ability of making a TXT glossary case sensitive? How are the two related?


I didn't know that! I thought that this category of characters was meant for the TM only.

Anyway, I guess that this means that I cannot have the glossary set to Match case?

Actually, if you add - character to the "Do not match" list both BindeStriche and Binde-Striche will produce a match from your glossary. As for the careless "Binde - Striche" (with spaces around -), you might do Find and Replace in the Project Source segments scope.


What would be a good name for this glossary context menu? Resolve hyphens Ignore internal dashes Dump Binda-Stricha?

Hello Igor,

That would be great! In manuals where clients want to write Maschinen-Bau-Gesellschaft, I can activate the Limited fuzziness on the fly via the context menu :). In all other manuals I just let it turned off.



Hello Hans,

I will explore how to solve it although it might involve introducing some limited fuzziness to glossary matching.


Hello Igor,

That would require inserting regular expressions in my big glossary. Would it be possible to work the other way around: if a dash is spotted inside a word, followed by a uppercase letter (preceded by zero ore one space), CafeTran handles this like the do not match category and ignores the dash, while the following letter is interpreted as lowercase:

Sour segment:


Found in glossary as:


Hello Hans,

This binde-striche case seems like a good candidate for a regular expression:



I can imagine that other languages have similar needs. How about the l and d apostrophe, for instance? Or z and s in English?

Login to post a comment