Answers - Multi-Language Repo - Custom Font not Appearing in Secondary Locale

Search Best Practices - Search Front-End
1

Hey Team!

I am utilizing a multi-language repository to power the United States and United Kingdom answers experiences for my customer. Everything seems to be working correctly, with the exception of the Fonts.

The English version correctly reflects the custom font that was applied (“national2”), whereas the UK experience seems unable to show the correct font, and is instead using the fallback. Nothing in the CSS has changed, so I’m not quite sure what the issue is here.

Let me know what you think!

2

Hi Jessie!

It looks like there’s some issue with css inlining and multi-language repos (specifically multi language repos that add another folder level to the url, which is the default behavior). Will take a look! In the short-term you can disable css-inlining by removing the data-webpack-inline attribute from the bundle.css in html.hbs

3

Hey Jessie,

To add to that, you’ll want to

  1. Shadow the html.hbs file (using the Override Theme command)
  2. Remove the data-webpack-inline attribute

Ex starting code:

<link rel="stylesheet" type="text/css" href="{{relativePath}}/bundle.css" data-webpack-inline>

Ex with attribute removed:

<link rel="stylesheet" type="text/css" href="{{relativePath}}/bundle.css" >

Let us know if you have any questions!

Thanks,
Liz

4

Thank you Liz & Oliver! This did the trick :slight_smile: