Hi all, There is an update coming to Source Serif and Source Sans. The "pro" extension after the name is replaced by the major version number: Source Serif 4 and Source Sans 3. Personally I don't care about that, but maybe others do. It's SR#909177 and SR#909177 I came across some discussion and background here: https://github.com/adobe-fonts/source-serif/issues/77 https://github.com/google/fonts/issues/2599 Kind regards, Cor
Hi, On Mon, 2021-08-02 at 22:54 +0200, Cor Blom wrote:
Hi all,
There is an update coming to Source Serif and Source Sans. The "pro" extension after the name is replaced by the major version number: Source Serif 4 and Source Sans 3. Personally I don't care about that, but maybe others do.
It's SR#909177 and SR#909177
I think you meant SR#909176 and SR#909177, right? Also, what happens to documents (PDF, LibreOffice, etc) where the font is specified as e.g. 'Source Serif Pro'? Will they use the new 'Source Serif 4' font or will they fall back to something else? If that is the case, maybe we should add the fonts as a new package or provide a freetype fallback... Thanks, Robert
I came across some discussion and background here:
https://github.com/adobe-fonts/source-serif/issues/77
https://github.com/google/fonts/issues/2599
Kind regards,
Cor
On Tue, 03 Aug 2021 12:42:03 +0200, Robert Munteanu wrote:
Hi,
On Mon, 2021-08-02 at 22:54 +0200, Cor Blom wrote:
Hi all,
There is an update coming to Source Serif and Source Sans. The "pro" extension after the name is replaced by the major version number: Source Serif 4 and Source Sans 3. Personally I don't care about that, but maybe others do.
It's SR#909177 and SR#909177
I think you meant SR#909176 and SR#909177, right?
Also, what happens to documents (PDF, LibreOffice, etc) where the font is specified as e.g. 'Source Serif Pro'? Will they use the new 'Source Serif 4' font or will they fall back to something else? If that is the case, maybe we should add the fonts as a new package or provide a freetype fallback...
That's a good point. Can it be covered by aliasing via fontconfig? Takashi
Thanks, Robert
I came across some discussion and background here:
https://github.com/adobe-fonts/source-serif/issues/77
https://github.com/google/fonts/issues/2599
Kind regards,
Cor
On Tue, Aug 03, 2021 at 02:05:47PM +0200, Takashi Iwai wrote:
On Tue, 03 Aug 2021 12:42:03 +0200, Robert Munteanu wrote:
Hi,
On Mon, 2021-08-02 at 22:54 +0200, Cor Blom wrote:
Hi all,
There is an update coming to Source Serif and Source Sans. The "pro" extension after the name is replaced by the major version number: Source Serif 4 and Source Sans 3. Personally I don't care about that, but maybe others do.
It's SR#909177 and SR#909177
I think you meant SR#909176 and SR#909177, right?
Also, what happens to documents (PDF, LibreOffice, etc) where the font is specified as e.g. 'Source Serif Pro'? Will they use the new 'Source Serif 4' font or will they fall back to something else? If that is the case, maybe we should add the fonts as a new package or provide a freetype fallback...
That's a good point. Can it be covered by aliasing via fontconfig?
On fontconfig level, it should be possible with something like <alias> <family>old_family_name</family> <accept> <family>new_family_name</family> </accept> <alias> Petr -- Have a lot of fun!
Op 03-08-2021 om 14:32 schreef pgajdos:
On Tue, Aug 03, 2021 at 02:05:47PM +0200, Takashi Iwai wrote:
On Tue, 03 Aug 2021 12:42:03 +0200, Robert Munteanu wrote:
Hi,
On Mon, 2021-08-02 at 22:54 +0200, Cor Blom wrote:
Hi all,
There is an update coming to Source Serif and Source Sans. The "pro" extension after the name is replaced by the major version number: Source Serif 4 and Source Sans 3. Personally I don't care about that, but maybe others do.
It's SR#909177 and SR#909177
I think you meant SR#909176 and SR#909177, right?
Also, what happens to documents (PDF, LibreOffice, etc) where the font is specified as e.g. 'Source Serif Pro'? Will they use the new 'Source Serif 4' font or will they fall back to something else? If that is the case, maybe we should add the fonts as a new package or provide a freetype fallback...
That's a good point. Can it be covered by aliasing via fontconfig?
On fontconfig level, it should be possible with something like
<alias> <family>old_family_name</family> <accept> <family>new_family_name</family> </accept> <alias>
Petr
I have made a submitrequest to the project which now include suggested fontconfig file Thanks, Cor
participants (4)
-
Cor Blom -
pgajdos -
Robert Munteanu -
Takashi Iwai