Roboto Typeface not rendering correctly even after update

James Brooks shared this problem 1 year ago
Solved

The attached image tells the story much better than my words. Please review it.


Roboto Medium renders as heavier than Roboto Bold. The hierarchy of font weights is not correct and it's impacting my ability to design every day.


Roboto is our main platform font and Medium is our main highlighted font weight... but I can't use it. I have to use Bold instead. And then I have no Bold to contrast against it.


Anyway... just look at the image... it's immediately obvious.

Furthermore, the JiM editor is artificially 'squashing' the typeface as well. Look at the letter o in both examples... it should have a slight oval shape like the Illustrator example... however, in JiM it's perfectly circular as if the whole thing were being squashed downward by a few pixels.

It's just not rendering Roboto correctly... across the board.


Please fix this asap.

Comments (16)

photo
1

+1. I'm not sure why Roboto is so messed up, since you can freely download it from Google Fonts, but it's going to be a very common need for anyone who designs Android apps or uses Material.

photo
1

Hi all,


Thanks for letting us know you're seeing this error. We're working on fixing this right now, and I'll get back to you ASAP with more info.


Apologies for any inconvenience.


Best,

Danielle

photo
1

Hi all,

We're currently looking into this issue. For further investigation from our engineers we will need the following information:

1. Which OS are you using? And version?

2.Are you using any font manager?

3. If possible, can you try installing the Roboto font directly from Google and let me know how this works for you?

Thank you in advance.

Sonia Durán

photo
1

Thanks for looking into this


Currently on


Lenovo Thinkpad

Windows 7 Enterprise - 64-bit

Service Pack 1

Intel i7

20 GB Ram


Not using a font manager.


Already had Roboto downloaded from Google but for the heck of it I uninstalled and reinstalled it and did the test in JIM and it still looks incorrect. I've attached a screenshot of what I was just seeing in the editor... which looks the same as the 1st one I attached. The weight hierarchy is incorrect and some of the weights also seem to be getting squashed downward somewhat... it's very obvious on Regular weight... all the o's look like circles instead of ovals.

photo
photo
1

this was an accidental comment... ignore. (but still keep trying to fIx roboto!) :-)

photo
1

Currently on


Apple Macbook Pro


MacOs Sierra 10.12.5


No font manager.


I tried the same things as James-uninstalling and reinstalling.

photo
1

I am having a similar issue using a new Google font which I downloaded with the new version of JIM. The font is downloaded however it isn't render in simulation mode or when using the app on the phone.


Apple Macbook Pro

MacOs Sierra 10.12.5

No font manager.

I tried the same things as James-uninstalling and reinstalling.

photo
1

Dear Robert,


We have launched a new update 8.0.1 to solve the fonts issue. Can you try updating and let me know how it goes?


Best,


Sonia Durán

photo
photo
1

So I saw that there was an update relating to Fonts.

It claimed to be a fix for the issue where characters were getting garbled in the editor.

I updated the editor and checked and now I'm not only having the issue where the Roboto weights are incorrect now I'm also seeing the garbled text that was supposedly fixed in 8.1


I've attached another image so you can see what I am seeing.

photo
1

Dear James,


Can you try to uninstall the Roboto font from your computer? That should fix the issue.


Best,


Sonia Durán

photo
1

Sonia,


I just opened a prototype on my home laptop. It was at 8.0. It was able to display Roboto Light normally. Although I WAS still having the aforementioned font weights issue where Medium was heavier than bold I wasn't having a problem displaying the characters themselves.


So I just updated the prototype to 8.0.1 and now all the characters are garbled, just like on my work laptop (which also had no problem until I upgraded to 8.0.1 and now displays completely garbled characters in the editor as well)


I tried uninstalling Roboto, restarting my laptop, reinstalling Roboto, and reloading the prototype... still the same result.


In the editor the characters look like Gaelic when I'm typing and when not selected they just look all jumbled and overlapping.


In the simulation everything looks normal.


To recap:


2 laptops updated w 8.0.1

Both had Roboto uninstalled and reinstalled

Both are displaying incorrect font weights

Both are showing two different garbled character views in the editor.


Thanks for your continued investigation of this matter

photo
1

Dear James,


Can you try uninstalling Roboto from your computer without reinstalling? Then restart Justinmind.


Let me know how this works for you.


Best,

photo
1

Before I tell you if it works or not I'm going to tell you that it's not a viable solution either way.


You simply cannot tell users to NOT use a font on their computer in order that they CAN use it in your application.


I need this font to be available to Photoshop, Illustrator, Powerpoint, etc... if it's not installed on my computer I cannot use it in any other program.


So that said, when I remove Roboto from my pc it works normally in JustInMind. But ONLY in JustInMind.


So please do not resolve this or consider it fixed.


It's not.


I'm now going to reinstall Roboto so I can use it in all my other software and I'm going to await a real fix from you guys.

photo
2

Look for the Roboto font inside the Justinmind folder and install the one that comes with Justinmind. After doing this, you shouldn't have any other issues with this font, and will be able to use it in any other application.

photo
2

I'm happy to report that this worked great.


My other programs are happy with this version of Roboto and everything is looking good in JIM now, as well.

photo
photo
2

Ultimately... users shouldn't have to install a separate version of Roboto from the JustInMind folder.

But for now this worked really well and you can mark this issue as resolved.