Currently the GUI the response of a saving request of a segment lasts until a saved segment comes termtagged from the server. On big Projects with big TBX files (and much traffic on the termtagger in general) saving of a segment will last for some seconds. Still the user can edit the next segments, as long as they are not repeated. If they are repeated, the user can only edit the next segment and then when he wants to save it has to wait for the completing of the saving of the previous segment. This gives the user a bad experience in using translate5.

Therefore the termtagging should be decoupled from segment saving. That means that the state of "not tagged" has to be ported to the frontend somehow, so that the user sees this, and the segment can be refetched from the server with the tagging informations.

Since this influences also the repetition editor and termtagging, this should also be checked.