Note for myself: The only reliable way to check for the comma is to use event.charCode (44 = comma) which is not present on keydown, instead keypress has to be used.
The issue lies deep inside the JavaScript class WCF.EditableItemList which is reused in a lot of places. In order to resolve this issue, I have to listen for the event keypress instead of keydown but unfortunately the key code (identifying which key was pressed) is incompatible. Exchanging the event will most likely break multiple deriving classes (including ones from 3rd party authors) and this is nothing one should do with a small bugfix release.
I will change it's behavior with WCF 2.1, but there will be no fix for WCF 2.0 for the above reason.
Which means some users (like myself) won't be able to use thread tags (and similar functions) until WCF 2.1... 
What can I do until then?
When is WCF 2.1 is due? I guess in a few months from now...?
What can I do until then?
Just fyi - my hashtag plugin correctly supports hebrew:
http://support.wcfhub.com/foru…p/Thread/100-Hebrew-Test/
Don’t have an account yet? Register yourself now and be a part of our community!
