Start a new topic

How to use pipe characters (|) in glossaries to indicate potential variable stuff?

Can someone give me the low-down* on adding stuff like 


to glossaries? Do I need to precede the entry with a pipe character, thus:


*low-down = ‘The true facts or relevant information about something.’

You can insert the pipe at the beginning to indicate that a source term is a regex. So it's not necessary in your example. BTW: What are you trying to achieve?

That was just an example of trying to catch anything starting with "waterpartij", but with different ending, such as "waterpartijen", "waterpartijxxx". Not a great example, but I just wanted to know if it needed to be preceded by a | or not.


So if it contains a regex: yes

if not: no.

I was hoping that I could say that by checking the box Look up word stems


The plural 'waterpartijen' would be recognised. Although this is often the case in German texts (with similar nouns with their plurals), I'm sorry to inform you that the Dutch Hunspell rules obviously aren't 'good/fine/precise' enough:


When I search the singular manually, it is found:


So, you could play a little with Prefix matching, to catch at least the plural, before you start inserting pipes. Of course, for words like waterpartijfilter (imaginary word) this won't work.

I'll do a quick test with a TM for terms now.

I know that you didn't ask this but I wanted to verify this for the record/myself and I can inform you that in a TM for terms, similar terms aren't recognised either (perhaps I should have tweaked some settings, I'm quite confident that if so, this will be reported):






No green highlights, indicating term recognition :(.

Still not sure what you are trying to achieve. I'd avoid to make entries to fuzzy, hoping to catch all. I'd advise grouping, if possible macrowise. Groot;grote = big // Grootte and grootheid are of course linguistically related but should get separate entries. No use for the Scottish piping squad here. I think that the pipe is of more use in agglutinating languages. The glossary should or rather could be set up following practical points of considerations rather than linguistic or even terminological or even lexicographical. Strange but oh so handy term nests like controleren;controleer;controleert u;controle = check;check for // the addition of the second target is very handy in combination with the feature to change the AA preferred target term. Note that the example above is a reversed EN > NL example. For your direction things could look completely different.

Yes, I know, it makes no sense what I was/am trying to do. I will try to explain: 

Sometimes, when I'm in a big hurry, but I still want to quickly create a termbase entry so I don't forget sth, but don't have time to give it much thought, I like to just put in a src term like exampleword|, hoping to catch all instance later on down the line. In these cases, my target entry might be a total mess (and thus be completely useless for AA ), but the entry might also contain a completed notes field with a bit of info, a URL, etc. 

Obviously, it would be insane to do this all the time, and I only do it once in a while, when in a hurry. So now you have some background info on my latest bad craziness. 

I'd be careful with this trick. Before you know it (Dutchism?), you get strange results that you cannot explain–because somewhere in 'a' glossary there is this pipe.


Login to post a comment