You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2024. It is now read-only.
This is just a feature proposal. I don't know if it's easy or hard to implement. Maybe it's easy, I don't know.
Background: often some translators use some fonts that cause issues and, no matter how hard those are educated not to use those fonts, once in a while they forget it. By using using a font whitelist this issue can be reduced a lot.
Proposal: allow a font whitelist to be configurable. This whitelist may just hide non-whitelisted fonts in the font selector, or not render those, what you think is easier (or best) to implement. This configuration doesn't need a UI as, at least how I think it can work, this configuration is provided to the translators along a portable Aegisub build.
Alternative ideas: if it's hard to be implemented in the fork like proposed then other solution would be making a private fork with a hardcoded whitelist. In the other hand, if there are other people having the same issues, making it a configuration would be better as each group can adjust it as their needs. Also I think adding a blacklist of fonts would not be a good idea as this list would be harder to maintain.
The text was updated successfully, but these errors were encountered:
This is just a feature proposal. I don't know if it's easy or hard to implement. Maybe it's easy, I don't know.
Background: often some translators use some fonts that cause issues and, no matter how hard those are educated not to use those fonts, once in a while they forget it. By using using a font whitelist this issue can be reduced a lot.
Proposal: allow a font whitelist to be configurable. This whitelist may just hide non-whitelisted fonts in the font selector, or not render those, what you think is easier (or best) to implement. This configuration doesn't need a UI as, at least how I think it can work, this configuration is provided to the translators along a portable Aegisub build.
Alternative ideas: if it's hard to be implemented in the fork like proposed then other solution would be making a private fork with a hardcoded whitelist. In the other hand, if there are other people having the same issues, making it a configuration would be better as each group can adjust it as their needs. Also I think adding a blacklist of fonts would not be a good idea as this list would be harder to maintain.
The text was updated successfully, but these errors were encountered: