Text font is different on translated pages

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are using the Xstore theme and WPML for translations on your site and have noticed that some theme text fonts differ from the original language on translated pages. The issue appears to be that the font is not found for the translations and defaults to a different font.
Solution:
First, verify if the font issue is related to the specific characters of the language by deactivating WPML and viewing the page in another language using a primary domain. This can help determine if the problem persists without WPML. If the issue remains, it suggests that the problem might be with the FUTURA font itself, rather than WPML. Consider checking the font settings in your theme or consulting with the theme provider for more specific guidance on font management.

If this solution does not resolve your issue or seems irrelevant due to updates or differences in your case, we recommend opening a new support ticket. Additionally, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please contact us through our support forum at WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Exception

This topic contains 4 replies, has 0 voices.

Last updated by Andrey 1 month ago.

Assisted by: Andrey.

Author	Posts
June 11, 2025 at 4:12 pm #17127105
martinK-154	Background of the issue: I am using the Xstore theme and WPML for translations on my site hidden link. I am trying to ensure that the text fonts on translated pages match the original language. Symptoms: Some theme text fonts are different from the original language on translated pages. It seems like the font is not found for the translations and defaults to a different font. Questions: Why are the text fonts different on translated pages? How can I ensure the correct font is used for translations?
June 11, 2025 at 6:23 pm #17127604
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for contacting WPML support. Could it be that the font you’re using displays characters differently when it is not Estonian? Do you clearly see a font difference in the code somewhere (for example, when inspecting the page with the browser console)? You could try temporarily deactivating WPML and viewing the page from another language (using a primary domain) to compare the results. Alternatively, try creating a test English page under the Estonian language and see if the issue persists.
June 13, 2025 at 4:53 pm #17134318
martinK-154	I checked with inspect element. It shows the right font family but displays wrong one. It says futurab on both translated pages and the original. I tried deactivating wpml but it still shows the fonts differently. For some reason it is only that font that shows differently on translated pages. Other texts and fonts are all fine. I also tried changing the Headings font in the themes settings. It seems that every other font works just fine. The problem is only when I use FUTURAB font.
June 13, 2025 at 5:00 pm #17134324
martinK-154	I guess the problem is only with the fonts that are uploaded manually (picture below). On translate domains backend all the uploaded font in theme settings are showing the same default font.
June 16, 2025 at 12:15 pm #17138560
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for your feedback. Could you please clarify what your secondary domain is? “I tried deactivating WPML but it still shows the fonts differently.” Could you elaborate on this point? If the issue persists even with WPML deactivated, then it’s likely unrelated to WPML. I suspect the cause might be the FUTURA font itself, as you mentioned.