8000 Update Oswald · Issue #58 · google/fonts · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update Oswald #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fowlerj opened this issue Jun 18, 2015 · 12 comments
Closed

Update Oswald #58

fowlerj opened this issue Jun 18, 2015 · 12 comments
Assignees
8000

Comments

@fowlerj
Copy link
fowlerj commented Jun 18, 2015

When using the font like this...

<link href='https://fonts.googleapis.com/css?family=Oswald:400,300,700|Quattrocento:400,700|Open+Sans:300italic,400italic,600italic,700italic,400,600,300,700' rel='stylesheet' type='text/css'>

... within a webpage rendered in IE10 when you print a document the text with Oswald will print the 's' character with these long lines that span over text below it until another element with Oswald begins. This can look like lines that span from h2 over numerous paragraphs until the next h2 is encountered.

The print previews all work without error, this only seems to be an issue when printing to a printer.

@adrientetar
Copy link

@fowlerj Did you mean to include an illustration?

@fowlerj
Copy link
Author
fowlerj commented Jul 2, 2015

I didn't realise that I needed three marks around code in markdown, my apology. I hope that the updated comment will suffice.

@davelab6 davelab6 added the bug label Aug 25, 2015
@davelab6
Copy link
Member

This is a known bug with earlier versions of ttfautohint. (Also Oswald family naming is not working in Word.)

@davelab6 davelab6 changed the title The font Oswald prints from IE10 with error on the 's' characters. Update Oswald with latest ttfautohint Aug 25, 2015
@ldeks
Copy link
ldeks commented May 7, 2016

Are there any plans to fix this? I love this font, but it doesn't print from Publisher 2013 correctly. I can workaround this by publishing to PDF before printing, but the other user of my document will hate having to do that. :)

Is there a way I can remove the ttfautohint command and rebuild the Oswald ttf file? I'm an experienced Linux developer.

@davelab6 davelab6 self-assigned this May 7, 2016
@davelab6
Copy link
Member
davelab6 commented May 7, 2016

Yes, you can use ttfautohint -d font.ttf out.ttf to de-hint the font.ttf and produce out.ttf, and then you can reapply ttfautohint using the latest version to out.ttf

I can't give an estimate of when this will be fixed

@davelab6 davelab6 modified the milestone: Update Families Jul 8, 2016
@davelab6 davelab6 modified the milestones: Update Families, Bugs Jul 8, 2016
@davelab6 davelab6 removed the bug label Jul 25, 2016
@davelab6
Copy link
Member
davelab6 commented Aug 8, 2016

This will be fixed with the new build from https://github.com/m4rc1e/OswaldFont

@davelab6
Copy link
Member
davelab6 commented Dec 9, 2016

https://twitter.com/kirstyatx/status/806986802741526530 says

@googlefonts Please fix the strangely sized punctuation in Oswald!

@davelab6 davelab6 changed the title Update Oswald with latest ttfautohint Update Oswald Dec 9, 2016
@laerm0
Copy link
Contributor
laerm0 commented Sep 12, 2017

Hm, I don't think the punctuation size in Oswald is odd. Or it isn't now, anyway. I think this can be closed.

screen region 2017-09-12 at 10 56 14

@davelab6
Copy link
Member

I've asked for confirmation on Twitter

@adrientetar
Copy link

The square part of colon/semicolon should sit on the baseline if you ask me, it's kinda levitating right now.

Punctuation could be larger indeed, e.g. if you look at Action condensed, right now it doesn't seem as black as the text.

@davelab6
Copy link
Member

Those are quality changes, not bug fixes... I'd rather tackle that across the collection than family by family.

@adrientetar
Copy link

"strangely sized punctuation" is a quality req indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
0