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

Regenerate DefaultTexFont.xml, update fonts #107

Open
ForNeVeR opened this issue Jan 27, 2018 · 7 comments
Open

Regenerate DefaultTexFont.xml, update fonts #107

ForNeVeR opened this issue Jan 27, 2018 · 7 comments
Assignees
Labels
kind:refactoring status:blocked For things blocked on other things.

Comments

@ForNeVeR
Copy link
Owner

ForNeVeR commented Jan 27, 2018

While working on #70, I found that our TTF files seem to not correspond to our font metrics. I think that we should get both TTF and TFM files from some consistent source and regenerate the DefaultTexFont.xml data.

Don't forget to publish all the scripts and clarify the documentation.

@alexreg
Copy link
Collaborator

alexreg commented Jan 27, 2018

Yep, or just extract the data on the fly. It would probably be just (almost) as quick. I remember considering doing this years ago...

@ForNeVeR
Copy link
Owner Author

Yes, I'm thinking about on-the-fly extraction. Although I'm not sure if all the data we need is available in the TTF files (as far as I can see, it isn't). Need to experiment more.

@alexreg
Copy link
Collaborator

alexreg commented Jan 27, 2018

Hmm. Could do on-the-fly extraction as much as possible, and then fill in the remaining data from a (much smaller) XML/JSON file? But yeah, have a closer look first. Maybe it's all there.

@ForNeVeR
Copy link
Owner Author

I think it's possible that our TTF files aren't the right one. Need to compare them with the latest officially published versions: maybe those include the kerning information.

@alexreg
Copy link
Collaborator

alexreg commented Jan 28, 2018

Yep. I would normally expect them to include kerning information, so worth a check...

@B3zaleel
Copy link
Contributor

B3zaleel commented Sep 1, 2018

They certainly aren't, because the font tables were manipulated. All alphabets seem to be in the same start range even though mathcal is not in Unicode. All alphabets should have a symbol mapping just like "sqrt" does then the convert character applies the text style prefix to the character(eg: 4 in mathrm is mupfour and Gamma in mathit is mitGamma). The kerning data is a lot harder to get through don't forget but they are only a few, and we could study it and get it. Currently I'm working on Asana Math font and the glyphs look so thick you might think you are in boldmath. Thus the blurry fonts are as a result of the fonts not the program. As at now the codebase is so glued to the default fonts, same as the other data and I've been working on opening it.

@ForNeVeR
Copy link
Owner Author

We should take a look at the https://github.com/himamis/ReTeX project. It looks like its auhors have replaced the original format with something less complicated. The metrics inside <FontDescriptions> look autogenerated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:refactoring status:blocked For things blocked on other things.
Projects
None yet
Development

No branches or pull requests

3 participants