So now, in order to toggle a feature on and off, you need to click twice: one time on the select box, and the second time on the wanted option.
I suggest changing it to radio buttons, so you can save that one click, something like this:
![Image](https://i.imgur.com/MW8GiF9.png)
Thoughts?
It came to our attention that HarfBuzz (the shaping engine used in Firefox and Chrome) uses a three state for features, even the though the specs only mention two (active and inactive features). This is an issue with init, medi, fina, and isol, where HarfBuzz by default applies input selectively, but if a feature is on, it will be applied for all glyphs in the text. We are not sure if it affects other features as well. That is why we made a generic solution.
I understand, thanks for explaining. I kept it that way – there's all three options: default, on, and off.Erwin Denissen wrote: ↑Sat Apr 04, 2020 8:46 amIt came to our attention that HarfBuzz (the shaping engine used in Firefox and Chrome) uses a three state for features, even the though the specs only mention two (active and inactive features). This is an issue with init, medi, fina, and isol, where HarfBuzz by default applies input selectively, but if a feature is on, it will be applied for all glyphs in the text. We are not sure if it affects other features as well. That is why we made a generic solution.
Great idea! very nice and organized.Erwin Denissen wrote: ↑Sat Apr 04, 2020 8:46 am
We consider adding the web test template files to
C:\Users\<yourname>\AppData\Roaming\FontCreator13\WOFFTest\
We can then also include a preview.txt file.
That way it is more convenient for users to make modifications.
That's ok, I trust you can find a better solution for RTL users.Erwin Denissen wrote: ↑Sat Apr 04, 2020 8:46 am
I'm not sure if the proposed way to set RTL is what we prefer, but I like the other suggested enhancements.
Me neither.Erwin Denissen wrote: ↑Sat Apr 04, 2020 8:46 am
I'm not sure what fails with the display of Hebrew characters, as it seems FontCreator correctly stores the file as utf-8.
Why is it not? It should be, in order to view most glyphs currently (in Hebrew and other languages too, I suppose).
Sorry, of course! I take it for granted because its my mother language.Erwin Denissen wrote: ↑Sat Apr 04, 2020 4:02 pm No, I don't have a clue about the RTL request. Can you explain a Dutch guy who only knows Latin script why it is important? Does it look better, or is there another reason?
You're right, cookies are not the best solution,Erwin Denissen wrote: ↑Sat Apr 04, 2020 10:03 pm Thank you for clarifying the importance of RTL.
I don't think cookies work local, and I don't like this approach.
See:
https://stackoverflow.com/questions/860 ... -html-file
But a settings.dat is also a nice option too for later extension.Erwin Denissen wrote: ↑Sat Apr 04, 2020 10:03 pm Maybe we need a settings.dat file with some optional settings. We can extend it later if there is a need for it.
I think there are also issues with localstorage:Hafonton wrote: ↑Sat Apr 04, 2020 10:25 pm You're right, cookies are not the best solution,
Thats I why I didn't use cookies, I used local-storage (similar to cookies but different, no need for server or local files, just a browser).
You can read about it here:
https://developer.mozilla.org/en/docs/W ... calStorage
And here's a video to demonstrate that it works perfectly: https://imgur.com/utYlaQQ
It works with the solution I attached in my last comment (where I attached wofftest.js file)
I'll see what we can do to make a setting file.