William Bader 

I can confirm this behavior with terms that begin with other special characters like quotation marks. The entry appears in the Term Recognition window but cannot be "picked" up by AutoSuggest. It can be aggravating indeed.

If your translations of laws always follow the same pattern as the example you have given above (Abs. removed, the paragraph number added inside parentheses), you might be able to make use of the RegEx Autosuggest provider app available in the app store to get AutoSuggest to work and automatically insert the correct translation.

William Bader 

I can confirm this behavior with terms that begin with other special characters like quotation marks. The entry appears in the Term Recognition window but cannot be "picked" up by AutoSuggest. It can be aggravating indeed.

If your translations of laws always follow the same pattern as the example you have given above (Abs. removed, the paragraph number added inside parentheses), you might be able to make use of the RegEx Autosuggest provider app available in the app store to get AutoSuggest to work and automatically insert the correct translation.

Thank you very much for looking into the issue. I want to emphasize that AutoSuggest had no problem with the "§" symbol in earlier versions of Trados - versions through 2020 as far as I can recall.  When the problem first emerged (after an upgrade or possibly an update to a new release), I thought it was a settings problem and that, sooner or later, I would find the setting that would fix it. 

Apparently, in the process of improving Trados, the ability of AutoSuggest to pick up entries beginning with "§" (and possibly other special characters as well) was eliminated. Perhaps it could be restored in the future?

Thank you also for your workaround suggestion.  I do not think it is practicable as the citation example that I gave was very simple. Much longer citations (e.g.§ 15 Abs. 1 S. 1 Nr. 1 i.V.m. § 3 Abs. 1 Nr. 1 KapMuG  =  § 15 (1) sent. 1 no. 1 KapMuG in conj. with § 3 (1) no. 1 KapMuG) are common. 

Ouch, that is indeed difficult and non-practicable with my suggested solution.

The last thing I can think of: Possibly add the terms (or modify existing) without the § sign. Would be fairly straightforward I think to export, fix and re-import. Then they should be picked up again by MultiTerm (since leading numbers "still" work ).

Thank you again for giving the problem a lot of thought.  I apologize for my tardy reply; I don't log into the forum much.  I think that, for the time being, I will insert German statutory citations manually from the MultiTerm hitlist.  They are in the list, so if I click on an entry and select "show entry" (or something to that effect), it will appear in the Termbase Viewer window, where it can be copied and pasted into my text.