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:
It's even worse. After posting the previous message, I got this segment:
Folgende Export -Möglichkeiten stehen zur Verfügung:
Yes, this is all a matter of Schlampigkeit. But that's not relevant here. Fact is that this sloppiness is slowing me down unnecessarily. The introduction of a switch:
[x] Ignore hyphen and leading/trailing space in glossary entries
would be a great improvement for me.
I'm just afraid that this would require a complete overhaul of the glossary code.
The underlaying question is: To what degree should a CAT tool cater for human errors and sloppiness?
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
I said silence!
Must I come over with a wooden hammer?
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.
Case closed. Problem solved. Moving on to a new challenge.
How about this one:
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.
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.
It's quite easy: put them where they are needed.
How about this one:
die Standard Maschinen - Konfiguration
Oh man ...
I can imagine that other languages have similar needs. How about the l and d apostrophe, for instance? Or z and s in English?
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.
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?