This is updated on the backend when ngrams are updated.

Merge branch 'dev-doc-annotation-issue' of ssh://gitlab.iscpif.fr:20022/gargantext/purescript-gargantext into dev-merge

Merge branch 'dev-multi-term-selection' of ssh://gitlab.iscpif.fr:20022/gargantext/purescript-gargantext into dev-merge

Instead of modifying state (which causes rerendering and removal of
current selection), we use refs.

This has the drawback of delayed popup showing, unfortunately (this
happens when backend send the periodic PUT message).

Also, some fixes to react component errors.

Merge branch 'dev-multi-term-selection' of ssh://gitlab.iscpif.fr:20022/gargantext/purescript-gargantext into dev-merge

Instead of modifying state (which causes rerendering and removal of
current selection), we use refs.

This has the drawback of delayed popup showing, unfortunately (this
happens when backend send the periodic PUT message).

Merge branch 'dev-doc-annotation-issue' of ssh://gitlab.iscpif.fr:20022/gargantext/purescript-gargantext into dev-merge

Merge branch 'dev-doc-annotation-new-term-no-spaces' of ssh://gitlab.iscpif.fr:20022/gargantext/purescript-gargantext into dev-merge

It is not enough to normalize terms on the backend, because the frontend
isn't fully aware of this (there isn't a "corrected" patch being sent,
after the term is committed). Therefore we perform some normalization
here (stripping spaces). However the `normNgram` function is used both
for sending terms and highlighting them later. Too much normalization
will lead to incorrect highlights.