How do I fix the fontPath error in Android Studio?

Add tools:ignore='MissingPrefix' to the View or parent ViewGroup in your XML, and include the tools namespace xmlns:tools='http://schemas.android.com/tools'. This is a known IDE issue mentioned in the README.

Calligraphy vs Android's native font handling: which should I use?

Calligraphy simplifies font usage in XML for older Android versions, but with Android's built-in font features in API 26+, using fontFamily might suffice. For new projects, consider native options or migrate to Calligraphy 3 due to deprecation.

How to migrate from Calligraphy to Calligraphy 3?

Check the InflationX/Calligraphy repository for migration guides. Since this version is deprecated, update your dependencies and follow the new setup instructions to ensure compatibility and ongoing support.

Can Calligraphy be used with RecyclerView or lists?

Yes, Calligraphy works with any TextView, including those in RecyclerView. Ensure the hosting Activity's context is wrapped with CalligraphyContextWrapper, but note that performance might vary in dynamic lists.

How to apply multiple fonts in one TextView with Calligraphy?

Use SpannableStringBuilder with CalligraphyTypefaceSpan, as shown in the README. Create spans for different text segments and apply typefaces dynamically, but this requires manual code for each instance.

Is Calligraphy compatible with Data Binding or MVVM patterns?

It can be used with Data Binding by setting fontPath in XML, but given its deprecated status and potential conflicts, consider alternatives or ensure proper context wrapping in ViewModels or activities.

Open-Awesome

Calligraphy

Apache-2.0Javav2.2.0

A library for easily applying custom fonts to Android TextViews without custom views or ViewTree traversal.

GitHub

8.5k stars1.1k forks0 contributors

What is Calligraphy?

Calligraphy is an Android library that provides a simple way to apply custom fonts to TextViews without creating custom views or manually traversing the view hierarchy. It solves the problem of cumbersome font management in Android by allowing developers to define fonts directly in XML layouts, styles, and themes.

Target Audience

Android developers who need to use custom fonts in their applications and want to avoid the complexity of custom views or manual font setting in code.

Value Proposition

Developers choose Calligraphy because it drastically reduces boilerplate code, integrates seamlessly with Android's existing styling system, and provides a clear, hierarchical approach to font resolution that matches Android's attribute resolution logic.

Overview

Custom fonts in Android the easy way...

Use Cases

Best For

Applying custom fonts across an entire Android app with minimal code changes
Defining fonts in XML layouts for individual TextViews
Using consistent fonts through Android themes and styles
Supporting multiple typefaces within a single TextView using Spannables
Simplifying font management in large Android projects
Avoiding custom view subclasses just to set fonts

Not Ideal For

New Android projects or those targeting the latest API levels, as the library is deprecated and unsupported.
Applications built with Jetpack Compose or modern UI frameworks, since Calligraphy only works with traditional View-based layouts.
Teams requiring ongoing maintenance, security updates, or compatibility with future Android versions.
Projects where minimal third-party dependencies are preferred, due to the intrusive context wrapping and potential IDE errors.

Pros & Cons

Pros

XML Font Integration

Allows applying custom fonts directly in XML layouts using a custom fontPath attribute, eliminating the need for custom view subclasses or manual code.

Hierarchical Font Resolution

Supports font definition at multiple levels (View, Style, TextAppearance, Theme, Default), matching Android's native attribute resolution logic for consistency.

Spannable Support

Enables multiple typefaces within a single TextView using CalligraphyTypefaceSpan, as shown in the code example for dynamic text styling.

Theme and Style Consistency

Fonts can be defined in app themes and styles, ensuring uniform typography across the entire application with minimal boilerplate.

Cons

End-of-Life Status

The library is no longer maintained, with no updates, bug fixes, or support, and users are advised to migrate to Calligraphy 3, risking compatibility issues.

Intrusive Context Wrapping

Requires wrapping the base context in every Activity's attachBaseContext method, which adds boilerplate and can be error-prone in complex projects.

IDE Error Marking

The custom fontPath attribute is often incorrectly flagged as an error in Android Studio and IntelliJ, requiring additional tools:ignore attributes to suppress warnings.

Limited Framework Support

Does not support modern Android UI frameworks like Jetpack Compose, and has known issues with widgets like SwitchCompat that require custom subclasses for proper typeface setting.

Frequently Asked Questions

Related Projects

Guava: Google Core Libraries for Java

Google core libraries for Java

RxJava – Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.

Stars48,292

Forks7,592

Last commit2 days ago

ZXing Android-Integration

ZXing ("Zebra Crossing") barcode scanning library for Java, Android

Stars33,920

Forks9,431

Last commit4 days ago

RxAndroid

RxJava bindings for Android

Stars20,006

Forks2,941

Last commit1 month ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub