-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Custom fonts already possible in latest Support Library? #410
Comments
I guess one reason I'm still using this library is because custom font support, even with the support library, is currently still difficult. |
I also think this lib is deprecated now |
If anyone's wondering why I still use this library, here's my story on Twitter: https://twitter.com/azriaba/status/978832315613786112 TLDR; I couldn't get bold & italics to work properly with custom fonts on certain phones. |
Oh, I guess I found a "solution". Instead of creating a font family file, calling the font file directly with the android:fontFamily attribute solved my problem.. but the docs never mentioned anything about that. |
So yes it's offically supported, but 1. its API 26+, most people don't use that yet! 2. Not all devices have play services app... YMMV |
@chrisjenx, if you use support library it will work from Android 4.1 (https://developer.android.com/guide/topics/ui/look-and-feel/fonts-in-xml). You also don't need any play services for this feature. |
So I agree with the starter of the issue that technically Calligraphy is not required anymore. |
Hi! Looking at the issue on google you mentioned in your documentation, looks like it's already supported in the latest release of the Support Library. Maybe you can update the doc to show why developers should use this library regardless?
The text was updated successfully, but these errors were encountered: