<p dir="auto">I am not sure which package to blame for this but autocomplet does not work with non-ascii words.</p>
<p dir="auto">When I type eg. "Immat" I get the autocomplete proposal "Immaterialgut" but not "Immaterialgüter". I guess autocomplete does not work with non-ascii chars at all. Thatmay be ok for programmers but not for writers, because we have a lot of non-ascii words out there.</p>
<p dir="auto">Current implementation seems to break words on unicode characters - so when I write "somēthing" in the editor, it gets tokenised into "som" and "thing" for purposes of autocomplete.</p>
<p dir="auto">If I follow the code correctly, it's due to JS regex used at <a href="https://github.com/saschagehlich/autocomplete-plus/blob/master/lib/provider.coffee#L6"><code class="notranslate">Provider.wordRegex</code></a>  not being unicode-enabled.</p>
<p dir="auto">Possible solutions:</p>
<ul dir="auto">
<li>use a character whitelist <a href="https://github.com/saschagehlich/autocomplete-plus/blob/master/lib/fuzzy-provider.coffee#L61">like here</a>;</li>
<li>bring in unicode-aware library like <a href="http://xregexp.com/" rel="nofollow">XRegExp</a>;</li>
</ul>
<p dir="auto">Which would you rather see implemented - nasty regex without additional libraries, or cleaner regex plus additional dependency? Or something else entirely?</p>