You have to manually delete the old FontCreator.exe and then reinstall the update.
Let me know your results.
It is strange that the new version of FontCreator.exe didn’t come through. Same issue here, but it is really awkward.
Second, the installer will always overwrite the WOFFTest files. In the future that might break new functionality if people use custom files within their AppData folder.
That did it!
Both functionalities you mentioned worked. 
Thanks for taking the time to help with that.
That’s fine, I did my backup. But I prefer using your up-to-date WOFFTest anyway.
For this thread what’s left is the rtl option
Within the generated html page does it show initialdir=“RTL”?
No. The default text is ltr.
I looked at the source code and it says
var initialdir = "LTR";
By the way, the Hebrew glyphs are shown fine no more utf-8 problems.
Its showing the Hebrew alphabet as the default text, which is very nice.
Is that going to be editable in the future? (the options file)
I thought it would work on your side, as it is determined by a local setting on your system. Not sure which one, but it apparently failed.
You might need to force it:
var initialdir = "RTL";
I forgot to tell it, but the files are already working through the User Data Folder.
Just go to the Options dialog, and click Copy… on the Advanced tab.
Then you can open the folder and edit the files to your liking. No need to restart FontCreator for these changes to take effect. Just do another WOFF test and it should catch the changes.
We will change the preview text samples. It would be nice if we could collect a couple for each commonly used script/ language.
Oh, cool thought.
I use Windows 10 with english though (its just my perference), that’s probably why it didn’t work as you expected.
Okay, I can do that.
Will I need to force it on each FC update?
What about if you make changes and enhancements in the WOFFTest files when a new FC update comes? I’d like to get the updates too.
It would be nice if I didn’t need to force it every update.
Wonderful!!! I just tried that and it worked like magic.
I very much appreciate your hard work and great customer support.
Well, the benefit of copying the data to a folder where you can edit them has a drawback as future updates of these files are not picked up if they come with a minor update of FontCreator. Keep an eye on the changelog to see if we made any changes to those files.
I understand.
Can we fix that by applying the localstorage function I wrote?
It works fine. You can test it
It doesn’t seem to work with good old Internet Explorer. For now you can use the manual fix I suggested.
I see.
Well, I’ll live with ltr as the default, because I prefer to always be up-to-date with your changes. (Its just more important to me).
But thanks for the manual fix you suggested. 
We’ve just released an update, available through the Check for Updates feature within FontCreator.
Thanks!
The dragging option when kerning works.
Hi
I have notice some incorrect mark positions in Arabic text inside web test font window, i have correct it in the attached file… thanks
webestarabic.txt (550 Bytes)
Thank you for the corrections. It will be part of the next update.
Not at all, Great.. thank you Mr. Erwin