Typing in many Latin languages generates diacritics using ‘dead keys’, which are prefix operators. (Originally, on a physical typewriter, these were keys that simply struck the paper without triggering the mechanism to advance the carriage.) If Unicode had taken this hint, life would be easier.
(ISO/IEC 6937 had prefix diacritics, but it was too late.)
Process whole strings, the meaning of a partial string may not be what you hope, even without fancy writing systems and Unicode encoding.
"Give the money to Steph" - OK, will do
"...enson" - Crap, OK, somebody chase Steph and get our money back, meanwhile here's James Stephenson's money
"... once he gives you the key" - Aargh. Somebody chase down James and get the key off him.
Either way there's already a recommendation in this area. I'm not sure if it strictly fits this particular scenario but the "UAX15-D3. Stream-Safe Text Format" suggests that you should support sequences at least 31 code points long.
That means that what Unicode today considers "one character" can be infinite in size.