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
Using latest material design TTF font #87
Comments
Is the font family set in your custom IkonResolver the appropriate one? |
No. I left the family the same as Material Design and yes I am using the material design pack at the same time. |
I'll perform another check. Based on https://github.com/Templarian/MaterialDesign-Font the font family in version |
and that is what I have. public String getFontFamily() { I switched to the TTF in the https://github.com/Templarian/MaterialDesign-Font link.
The site map2 throws the width exception. site map works fine. |
Same icon code but different description yet one fails and the other succeeds? Now that's indeed weird. I wonder what else could cause this. |
No idea why. I made sure to use the same code. BTW, I never see the AbstractIkonHandler#getFontFamily being called. The only thing I can think of is some conflict with the existing material design. The exception for the record: |
I see. Swing's |
So I removed the existing material design and it still fails. Then I replaced the TTF with the one from your distribution (2.6) and that worked. No code changes. The problem is I need the latest. |
As far as I can tell the latest uses codepoints that are beyond a single char (2 bytes) which is the limit currently supported by Ikonli. mdi-access-point in 1.7.22 is at f002 |
Oh thank you. That's a lot of enums to rewrite to support the int limit. |
Hello,
Thank you for the great product. We see fonts on the https://materialdesignicons.com/ website that we would like to use and have no equivalent enum. We use Java 8 with Swing so are stuck with the 2.6 release. We did the following:
The only thing I suspect is the way the TTF is imported. Any pointers will be greatly appreciated. Again, thank you for a wonderful project.
Tarek
The text was updated successfully, but these errors were encountered: