Skip to content

docs(figma): add troubleshooting for mixed fonts limitation #559

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.

Sign up for GitHub

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

Merged
andrii-bodnar merged 1 commit into from
Jan 6, 2026
Merged

docs(figma): add troubleshooting for mixed fonts limitation #559

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/content/docs/crowdin/integrations/figma.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -454,3 +454,14 @@ To avoid this:
* Check for missing font indicators (**A?**) before linking strings.
* Make sure the fonts used in the original design are installed and available in your Figma.
* If necessary, coordinate with the designer to confirm the correct font setup.

### Mixed Fonts Within Text Nodes

The Crowdin for Figma plugin does not support mixed fonts within a single text node due to technical limitations. This includes different font configurations, such as different font weights (e.g., 400 vs 700), even when using the same font family.

When you download translations to such text nodes, the plugin will apply the first font configuration used in the string to the entire text.

To avoid this issue:

* Ensure each text node uses a single font with a shared configuration for the entire text.
* Use regular formatting styles (bold, italic, etc.) instead of different font configurations to achieve visual emphasis.
11 changes: 11 additions & 0 deletions src/content/docs/enterprise/integrations/figma.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -454,3 +454,14 @@ To avoid this:
* Check for missing font indicators (**A?**) before linking strings.
* Make sure the fonts used in the original design are installed and available in your Figma.
* If necessary, coordinate with the designer to confirm the correct font setup.

### Mixed Fonts Within Text Nodes

The Crowdin for Figma plugin does not support mixed fonts within a single text node due to technical limitations. This includes different font configurations, such as different font weights (e.g., 400 vs 700), even when using the same font family.

When you download translations to such text nodes, the plugin will apply the first font configuration used in the string to the entire text.

To avoid this issue:

* Ensure each text node uses a single font with a shared configuration for the entire text.
* Use regular formatting styles (bold, italic, etc.) instead of different font configurations to achieve visual emphasis.