It's the font our company decided to go w/ corporate-wide when we rebranded last year. It was Lato previous to that. I don't mind the Roboto font, this display issue on the other hand...
No worries, Matthew. We utilize SL and embed SL content into Rise as well. It's good to have a heads up of font 'wonkiness'-- even if it spilled into a Rise specific forum. :)
Chrome, Edge, Firefox (MS Windows 10) - No zoom, browser full-screen.
All modes, editing-previewing-shared link output
One of the dev's replied to my submission ticket yesterday and noted it as a bug.
**However** on a Mac w/ Safari or Chrome -- (just tried Linux w/ Chrome, same deal), the output is fine. Seems OS dependent. I've tried this on multiple computers, networks, and various users from our team. Same results as what I've found in out rendered on screen.
7 Replies
I also have this issue. It needs to be corrected before we use Roboto--which is unfortunate.
It's the font our company decided to go w/ corporate-wide when we rebranded last year. It was Lato previous to that. I don't mind the Roboto font, this display issue on the other hand...
The way MS Word renders output at those sizes w/ Roboto would be desirable compared to what Rise displays currently.
See attached.
No worries, Matthew. We utilize SL and embed SL content into Rise as well. It's good to have a heads up of font 'wonkiness'-- even if it spilled into a Rise specific forum. :)
Hi there, Cass. Thanks for the image.
One of the dev's replied to my submission ticket yesterday and noted it as a bug.
**However** on a Mac w/ Safari or Chrome -- (just tried Linux w/ Chrome, same deal), the output is fine. Seems OS dependent. I've tried this on multiple computers, networks, and various users from our team. Same results as what I've found in out rendered on screen.
See attachment for how it's displaying in MacOS.
Thanks, Cass. I appreciate you working through this with Ryan, and we'll be sure to update you as soon as we have more to share on this bug.
This discussion is closed. You can start a new discussion or contact Articulate Support.