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

Fontforge-2017-07-31-Windows-r2: Trying to select Galician in language dropdown instead selects Fulfulde #3274

Open
4 of 5 tasks
StrangerCoug opened this issue Mar 28, 2018 · 4 comments

Comments

@StrangerCoug
Copy link

StrangerCoug commented Mar 28, 2018

If you click Font Info under the Element dropdown, select TTF Names, click New, and try to select Galician under the language dropdown, the field is instead populated with Fulfulde. Clicking it again seems to indicate that both languages are selected despite being unrelated.

When reporting a bug/issue:

  • Screenshot
  • The FontForge version and the operating system you're using
  • The behavior you expect to see, and the actual behavior
  • Steps to reproduce the behavior
  • (optional) Possible solution/fix/workaround
@StrangerCoug
Copy link
Author

Made it a bit neater. Sorry; new here.

@StrangerCoug StrangerCoug changed the title Trying to select Galician in language dropdown instead selects Fulfulde Fontforge-2017-07-31-Windows-r2: Trying to select Galician in language dropdown instead selects Fulfulde Mar 28, 2018
@ctrlcctrlv
Copy link
Member

I assume this is due to the order of the languages in the list,but am not at home now so cannot try to replicate the bug. Does this happen to any other languages in the list? What happens if you edit the SFD file manually to use Galician (note: manual editing of SFD files is not supported, it should only ever be done for debugging purposes as you can easily corrupt your file. Keep a backup)?

@JoesCat
Copy link
Contributor

JoesCat commented Apr 2, 2018

@StrangerCoug thanks for the tidy-up :-)
@ctrlcctrlv - I very much suspect the problem is due to the lack of automation. The programs Unicode/makebuildtables.c, Unicode/dump.c, and Unicode/makeutype.c are given the task of building various tables, like making unicode9.0. The problem is that there are many locations scattered around fontforge that there appears to be a program missing to also build other tables too, so those tables may be at ver8, 7, or lower. I don't know when they got lost or if it ever existed, but there is no easy clue showing what possibly built them. For example combiners.h was brought-up from unicode3.0 to ver9.0 manually by hand, and manual means there is a probability of missing details. I also saw an earlier version of makebuildtables or dump.c that had code removed that helped build other sections, but the code in the resulting areas have had bug fixes, so the corresponding dump or make*.c also need upgrading, otherwise you need to stich/merge-in the new bug fixes.

If you want to do a quick-fix, you can take a quick look at library libuninameslist (the menu table will be similar to the drop-down menu, and you may likely see what's missing). The permanent fix would involve either dump.c, makebuildtables.c, makeutype.c (or low-probability - possibly another file that may have existed in 20120731 but not existing here now in 2017-07-31).

@StrangerCoug
Copy link
Author

StrangerCoug commented Apr 20, 2018

@ctrlcctrlv Sorry for the slow response. How do you do that?

Edited to add: I've figured out how to open the .sfd file in Notepad++, and I see a LangName of 2070 no, actually, it's 1127 next to the copyright text. I wouldn't know what this corresponds to.

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

Successfully merging a pull request may close this issue.

3 participants