search

breezieb / googlefontdirectory

Automatically exported from code.google.com/p/googlefontdirectory
0 stars 0 forks source link

Roboto V2 "Regular" variant defaults to "Black" variant #325

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Remove any existing Roboto fonts on your Windows machine.
2. Download the latest Roboto V2 from 
http://www.google.com/design/spec/style/typography.html and install them on a 
Windows machine.
3. Try using both Regular and Black variants on some text in a photoshop 
document and they are both appear identically black.

What is the expected output? What do you see instead?

Roboto V2's Regular font variant should act as a Regular variant. Instead the 
Regular variant results in the Black variant due to an incorrect naming of the 
font internally.

What version of the product are you using? On what operating system?

Roboto Version 2, Windows 7

Please provide any additional information below.

You can see in this screenshot here: http://cl.ly/image/0y1f321V2127 that I've 
opened both the Regular and Black Roboto V2 variants with the windows font 
viewer. The Regular variant is the top window while the Black variant sits 
behind it. You will notice the window titles are identical though even though 
the fonts are clearly different in size. This results in Windows treating 
"Regular" as "Black" and therefore negates Regular from working properly.

Solution:

Correct the font Roboto V2 Regular font name so it says "Roboto Regular" 
internally and re-upload fonts again for download.

Original issue reported on code.google.com by QKSI...@gmail.com on 6 Aug 2014 at 7:33

GoogleCodeExporter commented 9 years ago 
I wrote a script to fix the font family naming, using the Python ttx library, a 
couple months ago:

https://gist.github.com/codeman38/9d77f650a875639a55e6

Original comment by codeman38 on 22 Aug 2014 at 4:30

GoogleCodeExporter commented 9 years ago

Original comment by pathum...@gmail.com on 27 Sep 2014 at 10:58

GoogleCodeExporter commented 9 years ago 
Fixed upstream in the latest version available from AOSP - the variants all 
have unique names on Windows now:

https://android.googlesource.com/platform/frameworks/base/+/master/data/fonts/

Original comment by codeman38 on 7 Nov 2014 at 9:40

GoogleCodeExporter commented 9 years ago 
@codeman38

This appears still unfixed in the latest master. I've pulled those files down 
from the master tgz link here: 
https://android.googlesource.com/platform/frameworks/base/+archive/master/data/f
onts.tar.gz

If you open both regular and black variants you will see identical "black" 
variants in the title on Windows. It's not the actual "filename" that needs 
changed if that was what you were referring too.

Original comment by QKSI...@gmail.com on 9 Nov 2014 at 9:40