The Rise sidebar menu font is set by design, but thanks for letting us know you'd like to change that font setting. If we add this customization option to Rise in the future, we'll let you know!
I’m sorry that you’re having a problem here. If you’re trying to use characters that are not in the default font the browser will choose the next available font. That looks to be what is happening here.
We have a feature request logged to allow for special characters in other languages within the default font, but it’s not something available right now.
I’ve included your question in the feedback to our product team. If I can help with anything else, please let me know.
I don’t currently have any updates, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.
Reminding you that there is still no solution to this. Lato does not support a number of languages.
I have applied the fix in the OP's comment for Turkish, and despite changing the <style>...</style> tags, Lato still keeps coming back and replacing my custom fonts
Thanks for your feedback. I don’t currently have any updates on this, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.
In the meantime, if there's anything else I can do to help, please let me know!
I have the same problem with some courses in Czech and Romanian. Even though the text seem to be ok on the preview (except for the menu), once the course is published for the web, the diacritics change to what I presume is Times New Roman.
I would also like to add my name to the list of people requesting for this to be a feature to be implemented as this is affecting a large number of the languages we use for our courses.
We have found a temporary solution, until we wait for an official fix.
In any RISE export, inside "(\scormcontent)\lib\main.bundle.js" you have to replace all "!important" entries in the JS code with a blank entry. In this way, all the "!important" tags in the generated CSS code will no longer be there and there shouldn't be any hierarchy left, other than what is written by default in index.html and perhaps in .css files, but with this you can now freely adjust the hierarchy and make changes at will in all of these files, which you couldn't before as the hierarchy set by the JavaScript would always be higher.
Here's an example with Notepad++ in making these changes:
Any more advanced text/code editor can do this, example with Visual Studio Code:
So far we haven't found any problems with this, but everyone who also had an issue here, we invite all to test this with their RISE courses and give further feedback here.
We have found a temporary solution, until we wait for an official fix.
In any RISE export, inside "(\scormcontent)\lib\main.bundle.js" you have to replace all "!important" entries in the JS code with a blank entry. In this way, all the "!important" tags in the generated CSS code will no longer be there and there shouldn't be any hierarchy left, other than what is written by default in index.html and perhaps in .css files, but with this you can now freely adjust the hierarchy and make changes at will in all of these files, which you couldn't before as the hierarchy set by the JavaScript would always be higher.
Here's an example with Notepad++ in making these changes:
Any more advanced text/code editor can do this, example with Visual Studio Code:
So far we haven't found any problems with this, but everyone who also had an issue here, we invite all to test this with their RISE courses and give further feedback here.
Thank you! Really helpful workaround! It works fine for me!
27 Replies
Change them in the player settings to choose the player font
Do you mean here?
because if so, that's the easy bit. the part I want to re-style is the side bar:
The font's seem to stay as Lato.
Hi Mark!
The Rise sidebar menu font is set by design, but thanks for letting us know you'd like to change that font setting. If we add this customization option to Rise in the future, we'll let you know!
Thank you for the clarification!
Hello,
I have a problem with latin extended characters (Czech language) in menu which are not in the right font. See picture attached.
Is there any solution for this problem?
Hi Lucie,
I’m sorry that you’re having a problem here. If you’re trying to use characters that are not in the default font the browser will choose the next available font. That looks to be what is happening here.
We have a feature request logged to allow for special characters in other languages within the default font, but it’s not something available right now.
I’ve included your question in the feedback to our product team. If I can help with anything else, please let me know.
Is there a solution for this or any update?
Hi Vipul,
Thanks for reaching out!
I don’t currently have any updates, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.
Reminding you that there is still no solution to this. Lato does not support a number of languages.
I have applied the fix in the OP's comment for Turkish, and despite changing the <style>...</style> tags, Lato still keeps coming back and replacing my custom fonts
Hi Brian,
Thanks for your feedback. I don’t currently have any updates on this, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.
In the meantime, if there's anything else I can do to help, please let me know!
This is deeply affecting courses my team are trying to create. Using the Romanian language, the diacritics are broken in the menu.
Same with Russian. UI CSS in RISE is inline not in CSS file. Fix that, please!
Hello,
I have the same problem with some courses in Czech and Romanian. Even though the text seem to be ok on the preview (except for the menu), once the course is published for the web, the diacritics change to what I presume is Times New Roman.
Hello, Hugo. It sounds like the menu text is displaying in a default font rather than your custom font, is that right?
We're looking at ways we can allow for custom fonts in the sidebar menu. If we make a change to this feature in the future, we'll let you know!
I also have a font problem in the menu and start buton. It's been a long time but it's not fixed. Can you specify when to fix this?
Hi, Haluk. I'm sorry I don't have an update on using custom fonts in the outline and start button right now. I'll let you know here if that changes.
I would also like to add my name to the list of people requesting for this to be a feature to be implemented as this is affecting a large number of the languages we use for our courses.
Hi, I have a similar issue with special characters in the sidebar menu in Polish.
What is weird - in the preview everything is ok, when published - characters are replaced.
When can we expect the issue to be fixed?
Can you please replace sidebar menu font with something more universal?
Kind regards,
Marta
This post was removed by the author
Hi Marta! Thanks for your question! We can keep the conversation going in this discussion, if you'd like.
Hello, a lot of time has passed and we are still waiting and waiting. Is there a solution for this or any update?
Hi Talentator,
We don't have any updates for now, but we will let you know as soon as we have one.
Thanks for checking in.
Hello again,
We have found a temporary solution, until we wait for an official fix.
In any RISE export, inside "(\scormcontent)\lib\main.bundle.js" you have to replace all "!important" entries in the JS code with a blank entry. In this way, all the "!important" tags in the generated CSS code will no longer be there and there shouldn't be any hierarchy left, other than what is written by default in index.html and perhaps in .css files, but with this you can now freely adjust the hierarchy and make changes at will in all of these files, which you couldn't before as the hierarchy set by the JavaScript would always be higher.
Here's an example with Notepad++ in making these changes:
Any more advanced text/code editor can do this, example with Visual Studio Code:
So far we haven't found any problems with this, but everyone who also had an issue here, we invite all to test this with their RISE courses and give further feedback here.
Thank you! Really helpful workaround! It works fine for me!