This issue will track updates to the Greek Roman and the development of the Greek Italic styles. It is useful for this discussion to happen in public, so I expect this to be a longer-term issue, and be updated periodically with design PDFs, feedback, comments etc.

@ReymundS and @late2game will handle the extension of Source Serif into optical sizes Display and Caption. This issue is for tracking the work, and for answering any questions.

The full text of the OFL is in the NAME table ID 13 of the binary font files distributed by Adobe from sourceforge.

I recommend replacing it with the following to reduce the filesize and improve web font latency:

This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://scripts.sil.org/OFL

I also recommend making the copyright notice in NAME table ID 1 match the copyright notice in the txt files distributed with the fonts:

Copyright 2014 Adobe Systems Incorporated (http://www.adobe.com/), with Reserved Font Name 'Source'.

The j-acute is for emphasis in Dutch. For instance: https://twitter.com/j_acute/status/794437856781537280 See also: https://www.flickr.com/groups/jacute/

I would appreciate it if @letterror would suggest a preferred implementation.

Underscore (ascii 5F) is not visible when a document in Word 2007 is saved as .pdf Other fonts do not have this problem. The character '5F' is present in the .pdf but not visible. Windows 10.

For example: if I use Georgia or other fonts, it shows \textsuperscript like this:

But if I use Source Serif Pro, it shows like this with \textsuperscript failed-to-apply:

Hey guys, I'd love to see the implementation of glyphs containing the diacritical dots also for the Italics of SSP. Is there any chance of doing that? I don't think it should be too complicated as the base glyphs already exist. Especially the ḥ glyph is of vital importance to me. It's such a pity that this amazing typeface cannot be used in works containing DMG transcriptions for that reason. Regards,

• Elendil 03

BTW, the italics done so far look excellent!

Hi everyone,

Thanks for creating this lovely font. I am using a subfont script for my website so I ship the characters I use. I noticed that script is flagging that a non-breaking hyphen is missing from the fonts.

If it is, could you add to your to-do list when you have chance, please?

Thanks,

Dave.

In Russian and several other languages that use the Cyrillic script, accented syllables can be shown with a stress mark above the vowel. In Source Serif Pro, some vowels with diacritics are rendered incorrectly: (I have no idea what’s wrong with the capital letters, I tried both TTF and OTF with the same result.)

For all Cyrillic letters, diacritics should be positioned just above the letter. I suppose ѣ is the least obvious, so here are some examples of ѣ with acute and diaeresis from an old dictionary (when this letter was in use):

I also have a question: is it possible to make all Cyrillic letters look decent with combining marks above and below? I understand that you don’t want to do it manually, but maybe there’s a way to make something passable automatically. It’s true that we don’t use diacritics in usual texts, but sometimes it may come in handy.

With Source Serif’s optical sizes on the horizon, the decision was made to change the family name to Source Serif 4.

The reason is twofold:

• avoid the name Pro (which used to stand for an extension from Basic Latin AL1 to CE-compatible character set AL2). Source Serif much exceeds AL2, therefore Pro does not really mean anything.
• avoid metrics incompatibility in comparison with older versions. To make the building of the VF more reliable, the location of the default master has changed, which may result in small advance-width differences across font versions.

The family name going forward will be Source Serif 4, which corresponds to the current global version number.

I think the Adobe Source fonts are absolutely great. Recently (past 6 months) I've switched to Go Mono because of its serif nature and the benefits of serifs. A month or so ago I discovered Source Serif, but today, I was met with disappointment: this isn't a monospace font!

Are there any plans to make one out of it, or somehow turn it into one easily?

Thanks! And keep up the great work!

Hello, I use Source Serif Pro font on my website and on my forum too. We use Traditional Bulgarian script (which was official in Bulgaria until 1945) The traditional Bulgarian alphabet includes letters Ѣ, Ѫ and Ѭ The letter Ѣ is already present in Source Serif Pro, but letters Ѫ and Ѭ aren't.

I would ask you to add these letters in the future into your cyrillic font glyphs.

P.S. Source Serif Pro already includes old cyrillic letters Ѳ (Fita) and Ѵ (Izhitsa)

The TTF VFs report WARNING: too much 'hmtx' table data. On deeper inspection, it seems that the hmtx table in the ttf files contains various glyphs not mentioned in the GlyphOrderAndAliasDB (glyph01464 through glyph01475) – the error is that these excluded glyphs are not explicitly mentioned in the designspace’s public.skipExportGlyphs list.

In some styles, the contextual kerning triplet for L·L is tighter than the default LL pair:

https://github.com/adobe-fonts/source-serif/issues/15#issuecomment-413929491

Something is rotten in the state of Danish characters!

The Danish glyphs ǿ and Ǿ are

• correct in Libre Office's Libre Writer,
• weird in LaTeX, and
• missing in MS Word.

"Weirdness" in LaTeX: The unicode glyphs ǿ and Ǿ appear correctly in LaTeX if I use Source Serif elsewhere in the document with the explicit LaTeX constructions \'\o and \'\O; otherwise, the unicode characters appear as "tofu".

MS Word converts them to Cambria and does not allow me to convert them to Source Serif.

(Given the errors with Word, I do not give details of my LaTeX set-up.)

These two glyphs are very rarely used in Danish, according to Wikipedia.