Italics #2

Open
jmuyskens opened this Issue May 18, 2014 · 48 comments

Projects

None yet
@jmuyskens

Are italic versions in the works?

@frankrolf
Member

Yes, Italics are in the making.

@frankrolf frankrolf closed this May 19, 2014
@pauldhunt

Frank, you may want to leave this open so that interested parties can see that this is a know issue and know the status of it.

@frankrolf
Member

Right, I have been thinking about this also.
I decided to close this because it is not inside the scope of the current project. I understand an issue to be more of a technical problem with the current project.
Italics are planned, on the roadmap and partly in production even, so that is all I can say at this point.

@ryanstewart

I'd also vote for leaving this open. In general, closing an issue on Github means it's been resolved (either as a "we aren't going to do this" or a "we've done this"). Keeping it closed will encourage others to open the same issue. Plus, by keeping it open, it's more visible so people can keep tabs on it.

@frankrolf
Member

Yeah, but then we get millions of “+1” emails, as seen with Source Code Pro.
Can’t it mean “Yes, we are doing this?”

@ryanstewart

I think you can unsubscribe from a specific comment thread if you want with the "Unsubscribe" button to the right.

And sure, it can mean whatever you want it to mean. It's just not the way other Github projects handle it. So you may start to see people creating a new issue for it. But if not, then that's a good indication that this way works!

@adrientetar adrientetar referenced this issue in rust-lang/rust Jul 8, 2014
Merged

webfonts: fixes #15530

@bors bors added a commit to rust-lang/rust that referenced this issue Jul 9, 2014
@bors bors auto merge of #15530 : adrientetar/rust/proper-fonts, r=alexcrichton
- Treat WOFF as binary files so that git does not perform newline normalization.
- Replace corrupt Heuristica files with Source Serif Pro — italics are [almost in production](adobe-fonts/source-serif-pro#2) so I left Heuristica Italic which makes a good pair with SSP. Overall, Source Serif Pro is I think a better fit for rustdoc (cc @TheHydroImpulse). This ought to fix #15527.
- Store Source Code Pro locally in order to make offline docs freestanding. Fixes #14778.

Preview: http://adrientetar.legtux.org/cached/rust-docs/core.html

r? @alexcrichton
b53f3e7
@miguelsousa miguelsousa reopened this Dec 12, 2014
@davelab6 davelab6 referenced this issue in adobe-fonts/source-sans-pro Jan 21, 2015
Closed

Support more writing systems? #56

@PeterBocan

Any news on that? It's almost a year ago, guys...

@pauldhunt

There is a ton of news, just not an official version yet. You can follow all the latest changes here:
https://github.com/pauldhunt/SourceCodePro/tree/PaulVersionCurrent

@adrientetar

@pauldhunt I think you're confusing repos, this is Source Serif Pro here.:)

@pauldhunt
pauldhunt commented Apr 18, 2015 edited

doh! apparently i have SCP italics on the brain, which have also been taking plenty of time. font development can be a slow process, especially if you have multiple projects that require attention.

@miguelsousa
Member

@PeterBocan it's probably going to be another year until the italics materialize. @frankrolf has been sketching them out, but he has higher priority projects in his queue.

@PeterBocan

Okay, thank you, @miguelsousa :)

@pstonier

Any update on where these stand? I'm excited for how this is progressing.

@frankrolf
Member

Still in active development, however without a specific deadline.

@pstonier

ok. Thank you.

@andya9
andya9 commented Oct 7, 2015

Thank’you for the beautiful font!
(Btw, you can leave an issue open but prevent adding more comments to it by locking it, see here https://github.com/blog/1847-locking-conversations)

@frankrolf
Member

Thanks @andya9! Sorry for being grouchy here originally, still working on the Italics! :)

@andya9
andya9 commented Oct 8, 2015

No probs, thank’you again 😄

@mbutterick

You got monkeypatched!

@miguelsousa
Member

@mbutterick Utopia Italic derivative? Seems to work well together at first glance.

@adrientetar

Utopia Italic derivative?

Yes, it's called Heuristica. Originally we were using it in the upright style too but people weren't very satisfied with it and I found Source Serif Pro to be a better fit for the documentation.
But it doesn't have italics.

Anyway. I think it works fairly well with Utopia here.

@frankrolf
Member

It’s nice to see how lacking italics inspire typographic creativity.
Eventually the Rust documentation will be able to use Source Serif throughout, but not just yet.

@dmoonfire

I went another approach of using the lighter weight (in the epigraph and the line that starts with "As the sun touched the horizon, the dépa turned sharply") for italics. I was originally planning on switching to italics when they were available, but using the light for italics has been growing on me. I'm doing the same with Source Serif Pro also since they are on the same page on that site.

@frankrolf
Member

@dmoonfire Great! There are many ways for expressing typographic hierarchy other than using Italics. I am not apologizing here, just making a point for people saying Source Serif is “unusable” for its lack of Italics. They will come eventually!

@mbutterick

☹ U+2639 SAD ADOBE FACE

@frankrolf
Member

:trollface: U+666G TROLL FACE

@LandonSchropp

+1 😄

@KingScooty

+1

@philipzae

+1 - LibreOffice wishes to bundle the font with its installation, as it already bundles Source Sans, but is awaiting italics to be completed. https://bugs.documentfoundation.org/show_bug.cgi?id=79022

@frankrolf is there some means to assisting in its completion?

@frankrolf
Member

That is very nice to hear!
Encouragements like this are good arguments for internal politics, so in a way, you are assisting already! Other than that, I think I just need a bit more time.
Thank you!

@nathanjweber

+1

In a way, restriction has bred creativity on our team but having the flexibility of using italics in some areas would be nice. It's especially necessary for our work since italics mean something specific to our users as a way of differentiating references and cites. Hope it comes to fruition soon!

@mg-13 mg-13 referenced this issue in silkeh/latex-sourceserifpro Apr 8, 2016
Closed

Font variants (weights, shapes) don't work #1

@mg-13
mg-13 commented Apr 8, 2016

Why am I able to set font-style: italic; in CSS when viewing the font on the web (e.g. in typekit )?
Does the browser just tilt this over? Works in Firefox and IE (no webkit currently installed)...

@mrzool
mrzool commented Apr 8, 2016

@mg-13 That's exactly what browsers do, it's called faux italic.

If text is styled as bold or italic and the typeface family does not include a bold or italic font, browsers will compensate by trying to create bold and italic styles themselves. (via)

@KurtPfeifle

Has development of this font stalled? Latest commit (other than a small update to the README 6 months ago) was more than a year ago: "commit 03b7185 on Jan 16, 2015".

Should I let go all hope for a real italic version?

@miguelsousa
Member

@KurtPfeifle Development on this project is very much alive, and coincidentally @frankrolf and I just finished discussing plans for a new build of the upright fonts coming out within the next couple of months or so.
Progress on the design of the italics has also happened in the meantime, but it's still too early to tell when those will be released.

@frankrolf
Member

Tough words.
I can assure you all that the lack of Italics has nothing to do with laziness or lack of dedication. However, there are internal priorities that take precedence. Here in this repository, of course it looks like the project is “dead”, but progress is being made every day. There are very good reasons for this progress not being public.

Being critical toward my work, I would rather release no Italics than half-baked ones, and I encourage you all to either find alternate typefaces, or – if you have to use Source Serif, use different ways for typographic emphasis.

@KurtPfeifle

@miguelsousa: Thanks a lot for the update. Good to know that we've need to be a bit more patient.

@kenlunde
Member
kenlunde commented Jun 1, 2016

@ShikiSuen: As an observer of this thread, I would like to state that you are being overly and inappropriately critical toward my highly-talented colleague, @frankrolf. As he stated in his reply, this project is not his only responsibility, and while other font developers may choose to release something that is half-baked, our team does not.

I would also like to point out that all of the projects in this repository are very important for our team, and we never take a "cut the umbilical cord" attitude toward them. Some projects require more attention than others.

In other words, please continue to be patient. 😉

@eyerhyme
eyerhyme commented Jun 1, 2016

Thank you Adobe, @frankrolf and your hard working team for giving such a generous gift to the world as these high quality open source typefaces (sans and serif). They have been widely praised by designers and the type design community.

I am looking forward to italics like everyone here, but feel rather humble to be placing any demands, because it is really a gift they are giving; and I am not financially supporting all their hard work in any way.

I am not a type designer, but all accounts are that good work like this takes a tremendous amount of time and artistic effort...many years often. I encourage all here to be patient and trust what the designers have said: they are working on it. I hope the design team feels free to take all the time they need for a quality product that they are proud of.

@PeterBocan

"Good things come to those who wait."
I have no problem waiting another year.

@kenlunde
Member
kenlunde commented Jun 7, 2016 edited

@ShikiSuen: Please accept this constructive advice.

You aren't doing yourself any favors by removing or seriously editing your posts, mainly because it disrupts the discussion flow and removes all-important context, but perhaps more importantly because your activity is always visible.

We all make mistakes, or write things in the heat of passion that we later regret, and I am as guilty as the next person when it comes to this. Owning up is always the prudent approach for such matters.

(Also, I suggest that you change your avatar.)

@frankrolf
Member

Any minute invested in removing and/or editing comments takes away my time from working on the Italics. With that in mind, I would encourage everyone to just move on, and not make this a bigger thing than it is.
I felt the need to respond to the original (now deleted) comment by @ShikiSuen, but I don’t feel the necessity to edit this conversation.

@pathawks
pathawks commented Jun 8, 2016

If you’d like to reduce the noise, you can always lock the conversation to contributors only. That way, those of us who have subscribed for updates can continue to recieve only the relevant information.

@miguelsousa miguelsousa locked and limited conversation to collaborators Jun 8, 2016
@frankrolf
Member

You can follow the progress of Source Serif Italic in my private fork.

@miguelsousa miguelsousa unlocked this conversation Jan 11, 2017
@mnmiller78

Coming soon?

@MuppetGate

Thanks for working in this :-)

@MuppetGate

Er… I meant "working on this".

@jrmiller82

Any idea when italics are going to be added? It's hard to actually use a serif font for any sort of real body text without italics...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment