Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

text-based lookup tables #4925

Open
aminabedi68 opened this issue Mar 5, 2022 · 3 comments
Open

text-based lookup tables #4925

aminabedi68 opened this issue Mar 5, 2022 · 3 comments

Comments

@aminabedi68
Copy link

aminabedi68 commented Mar 5, 2022

Hi
i think work with lookup tables(i mean line to line tables) should be much easier. it's very hard to input and edit data into them.
here is an idea: a text-based environment for write the afdko feature codes(like new fontlabs) or (for those line to line tables)using XML data structure or even simple separators to compile text like a table for fontforge. respectfully i think the biggest problem for this kind of issues is the priority, because fontforge developers didn't use it like regular users.

@skef
Copy link
Contributor

skef commented Mar 5, 2022

It's already possible to import AFDKO feature files.

@aminabedi68
Copy link
Author

yes, but I mean internal afdko editor WITH fontforge tiny gui tools like glyph description and picker... as i said above(for emphasis, elaborate and give you a different point of view): i think fontforge developers should use fontforge like a noob users too, i saw the power of python scripting or internal codes before but i spend a lot of time inside gui yet because i can't deal with tones of codepoint names... today i had to input a large amount of data through the gui, beacuse i needed the codepoint descriptions(showing characters in parents, one of the best fontforge's helpers) to see what is going on...It was really bad experience. this is not a personal problem(i have a lot of bigger problem with fontforge), no offence skef, i appreciate your works here, i really do, but I can't see a considerable improvement in user experience through this years. I think we need to fix bad experiences more than anything.

@skef
Copy link
Contributor

skef commented Mar 5, 2022

As always, it's possible to code new functionality for alternate means of doing things but the challenge is finding people interested in doing the work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants